[SIPForum-discussion] SDP Message in SIP problem. Please Help.
Jyoti Parija
JParija at veraznet.com
Wed Jul 29 20:42:59 UTC 2009
Kristine,
The media ports look correct to me. What kind of device you are using for SIP endpoints. From your flow it doesn't look like a firewall issue but still make sure all the ports are open, also take a ethereal trace and look for RTP/RTCP packets.
Thanks,
-JP
________________________________
From: Kristine Regis [mailto:kristine at racequeen.ph]
Sent: Tuesday, July 28, 2009 8:30 PM
To: Jyoti Parija
Cc: discussion at sipforum.org
Subject: Re: [SIPForum-discussion] SDP Message in SIP problem. Please Help.
Hi Jyoti,
I already modified my codes about this. Below is the new log. Still no voice can be heard... I guess the IP is valid but I do not know is the port in the SDP is also valid. Please help. Thank you very much.
No. Time Source Destination Protocol Info
13 2.106035 172.16.100.21 172.16.100.20 SIP/SDP Request: INVITE sip:1011 at ws20.racequeen.local, with session description
Frame 13 (657 bytes on wire, 657 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: INVITE sip:1011 at ws20.racequeen.local SIP/2.0
Message Header
Max-Forwards: 69
Content-Length: 208
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>
Contact: <sip:172.16.100.21:5060;fid=server_1><sip:172.16.100.21:5060;fid=server_1>
Cseq: 1 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacfa263e491017434f85efc270abacd3f2
Content-Type: application/sdp
Call-Id: 172.16.100.21_4_8329965267378655822
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): root 3457825906 3457825906 IN IP4 172.16.100.21
Session Name (s): -
Connection Information (c): IN IP4 172.16.100.21
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 32346 RTP/AVP 0 8 101
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute (a): fmtp:101 0-15
No. Time Source Destination Protocol Info
14 2.106209 172.16.100.20 172.16.100.21 SIP Status: 100 Giving a try
Frame 14 (373 bytes on wire, 373 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 100 Giving a try
Message Header
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>
Cseq: 1 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacfa263e491017434f85efc270abacd3f2
Call-Id: 172.16.100.21_4_8329965267378655822
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
Server: OpenSIPS (1.5.1-tls (i386/linux))
Content-Length: 0
No. Time Source Destination Protocol Info
15 2.108657 172.16.100.20 172.16.100.21 SIP Status: 180 Ringing
Frame 15 (454 bytes on wire, 454 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 180 Ringing
Message Header
Max-Forwards: 70
Record-Route: <sip:172.16.100.20;lr=on><sip:172.16.100.20;lr=on>
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=2132004122
CSeq: 1 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacfa263e491017434f85efc270abacd3f2
Call-ID: 172.16.100.21_4_8329965267378655822
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
Contact: <sip:1011 at 172.16.100.20:45604;transport=udp><sip:1011 at 172.16.100.20:45604;transport=udp>
Content-Length: 0
No. Time Source Destination Protocol Info
36 9.118161 172.16.100.20 172.16.100.21 SIP/SDP Status: 200 OK, with session description
Frame 36 (640 bytes on wire, 640 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Max-Forwards: 70
Record-Route: <sip:172.16.100.20;lr=on><sip:172.16.100.20;lr=on>
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=2132004122
CSeq: 1 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacfa263e491017434f85efc270abacd3f2
Call-ID: 172.16.100.21_4_8329965267378655822
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
Contact: <sip:1011 at 172.16.100.20:45604;transport=udp><sip:1011 at 172.16.100.20:45604;transport=udp>
Content-Type: application/sdp
Content-Length: 158
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 3344 3344 IN IP4 172.16.100.20
Session Name (s): Minisip Session
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 32054 RTP/AVP 0
Connection Information (c): IN IP4 172.16.100.20
Media Attribute (a): fmtp:0 PCMU/8000
Media Attribute (a): rtpmap:0 PCMU/8000
No. Time Source Destination Protocol Info
60 9.160936 172.16.100.21 172.16.100.20 SIP Request: ACK sip:1011 at 172.16.100.20:45604;transport=udp
Frame 60 (424 bytes on wire, 424 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: ACK sip:1011 at 172.16.100.20:45604;transport=udp SIP/2.0
Message Header
Max-Forwards: 69
Content-Length: 0
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=2132004122
Cseq: 1 ACK
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac0244f9f7586f4230b9a01c480b6e869b
Route: <sip:172.16.100.20;lr=on><sip:172.16.100.20;lr=on>
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
Call-Id: 172.16.100.21_4_8329965267378655822
No. Time Source Destination Protocol Info
669 20.408322 172.16.100.20 172.16.100.21 SIP Request: BYE sip:172.16.100.21:5060;fid=server_1
Frame 669 (454 bytes on wire, 454 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: BYE sip:172.16.100.21:5060;fid=server_1 SIP/2.0
Message Header
Via: SIP/2.0/UDP 172.16.100.20;branch=z9hG4bK96f9.a20ac5a.0
Via: SIP/2.0/UDP 172.16.100.20:45604;received=172.16.100.20;rport=45604;branch=z9hG4bK64484690
Max-Forwards: 69
From: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=2132004122
To: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
CSeq: 101 BYE
Call-ID: 172.16.100.21_4_8329965267378655822
Content-Length: 0
No. Time Source Destination Protocol Info
670 20.540495 172.16.100.21 172.16.100.20 SIP Status: 200 OK
Frame 670 (432 bytes on wire, 432 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Content-Length: 0
To: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxphdaq1-4
Cseq: 101 BYE
Via: SIP/2.0/UDP 172.16.100.20;branch=z9hG4bK96f9.a20ac5a.0
Via: SIP/2.0/UDP 172.16.100.20:45604;received=172.16.100.20;rport=45604;branch=z9hG4bK64484690
Call-Id: 172.16.100.21_4_8329965267378655822
From: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=2132004122
Server: Glassfish_SIP_1.0.0
Jyoti Parija wrote:
Kristine,
This is not correct; basically SIP is a signaling protocol which exchanged in the following signaling path. A UDP socket is created with the below information.
( Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Now after successful signaling, for RTP you also need to create another UDP socket which is already exchanged in your SIP signaling messages, but if you are providing same IP/PORT for both side then the connection can't be established. For your specific case you can stop sending SDP in the ACK or send the SDP with valid IP & port in the SDP.
Please let me know if you have any further question.
Thanks,
-JP
________________________________
From: Kristine Regis [mailto:kristine at racequeen.ph]
Sent: Tuesday, July 28, 2009 4:50 PM
To: Jyoti Parija
Cc: discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: Re: [SIPForum-discussion] SDP Message in SIP problem. Please Help.
Jyoti
Yes, I already noticed that. It seems that the SDP that I sent to the other is the same SDP that the other sent to me. Is this wrong? What must I do to this kind of problem?
Jyoti Parija wrote:
Kristine
>From your logs it looks like you are sending same media attributes from both the end. You started with a different SDP in the INVITE from originating side but in the ACK you are updating the SDP and looks like you are sending the same media attributes which you have received from the terminating party in the 200OK.
Hope this help.
Frame 54 (656 bytes on wire, 656 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Max-Forwards: 70
Record-Route: <sip:172.16.100.20;lr=on;did=d53.8b77d2a><sip:172.16.100.20;lr=on;did=d53.8b77d2a>
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=1992049861
CSeq: 2 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac3bcf533d13cc42b7a6421db7f67c6376
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-ID: 172.16.100.21_3_5421782881147155363
Contact: <sip:1011 at 172.16.100.20:45604;transport=udp><sip:1011 at 172.16.100.20:45604;transport=udp>
Content-Type: application/sdp
Content-Length: 158
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 3344 3344 IN IP4 172.16.100.20
Session Name (s): Minisip Session
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 30216 RTP/AVP 0
Connection Information (c): IN IP4 172.16.100.20
Media Attribute (a): fmtp:0 PCMU/8000
Media Attribute (a): rtpmap:0 PCMU/8000
No. Time Source Destination Protocol Info
64 3.976924 172.16.100.21 172.16.100.20 SIP/SDP Request: ACK sip:1011 at 172.16.100.20:45604;transport=udp, with session description
Frame 64 (631 bytes on wire, 631 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: ACK sip:1011 at 172.16.100.20:45604;transport=udp SIP/2.0
Message Header
Max-Forwards: 69
Content-Length: 158
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=1992049861
Cseq: 2 ACK
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac9271347a14484bd68fca9e4cc9a21e2a
Content-Type: application/sdp
Route: <sip:172.16.100.20;lr=on;did=d53.8b77d2a><sip:172.16.100.20;lr=on;did=d53.8b77d2a>
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-Id: 172.16.100.21_3_5421782881147155363
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 3344 3344 IN IP4 172.16.100.20
Session Name (s): Minisip Session
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 30216 RTP/AVP 0
Connection Information (c): IN IP4 172.16.100.20
Media Attribute (a): fmtp:0 PCMU/8000
Media Attribute (a): rtpmap:0 PCMU/8000
JP
________________________________
From: discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org> [mailto:discussion-bounces at sipforum.org] On Behalf Of Kristine Regis
Sent: Tuesday, July 28, 2009 12:10 AM
To: Venkata Ramesh B
Cc: discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: Re: [SIPForum-discussion] SDP Message in SIP problem. Please Help.
Hi,
Thank you for the reply. I have the wireshark trace. The SDP Message is already updated and the payload 101 is already there but still there is no voice streaming happening.
The trace is the following:
No. Time Source Destination Protocol Info
7 1.105177 172.16.100.21 172.16.100.20 SIP/SDP Request: INVITE sip:1011 at ws20.racequeen.local, with session description
Frame 7 (671 bytes on wire, 671 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: INVITE sip:1011 at ws20.racequeen.local SIP/2.0
Message Header
Max-Forwards: 69
Content-Length: 222
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>
Contact: <sip:172.16.100.21:5060;fid=server_1><sip:172.16.100.21:5060;fid=server_1>
Cseq: 1 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacb94b87d8c96340dbb28986e8f78f78bd
Content-Type: application/sdp
Call-Id: 172.16.100.21_3_5421782881147155363
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): root 3457739521 3457739521 IN IP4 ws21.racequeen.local
Session Name (s): -
Connection Information (c): IN IP4 ws21.racequeen.local
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 32346 RTP/AVP 0 8 101
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute (a): fmtp:101 0-15
No. Time Source Destination Protocol Info
8 1.107079 172.16.100.20 172.16.100.21 SIP Status: 407 Proxy Authentication Required
Frame 8 (547 bytes on wire, 547 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 407 Proxy Authentication Required
Message Header
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.7440
Cseq: 1 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacb94b87d8c96340dbb28986e8f78f78bd
Call-Id: 172.16.100.21_3_5421782881147155363
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Proxy-Authenticate: Digest realm="ws20.racequeen.local", nonce="4a6e6ca0000000026de77af5ef8dceea597d1fa785a4ee52"
Server: OpenSIPS (1.5.1-tls (i386/linux))
Content-Length: 0
No. Time Source Destination Protocol Info
9 1.166012 172.16.100.21 172.16.100.20 SIP Request: ACK sip:1011 at ws20.racequeen.local
Frame 9 (404 bytes on wire, 404 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: ACK sip:1011 at ws20.racequeen.local SIP/2.0
Message Header
Max-Forwards: 70
Content-Length: 0
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.7440
Cseq: 1 ACK
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaacb94b87d8c96340dbb28986e8f78f78bd
Call-Id: 172.16.100.21_3_5421782881147155363
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
No. Time Source Destination Protocol Info
10 1.214436 172.16.100.21 172.16.100.20 SIP/SDP Request: INVITE sip:1011 at ws20.racequeen.local, with session description
Frame 10 (901 bytes on wire, 901 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: INVITE sip:1011 at ws20.racequeen.local SIP/2.0
Message Header
Max-Forwards: 69
Proxy-Authorization: Digest algorithm=MD5, username="1009", realm="ws20.racequeen.local", nonce="4a6e6ca0000000026de77af5ef8dceea597d1fa785a4ee52", uri="sip:1011 at ws20.racequeen.local"<sip:1011 at ws20.racequeen.local>, response="11238a9c03294b7a304d2746d7473168"
Content-Length: 222
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>
Contact: <sip:172.16.100.21:5060;fid=server_1><sip:172.16.100.21:5060;fid=server_1>
Cseq: 2 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac3bcf533d13cc42b7a6421db7f67c6376
Content-Type: application/sdp
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-Id: 172.16.100.21_3_5421782881147155363
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): root 3457739522 3457739522 IN IP4 ws21.racequeen.local
Session Name (s): -
Connection Information (c): IN IP4 ws21.racequeen.local
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 32346 RTP/AVP 0 8 101
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute (a): fmtp:101 0-15
No. Time Source Destination Protocol Info
16 1.220290 172.16.100.20 172.16.100.21 SIP Status: 100 Giving a try
Frame 16 (373 bytes on wire, 373 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 100 Giving a try
Message Header
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>
Cseq: 2 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac3bcf533d13cc42b7a6421db7f67c6376
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-Id: 172.16.100.21_3_5421782881147155363
Server: OpenSIPS (1.5.1-tls (i386/linux))
Content-Length: 0
No. Time Source Destination Protocol Info
29 1.275839 172.16.100.20 172.16.100.21 SIP Status: 180 Ringing
Frame 29 (470 bytes on wire, 470 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 180 Ringing
Message Header
Max-Forwards: 70
Record-Route: <sip:172.16.100.20;lr=on;did=d53.8b77d2a><sip:172.16.100.20;lr=on;did=d53.8b77d2a>
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=1992049861
CSeq: 2 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac3bcf533d13cc42b7a6421db7f67c6376
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-ID: 172.16.100.21_3_5421782881147155363
Contact: <sip:1011 at 172.16.100.20:45604;transport=udp><sip:1011 at 172.16.100.20:45604;transport=udp>
Content-Length: 0
No. Time Source Destination Protocol Info
41 1.781782 172.16.100.20 172.16.100.21 SIP Status: 180 Ringing
Frame 41 (470 bytes on wire, 470 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 180 Ringing
Message Header
Max-Forwards: 70
Record-Route: <sip:172.16.100.20;lr=on;did=d53.8b77d2a><sip:172.16.100.20;lr=on;did=d53.8b77d2a>
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=1992049861
CSeq: 2 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac3bcf533d13cc42b7a6421db7f67c6376
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-ID: 172.16.100.21_3_5421782881147155363
Contact: <sip:1011 at 172.16.100.20:45604;transport=udp><sip:1011 at 172.16.100.20:45604;transport=udp>
Content-Length: 0
No. Time Source Destination Protocol Info
54 3.930376 172.16.100.20 172.16.100.21 SIP/SDP Status: 200 OK, with session description
Frame 54 (656 bytes on wire, 656 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a), Dst: HonHaiPr_59:bf:74 (00:22:68:59:bf:74)
Internet Protocol, Src: 172.16.100.20 (172.16.100.20), Dst: 172.16.100.21 (172.16.100.21)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Max-Forwards: 70
Record-Route: <sip:172.16.100.20;lr=on;did=d53.8b77d2a><sip:172.16.100.20;lr=on;did=d53.8b77d2a>
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=1992049861
CSeq: 2 INVITE
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac3bcf533d13cc42b7a6421db7f67c6376
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-ID: 172.16.100.21_3_5421782881147155363
Contact: <sip:1011 at 172.16.100.20:45604;transport=udp><sip:1011 at 172.16.100.20:45604;transport=udp>
Content-Type: application/sdp
Content-Length: 158
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 3344 3344 IN IP4 172.16.100.20
Session Name (s): Minisip Session
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 30216 RTP/AVP 0
Connection Information (c): IN IP4 172.16.100.20
Media Attribute (a): fmtp:0 PCMU/8000
Media Attribute (a): rtpmap:0 PCMU/8000
No. Time Source Destination Protocol Info
64 3.976924 172.16.100.21 172.16.100.20 SIP/SDP Request: ACK sip:1011 at 172.16.100.20:45604;transport=udp, with session description
Frame 64 (631 bytes on wire, 631 bytes captured)
Ethernet II, Src: HonHaiPr_59:bf:74 (00:22:68:59:bf:74), Dst: HonHaiPr_59:bf:7a (00:22:68:59:bf:7a)
Internet Protocol, Src: 172.16.100.21 (172.16.100.21), Dst: 172.16.100.20 (172.16.100.20)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: ACK sip:1011 at 172.16.100.20:45604;transport=udp SIP/2.0
Message Header
Max-Forwards: 69
Content-Length: 158
To: <sip:1011 at ws20.racequeen.local><sip:1011 at ws20.racequeen.local>;tag=1992049861
Cseq: 2 ACK
Via: SIP/2.0/UDP 172.16.100.21:5060;branch=z9hG4bKdaac9271347a14484bd68fca9e4cc9a21e2a
Content-Type: application/sdp
Route: <sip:172.16.100.20;lr=on;did=d53.8b77d2a><sip:172.16.100.20;lr=on;did=d53.8b77d2a>
From: <sip:1009 at ws20.racequeen.local><sip:1009 at ws20.racequeen.local>;tag=fxo1xri9-3
Call-Id: 172.16.100.21_3_5421782881147155363
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 3344 3344 IN IP4 172.16.100.20
Session Name (s): Minisip Session
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 30216 RTP/AVP 0
Connection Information (c): IN IP4 172.16.100.20
Media Attribute (a): fmtp:0 PCMU/8000
Media Attribute (a): rtpmap:0 PCMU/8000
I do not know what really is the problem why both parties cannot hear each other. Please help me solve this.. Thank you very much..
Venkata Ramesh B wrote:
Hi Kristine,
The SDP has a problem that the rtpmap line is missing for payload 101 and it is mandatory. Since you say that the INVITE is accepted by the server, it is hard to say if that is the real problem. Do you have the full wireshark trace ?
Best Regards,
Ramesh.
On Sat, Jul 25, 2009 at 9:38 AM, Kristine Regis <kristine at racequeen.ph<mailto:kristine at racequeen.ph>> wrote:
Hi, I hope anyone could help me figure out what's the problem here.
I am currently developing a SIP Call. The flow of the call from INVITE
to BYE is correct, as I assume since the server accepted it - the server
is OpenSIPs. My SDP is as follows:
v=0
o=root 3457409648 3457409648 IN IP4 172.16.100.21
s=-
c=IN IP4 172.16.100.21
t=0 0
m=audio 5060 RTP/AVP 0 8 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
I have this SDP and the voice streaming cannot be done. The caller and
the call cannot here each other. I don't know what is the problem here
or if the SDP above is wrong.
I hope you could help me solve this problem. Thank you.
_______________________________________________
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/20090729/974626a6/attachment-0002.html>
More information about the discussion
mailing list