[jitsi-dev] SIP: Is Message-Account mandatory?


#1

I am tyring to connect Jitsi to my corporate SIP system but I am not
getting voicemail notifications.

I see the following in the SIP NOTIFY message coming from the server:

No. Time Source Destination Protocol
Info
     27 4.851096 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY SIP
Request: NOTIFY sip:1079@YYY.YYY.YYY.YYY
:5060;transport=udp;registering_acc=XXX.XXX.XXX.XXX

Frame 27: 683 bytes on wire (5464 bits), 683 bytes captured (5464 bits)
Ethernet II, Src: 00:ff:69:75:0a:89 (00:ff:69:75:0a:89), Dst:
00:ff:68:75:0a:89 (00:ff:68:75:0a:89)
Internet Protocol, Src: XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX), Dst:
YYY.YYY.YYY.YYY (YYY.YYY.YYY.YYY)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
    Request-Line: NOTIFY
sip:1079@YYY.YYY.YYY.YYY:5060;transport=udp;registering_acc=XXX.XXX.XXX.XXX
SIP/2.0
    Message Header
        Via: SIP/2.0/UDP
XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-d87543-bc3dde151dfbb234-1--d87543-;rport
        Max-Forwards: 70
        Contact: <sip:2000@XXX.XXX.XXX.XXX>
        Call-ID: e86ceda02031bf2a852d6fe2de9dab6d@0:0:0:0:0:0:0:0
        CSeq: 2 NOTIFY
        Content-Type: application/simple-message-summary
        User-Agent: Aastra MX-ONE SN/12.120
        Subscription-State: active;expires=3600
        Event: message-summary
        Content-Length: 23
    Message Body
        Messages-Waiting: yes\r\n

I have normally seen the 'message body' fields to contain following
elements and values (as an example):
    Message Body
        Messages-Waiting: yes\r\n
        Message-Account: sip:xxxx@sip.domain.com\r\n
        Voice-Message: 3/0 (0/0)\r\n

Does Jitsi expect the Message-Account and Voice-Message IE's also? Are
these mandatory or can they be left out in certain circumstances? I
sometimes use the free SIP Client Zoiper and it does give me a message
waiting indicator.

Thanks!

···

To: "MyName"<sip:1000@XXX.XXX.XXX.XXX>;tag=e153a10e
        From: "MyName"<sip:1000@XXX.XXX.XXX.XXX>;tag=b00ff97a


#2

Hi,

well it seems that the detailed message summary is not always
available as said in rfc3842:
"In some cases, detailed message summaries are not available."

But on our side we are waiting to see number of messages to notify the
UI, and that's why you don't see any indication.
So we should notify the UI and without number of voice
messages(MessageWaitingEvent), lets hear other devs, any other
proposals?
And without number we still need to make the red button of newly
arrived messages to indicate them.

Regards
damencho

···

On Thu, Mar 22, 2012 at 11:39 AM, Mark Campbell-Smith <mcampbellsmith@gmail.com> wrote:

I am tyring to connect Jitsi to my corporate SIP system but I am not getting
voicemail notifications.

I see the following in the SIP NOTIFY message coming from the server:

No. Time Source Destination Protocol
Info
27 4.851096 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY SIP
Request: NOTIFY
sip:1079@YYY.YYY.YYY.YYY:5060;transport=udp;registering_acc=XXX.XXX.XXX.XXX

Frame 27: 683 bytes on wire (5464 bits), 683 bytes captured (5464 bits)
Ethernet II, Src: 00:ff:69:75:0a:89 (00:ff:69:75:0a:89), Dst:
00:ff:68:75:0a:89 (00:ff:68:75:0a:89)
Internet Protocol, Src: XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX), Dst:
YYY.YYY.YYY.YYY (YYY.YYY.YYY.YYY)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: NOTIFY
sip:1079@YYY.YYY.YYY.YYY:5060;transport=udp;registering_acc=XXX.XXX.XXX.XXX
SIP/2.0
Message Header
Via: SIP/2.0/UDP
XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-d87543-bc3dde151dfbb234-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:2000@XXX.XXX.XXX.XXX>
To: "MyName"<sip:1000@XXX.XXX.XXX.XXX>;tag=e153a10e
From: "MyName"<sip:1000@XXX.XXX.XXX.XXX>;tag=b00ff97a
Call-ID: e86ceda02031bf2a852d6fe2de9dab6d@0:0:0:0:0:0:0:0
CSeq: 2 NOTIFY
Content-Type: application/simple-message-summary
User-Agent: Aastra MX-ONE SN/12.120
Subscription-State: active;expires=3600
Event: message-summary
Content-Length: 23
Message Body
Messages-Waiting: yes\r\n

I have normally seen the 'message body' fields to contain following elements
and values (as an example):
Message Body
Messages-Waiting: yes\r\n
Message-Account: sip:xxxx@sip.domain.com\r\n
Voice-Message: 3/0 (0/0)\r\n

Does Jitsi expect the Message-Account and Voice-Message IE's also? Are
these mandatory or can they be left out in certain circumstances? I
sometimes use the free SIP Client Zoiper and it does give me a message
waiting indicator.

Thanks!


#3

Hey,

I've just committed a quick fix for it. When there is no detail
information for messages you will still get notification that you have
new messages, but you will still be unable to call to check them, as
the account for checking messages is missing.
Please test build 3960 to see is it working now?

Thanks
damencho

···

On Thu, Mar 22, 2012 at 11:59 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

well it seems that the detailed message summary is not always
available as said in rfc3842:
"In some cases, detailed message summaries are not available."

But on our side we are waiting to see number of messages to notify the
UI, and that's why you don't see any indication.
So we should notify the UI and without number of voice
messages(MessageWaitingEvent), lets hear other devs, any other
proposals?
And without number we still need to make the red button of newly
arrived messages to indicate them.

Regards
damencho

On Thu, Mar 22, 2012 at 11:39 AM, Mark Campbell-Smith > <mcampbellsmith@gmail.com> wrote:

I am tyring to connect Jitsi to my corporate SIP system but I am not getting
voicemail notifications.

I see the following in the SIP NOTIFY message coming from the server:

No. Time Source Destination Protocol
Info
27 4.851096 XXX.XXX.XXX.XXX YYY.YYY.YYY.YYY SIP
Request: NOTIFY
sip:1079@YYY.YYY.YYY.YYY:5060;transport=udp;registering_acc=XXX.XXX.XXX.XXX

Frame 27: 683 bytes on wire (5464 bits), 683 bytes captured (5464 bits)
Ethernet II, Src: 00:ff:69:75:0a:89 (00:ff:69:75:0a:89), Dst:
00:ff:68:75:0a:89 (00:ff:68:75:0a:89)
Internet Protocol, Src: XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX), Dst:
YYY.YYY.YYY.YYY (YYY.YYY.YYY.YYY)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: NOTIFY
sip:1079@YYY.YYY.YYY.YYY:5060;transport=udp;registering_acc=XXX.XXX.XXX.XXX
SIP/2.0
Message Header
Via: SIP/2.0/UDP
XXX.XXX.XXX.XXX:5060;branch=z9hG4bK-d87543-bc3dde151dfbb234-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:2000@XXX.XXX.XXX.XXX>
To: "MyName"<sip:1000@XXX.XXX.XXX.XXX>;tag=e153a10e
From: "MyName"<sip:1000@XXX.XXX.XXX.XXX>;tag=b00ff97a
Call-ID: e86ceda02031bf2a852d6fe2de9dab6d@0:0:0:0:0:0:0:0
CSeq: 2 NOTIFY
Content-Type: application/simple-message-summary
User-Agent: Aastra MX-ONE SN/12.120
Subscription-State: active;expires=3600
Event: message-summary
Content-Length: 23
Message Body
Messages-Waiting: yes\r\n

I have normally seen the 'message body' fields to contain following elements
and values (as an example):
Message Body
Messages-Waiting: yes\r\n
Message-Account: sip:xxxx@sip.domain.com\r\n
Voice-Message: 3/0 (0/0)\r\n

Does Jitsi expect the Message-Account and Voice-Message IE's also? Are
these mandatory or can they be left out in certain circumstances? I
sometimes use the free SIP Client Zoiper and it does give me a message
waiting indicator.

Thanks!