[SIPForum-discussion] NOTIFY SIP message check.

Mon Nov 14 01:51:52 UTC 2011

The port is optional, and if it's not explicitly encoded then it defaults to the well-known port number for SIP of 5060, and according to the capture info it was correctly using 5060 at the UDP layer.  So this shouldn't cause the 400 response.

The only thing I can see that is bad about this request is it's a NOTIFY outside of a Subscription dialog: it has not To-tag, and it has no Subscription-State header.  While technically illegal, it's not uncommon to see such NOTIFY requests (it's often called an "unsolicited Notify" in the industry).  So if your PBX doesn't support unsolicited Notify, it may well be the reason it's sending a 400 response. (it should have sent a 481 instead, but that doesn't matter)

Or it could be that the PBX simply doesn't support the "message-summary" event-package. (it should send a 489 in such a case, but that doesn't matter)

Or it could be that there's something syntactically invalid about the message that we can't tell from the parsed debugging output below.  For example, the Content-Length says it's 20, but if it actually follows RFC 3842 then I think there's supposed to be a CRLF at the end of the "Messages-Waiting: no" text, and that CRLF is part of the body not a delimiter and thus the Content-Length should be 22.  So either the MIME body is wrong, or the body really does contain the CRLF and the Content-Length is wrong.  We can't tell because the decoded message in the email below is in parsed text format itself so we can't see the actual UDP packet payload contents.

-hadriel

On Nov 10, 2011, at 1:02 PM, Keyur Amin wrote:

You seem to be missing port of the Request URI:

NOTIFY sip:3003 at 192.168.1.230:[PORT] SIP/2.0

Thanks,
Keyur Amin
________________________________

________________________________
From: Andy Burbidge <Andy.Burbidge at tigertms.com<mailto:Andy.Burbidge at tigertms.com>>
To: "discussion at sipforum.org<mailto:discussion at sipforum.org>" <discussion at sipforum.org<mailto:discussion at sipforum.org>>
Sent: Wednesday, November 9, 2011 2:01 AM
Subject: [SIPForum-discussion] NOTIFY SIP message check.

Would someone be good enough to take a look at this text capture of a NOTIFY message from Wireshark and tell me it looks 'well formed'?

I am getting 400 Bad Request bad from the PBX and I just wanted to check the simple things first :)

TIA

Frame 1306 (549 bytes on wire, 549 bytes captured)
Ethernet II, Src: Dell_08:e6:43 (00:19:b9:08:e6:43), Dst: AsustekC_4f:04:e2 (00:17:31:4f:04:e2)
Internet Protocol, Src: 192.168.137.205 (192.168.137.205), Dst: 192.168.1.230 (192.168.1.230)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
    Request-Line: NOTIFY sip:3003 at 192.168.1.230 SIP/2.0
        Method: NOTIFY
        [Resent Packet: False]
    Message Header
        From: <sip:8000 at 192.168.137.205>;tag=5de8a78-0-13c4-10361b-31597357-10361b
            SIP from address: sip:8000 at 192.168.137.205
            SIP tag: 5de8a78-0-13c4-10361b-31597357-10361b
        To: <sip:3003 at 192.168.1.230>
            SIP to address: sip:3003 at 192.168.1.230
        Call-ID: 5de8a78-0-13c4-10361b-3e001cf9-10361b at 192.168.137.205<mailto:5de8a78-0-13c4-10361b-3e001cf9-10361b at 192.168.137.205>
        CSeq: 1 NOTIFY
            Sequence Number: 1
            Method: NOTIFY
        Via: SIP/2.0/UDP 192.168.137.205:5060;branch=z9hG4bK-10361b-3f535ac0-524b0494
            Transport: UDP
            Sent-by Address: 192.168.137.205
            Sent-by port: 5060
            Branch: z9hG4bK-10361b-3f535ac0-524b0494
        Max-Forwards: 70
        Supported: replaces
        Content-Disposition: signal; handling=optional
        Event: message-summary
        Content-Type: application/simple-message-summary
        Content-Length: 20
    Message body
        Messages-Waiting: no

Andy Burbidge
Voice Developer

--
This message (including attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and delete this message immediately.
Any views or opinions presented are solely those of the author and do not necessarily represent those of TigerTMS unless otherwise specifically stated.

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20111114/0577b208/attachment-0002.html>