Hi,
One noticable difference among two NOTIFY is, contact header is
missing in first. As per RFC 3265, contact header being mandatory for
NOTIFY hence could be one reason for failure response, though response
code doesn't seem so.
You may refer the table in RFC3265,
7.1. New Methods
This document describes two new SIP methods: SUBSCRIBE and
NOTIFY.
This table expands on tables 2 and 3 in SIP [1].
Header Where SUB NOT
------ ----- --- ---
Contact R m m
Rgds,
Manju
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Peter Spikings
> Sent: Tuesday, August 08, 2006 9:20 PM
> To: [email protected]
> Subject: [Sip-implementors] Problem with notify's
>
>
> Hi all,
>
> I've written a program which is designed to notify some
> phones when they have voicemails based on some centralised
> database voicemail storage. The phones all register with one
> of a number of Asterisk servers for load balancing and
> Asterisk isn't capable of sending notify's when the voicemail
> is stored in the database.
>
> The way Asterisk sends out voicemail notifications is that it
> just sends the notify without any subscription from the phone
> as long as the phone has registered with it. This works fine
> but when I try and do the same thing myself the phone
> responds with 404.
>
> I end up sending:
>
> --
> NOTIFY sip:[EMAIL PROTECTED] SIP/2.0
> Via: SIP/2.0/UDP 192.168.1.253:5062;rport;branch=z9hG4bK1853134342
> From: <sip:[EMAIL PROTECTED]>;tag=1047304202
> To: <sip:[EMAIL PROTECTED]>
> Call-ID: [EMAIL PROTECTED]
> CSeq: 20 NOTIFY
> Max-Forwards: 5
> User-Agent: eXosip/0.1
> Event: message-summary
> Content-Type: application/simple-message-summary
> Content-Length: 93
>
> Message-Waiting: yes
> Message-Account: sip:[EMAIL PROTECTED]
> Voice-Message: 1/1 (0/0)
> --
>
> and receive back:
>
> --
> SIP/2.0 404 Not Found
> Via: SIP/2.0/UDP 192.168.1.253:5062;rport;branch=z9hG4bK1853134342
> From: <sip:[EMAIL PROTECTED]>;tag=1047304202
> To: <sip:[EMAIL PROTECTED]>
> CSeq: 20 NOTIFY
> Call-ID: [EMAIL PROTECTED]
> Event: message-summary
> User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.4.0064
> Content-Length: 0
> --
>
> Here is an example of Asterisk sending the notification:
>
> --
> NOTIFY sip:[EMAIL PROTECTED] SIP/2.0
> Via: SIP/2.0/UDP 10.10.8.249:5060;branch=z9hG4bK7709e69b;rport
> From: "asterisk" <sip:[EMAIL PROTECTED]>;tag=as03f6fd5f
> To: <sip:[EMAIL PROTECTED]>
> Contact: <sip:[EMAIL PROTECTED]>
> Call-ID: [EMAIL PROTECTED]
> CSeq: 102 NOTIFY
> User-Agent: Asterisk PBX
> Max-Forwards: 70
> Event: message-summary
> Content-Type: application/simple-message-summary
> Content-Length: 92
>
> Messages-Waiting: yes
> Message-Account: sip:[EMAIL PROTECTED]
> Voice-Message: 1/1 (0/0)
> --
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 10.10.8.249:5060;branch=z9hG4bK7709e69b;rport
> From: "asterisk" <sip:[EMAIL PROTECTED]>;tag=as03f6fd5f
> To: <sip:[EMAIL PROTECTED]>;tag=EE7CE0E5-B25F3EAE
> CSeq: 102 NOTIFY
> Call-ID: [EMAIL PROTECTED]
> Contact: <sip:[EMAIL PROTECTED]>
> Event: message-summary
> User-Agent: PolycomSoundPointIP-SPIP_600-UA/1.6.4.0064
> Content-Length: 0
> --
>
> I can't see any substantive differences hence this post. Can
> anyone see what I'm doing wrong here? If there are any
> transgressions against the SIP RFC I'd also appreciate
> knowing about them too :)
>
> TIA,
>
> Peter.
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/lis> tinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
