Hi, My question today is more regarding RFC's.
I've tried to find out if NOTIFY and Event: message-summary needs a Contact header. At least my Cisco gateway discards Notify's without a Contact header (400 Bad Request - 'Malformed/Missing Contact field')
Is this a Cisco bug or SHOULD/MUST a NOTIFY have Contact of the sender?
br hw
On Thu, Jan 12, 2006 at 09:15:23AM +0100, Helge Waastad wrote:
Hi, My question today is more regarding RFC's.
I've tried to find out if NOTIFY and Event: message-summary needs a Contact header. At least my Cisco gateway discards Notify's without a Contact header (400 Bad Request - 'Malformed/Missing Contact field')
Is this a Cisco bug or SHOULD/MUST a NOTIFY have Contact of the sender?
br hw
The Contact header is mandatory in NOTIFY requests and 3xx responses for NOTIFY, according to the table on page 33 in RFC3265.
/Mikael
Hi, and thank's.
I guess there are several SIP components out there not strictly RFC compliant... :-( (I mean my Cisco (in this matter) is OK, but not the other component I have for testing)
br hw
On Thu, Jan 12, 2006 at 09:15:23AM +0100, Helge Waastad wrote:
Hi, My question today is more regarding RFC's.
I've tried to find out if NOTIFY and Event: message-summary needs a Contact header. At least my Cisco gateway discards Notify's without a Contact header (400 Bad Request - 'Malformed/Missing Contact field')
Is this a Cisco bug or SHOULD/MUST a NOTIFY have Contact of the sender?
br hw
The Contact header is mandatory in NOTIFY requests and 3xx responses for NOTIFY, according to the table on page 33 in RFC3265.
/Mikael
-
Helge Waastad -
Mikael Magnusson