Hi All.
I'm using ser-0.9.1.
Does anyone know if angle brackets are required around the TO: and FROM: headers?
Our Sonus gateway sometimes omits these brackets and I just want to make sure that SER correctly identifies SIP transactions.
Here is a PSTN->SIP INVITE that shows the brackets being omitted.
U 2005/03/21 10:19:08.966284 216.229.127.60:5060 -> 10.3.0.221:5060 INVITE sip:3212514231@10.3.0.221:5060 SIP/2.0. Via: SIP/2.0/UDP 216.229.127.60:5060;branch=z9hG4bK619440ef48f-34104637. Via: SIP/2.0/UDP 66.243.109.99:5060;branch=4ad748fe5b9d60cbf6a53c0614a3da05. To: 3212514231 sip:3212514231@66.243.109.99:5060. From: sip:4073192279@66.236.245.98;tag=67DD67C-D31. Call-ID: 6997024-3320407223-278012@66.243.109.99. CSeq: 1 INVITE. Max-Forwards: 4. Contact: sip:4073192279@66.243.109.99:5060. Record-Route: sip:216.229.127.60:5060;lr. Content-Type: application/sdp. Content-Length: 313. . v=0. o=NexTone-MSW 1234 3665 IN IP4 66.236.245.98. s=sip call. c=IN IP4 66.236.245.98. t=0 0. m=audio 17694 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=fmtp:4 annexa=yes. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16.
Regards, Paul
Hi Paul,
Conforming to the grammar from RFC 3261, the brackets are required only if a display name is present or if you have uri parameters: "name" <uri> uri;param <- param is header parameter <uri;param> <- param is uri parameter <uri;uparam>;hparam <- uparam = uri parameter; hparam = hdr parameter
Best regards, Marian
Java Rockx wrote:
Hi All.
I'm using ser-0.9.1.
Does anyone know if angle brackets are required around the TO: and FROM: headers?
Our Sonus gateway sometimes omits these brackets and I just want to make sure that SER correctly identifies SIP transactions.
Here is a PSTN->SIP INVITE that shows the brackets being omitted.
U 2005/03/21 10:19:08.966284 216.229.127.60:5060 -> 10.3.0.221:5060 INVITE sip:3212514231@10.3.0.221:5060 SIP/2.0. Via: SIP/2.0/UDP 216.229.127.60:5060;branch=z9hG4bK619440ef48f-34104637. Via: SIP/2.0/UDP 66.243.109.99:5060;branch=4ad748fe5b9d60cbf6a53c0614a3da05. To: 3212514231 sip:3212514231@66.243.109.99:5060. From: sip:4073192279@66.236.245.98;tag=67DD67C-D31. Call-ID: 6997024-3320407223-278012@66.243.109.99. CSeq: 1 INVITE. Max-Forwards: 4. Contact: sip:4073192279@66.243.109.99:5060. Record-Route: sip:216.229.127.60:5060;lr. Content-Type: application/sdp. Content-Length: 313. . v=0. o=NexTone-MSW 1234 3665 IN IP4 66.236.245.98. s=sip call. c=IN IP4 66.236.245.98. t=0 0. m=audio 17694 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=fmtp:4 annexa=yes. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16.
Regards, Paul
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Thanks for clearing that up!
Regards, Paul
On Mon, 21 Mar 2005 17:23:23 +0100, Marian Dumitru marian.dumitru@voice-sistem.ro wrote:
Hi Paul,
Conforming to the grammar from RFC 3261, the brackets are required only if a display name is present or if you have uri parameters: "name" <uri> uri;param <- param is header parameter <uri;param> <- param is uri parameter <uri;uparam>;hparam <- uparam = uri parameter; hparam = hdr parameter
Best regards, Marian
Java Rockx wrote:
Hi All.
I'm using ser-0.9.1.
Does anyone know if angle brackets are required around the TO: and FROM: headers?
Our Sonus gateway sometimes omits these brackets and I just want to make sure that SER correctly identifies SIP transactions.
Here is a PSTN->SIP INVITE that shows the brackets being omitted.
U 2005/03/21 10:19:08.966284 216.229.127.60:5060 -> 10.3.0.221:5060 INVITE sip:3212514231@10.3.0.221:5060 SIP/2.0. Via: SIP/2.0/UDP 216.229.127.60:5060;branch=z9hG4bK619440ef48f-34104637. Via: SIP/2.0/UDP 66.243.109.99:5060;branch=4ad748fe5b9d60cbf6a53c0614a3da05. To: 3212514231 sip:3212514231@66.243.109.99:5060. From: sip:4073192279@66.236.245.98;tag=67DD67C-D31. Call-ID: 6997024-3320407223-278012@66.243.109.99. CSeq: 1 INVITE. Max-Forwards: 4. Contact: sip:4073192279@66.243.109.99:5060. Record-Route: sip:216.229.127.60:5060;lr. Content-Type: application/sdp. Content-Length: 313. . v=0. o=NexTone-MSW 1234 3665 IN IP4 66.236.245.98. s=sip call. c=IN IP4 66.236.245.98. t=0 0. m=audio 17694 RTP/AVP 18 0 4 8 101. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:4 G723/8000. a=fmtp:4 annexa=yes. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16.
Regards, Paul
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Voice System http://www.voice-system.ro
-
Java Rockx -
Marian Dumitru