search

Sanjivkumarroshan / csipsimple

Automatically exported from code.google.com/p/csipsimple
0 stars 0 forks source link

Feature Request: MWI via Unsolicited NOTIFY #2816

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I am trying to get MWI notification via my company's CISCO Unified 
Communications Manager [aka. CUCM] 
But CISCO CUCM only supports "Unsolicited NOTIFY".

CSIP/pjsip understands "Unsolicited NOTIFY"; but does not do anything with it:

D/libpjsip(11326): NOTIFY sip:1910@192.168.137.176:55092;ob SIP/2.0
D/libpjsip(11326): Date: Thu, 16 Oct 2014 15:57:48 GMT
<snip>
D/libpjsip(11326): Messages-Waiting: yes
D/libpjsip(11326): --end msg--
D/libpjsip(11326): 11:57:47.621 pjsip_mod_earl  .mod_earlylock_on_rx_request
D/libpjsip(11326): 11:57:47.621   pjsua_pres.c  .Got unsolicited NOTIFY from 
172.22.137.5:5060..
D/libpjsip(11326): 11:57:47.622   pjsua_core.c  ...TX 275 bytes Response msg 
200/NOTIFY/cseq=101 (tdta0x61b24f50) to UDP 172.22.137.5:5060:
D/libpjsip(11326): SIP/2.0 200 OK
<snip>
D/libpjsip(11326): --end msg--
D/PjService(11326): Found pjsua 2 searching 2
D/PjService(11326): Update profile from service for 2 aka in db 2
D/SIP UA Receiver(11326): < LOCK CPU
W/SIP UA Receiver(11326): Matches : yes
D/SIP UA Receiver(11326): Hey there is messages !!! 
D/AccountChooserButton(11339): Accounts status.onChange( false)
D/PjService(11326): Profile state UP : status_text=OK status_code=200 
expires=114
D/SIP UA Receiver(11326): > UNLOCK CPU 0

I know this is actually a CISCO problem (not yours); but I am hoping that 
showing the "messages waiting" notification is a simple enough fix that you 
might do it for me.

thanks,
Kevin York

Original issue reported on code.google.com by Kevin.Yo...@gmail.com on 26 Oct 2014 at 2:25

GoogleCodeExporter commented 9 years ago 
Actually the app should support that.
BTW, from logs you see that it detects there might be some messages :
"""
D/SIP UA Receiver(11326): Hey there is messages !!! 
"""
I think that the problem is that there is no counter information in the Notify 
message.
To be sure about that could you paste the <snip> part just before the 
"Messages-Waiting".

The app expect something that matches :
Voice-Message[ \t]?:[ \t]?([0-9]*)/[0-9]*.*

in order to count messages. And if there is something > 0, display a 
notification.
Maybe this part should be optional and the app should consider there is an 
undefined number of message (but still messages) in case the Voice-Message 
header is not present.
The risk is that it's not about voice message, but other kind of messages. 
(Some SIP servers supports fax messages for example).

Original comment by r3gis...@gmail.com on 26 Oct 2014 at 9:45

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r2431.

Original comment by r3gis...@gmail.com on 26 Oct 2014 at 9:55