Warning Messages on res_pjsip_pubsub,c on Asterisk 14.6.1 CLI

Hello Support;

  1. I manage to compile Asterisk 14.6.1 and got it to run Under Ubuntu 17.
    

When asterisk was started # asterisk -cvvvvv ; some warning messages kept showing up on the screen :
[Sep 5 02:50:14] WARNING[26971]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:53:56] WARNING[26981]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:53:56] WARNING[26981]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:54:13] WARNING[26981]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:54:13] WARNING[26981]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
What is causing this warning and how can I fix this ?

2.) I did the Hello World test ; most of the step seems successful and the asterisk core is able to register the Zoiper softphone . However; I could not get any audio on the Zoiper softphone on the windows laptop

*CLI> – Added contact ‘sip:6001@172.29.97.223:60071;transport=UDP;rinstance=71dcc1f91aba92c3’ to AOR ‘6001’ with expiration of 70 seconds
== Contact 6001/sip:6001@172.29.97.223:60071;transport=UDP;rinstance=71dcc1f91aba92c3 has been created
== Endpoint 6001 is now Reachable
– Contact 6001/sip:6001@172.29.97.223:60071;transport=UDP;rinstance=71dcc1f91aba92c3 is now Unknown. RTT: 0.000 msec
– Removed contact ‘sip:6001@172.29.97.223:60071;transport=UDP;rinstance=71dcc1f91aba92c3’ from AOR ‘6001’ due to request
== Contact 6001/sip:6001@172.29.97.223:60071;transport=UDP;rinstance=71dcc1f91aba92c3 has been deleted
== Endpoint 6001 is now Unreachable
– Added contact ‘sip:6001@172.29.97.223:60071;transport=UDP;rinstance=867d9997c2962aa3’ to AOR ‘6001’ with expiration of 3600 seconds
== Contact 6001/sip:6001@172.29.97.223:60071;transport=UDP;rinstance=867d9997c2962aa3 has been created
== Endpoint 6001 is now Reachable
– Contact 6001/sip:6001@172.29.97.223:60071;transport=UDP;rinstance=867d9997c2962aa3 is now Unknown. RTT: 0.000 msec
[Sep 5 02:00:42] WARNING[26774]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:00:42] WARNING[26774]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:07:46] WARNING[26818]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:07:46] WARNING[26818]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
== Setting global variable ‘SIPDOMAIN’ to ‘172.29.160.54’
– Executing [100@from-internal:1] Answer(“PJSIP/6001-00000000”, “”) in new stack
> 0x3fff9c007980 – Probation passed - setting RTP source address to 172.29.97.223:8000
– Executing [100@from-internal:2] Wait(“PJSIP/6001-00000000”, “1”) in new stack
[Sep 5 02:07:48] WARNING[26818]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:07:48] WARNING[26818]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
– Executing [100@from-internal:3] Playback(“PJSIP/6001-00000000”, “hello-world”) in new stack
– <PJSIP/6001-00000000> Playing ‘hello-world.gsm’ (language ‘en’)
– Executing [100@from-internal:4] Hangup(“PJSIP/6001-00000000”, “”) in new stack
== Spawn extension (from-internal, 100, 4) exited non-zero on ‘PJSIP/6001-00000000’
[Sep 5 02:11:04] WARNING[26836]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:11:04] WARNING[26836]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:11:15] WARNING[26836]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:11:15] WARNING[26836]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
== Setting global variable ‘SIPDOMAIN’ to ‘172.29.160.54’
– Executing [100@from-internal:1] Answer(“PJSIP/6001-00000001”, “”) in new stack
> 0x3fff78007c60 – Probation passed - setting RTP source address to 172.29.97.223:8000
– Executing [100@from-internal:2] Wait(“PJSIP/6001-00000001”, “1”) in new stack
[Sep 5 02:11:17] WARNING[26836]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:11:17] WARNING[26836]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winf o
– Executing [100@from-internal:3] Playback(“PJSIP/6001-00000001”, “hello-world”) in new stack
– <PJSIP/6001-00000001> Playing ‘hello-world.gsm’ (language ‘en’)
– Executing [100@from-internal:4] Hangup(“PJSIP/6001-00000001”, “”) in new stack
== Spawn extension (from-internal, 100, 4) exited non-zero on ‘PJSIP/6001-00000001’
[Sep 5 02:11:58] WARNING[26836]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:11:58] WARNING[26836]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winf o
[Sep 5 02:23:37] WARNING[26878]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo
[Sep 5 02:23:37] WARNING[26878]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:41:21] WARNING[26930]: res_pjsip_pubsub.c:3183 pubsub_on_rx_publish_request: No registered publish handler for event presence
[Sep 5 02:41:21] WARNING[26930]: res_pjsip_pubsub.c:678 subscription_get_handler_from_rdata: No registered subscribe handler for event presence.winfo

Please advise how to fix the no audio problem on the softphone.
; Thank you

There is no way to fix the initial warning, the device you are using is attempting to publish presence information and this is currently unsupported.

As for your no audio problem you haven’t provided enough information. Is the client behind NAT? Is Asterisk behind NAT? What is the configuration?

Hello Jcolp,
Thank you for your response.

  1. In the first case about the constantly recurring WARNING [26930] do you mean that it is not an error and can be ignored ? Also the device is the Zoiper Softphone (running on a window laptop) or the asterisk server (which is on a cloud based VM) and connected by VPN.

2.To solve this problem; does it mean that both the Asterisk server VM and the Softphone VM must be on the same LAN segment ? Currently the Asterisk server is in the cloud and is access via putty/ssh through VPN from my laptop where the Joiper Softphone is installed. They are in different LAN segments and the ping can only go from Joiper side to Asterisk. Is this the cause of the no audio issue ?

The warning is not an error. It can be ignored.

Yes, it is entirely possible that is the cause of your audio issue. They don’t need to be on the same LAN segment, but Asterisk does need to be told it is behind NAT If so, and traffic has to be routeable between them. You’d need to provide further information about the network layout and SIP trace (pjsip set logger on) as well as configuration (pjsip.conf).