12 Jan
2006
12 Jan
'06
10:15 a.m.
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
12 Jan
12 Jan
10:26 a.m.
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
10:55 a.m.
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
6889
days inactive
6889
days old
2 comments
2 participants
participants (2)
-
Helge Waastad -
Mikael Magnusson