[OpenSIPS-Users] Inconsistent c= and o= using rtpproxy_offer and rtpproxy_answer
Bogdan-Andrei Iancu
bogdan at opensips.org
Mon Jun 30 11:48:39 CEST 2014
Hi Nick,
Assuming you do not do any autopbridging or so...., right ?
Also, hoping you connect yo RTPproxy via UDP protocol, could you make a
network trace to see what OpenSIPS sends and receives (in relation to
rtpproxy) - this capture must to be correlated (as time) with the SIP
capture, so we can see what RTPProxy interactions is done for the 183 reply.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 30.06.2014 05:26, Nick Cameo wrote:
> Hello Bogdan,
>
> Put the instance in debug level 4, inserted xlog in the on_reply as seen in the
> first line. Basically no error has been raised however, the SDP payload
> was not modified as was suggested by force_rtp_proxy:
>
>
> On_Reply Route: From=sip:'555-555-5555'@test.example.com,
> To=sip:447949185140 at 192.168.2.20:5080, RU=<null>,
> CI=66c7328526dc365a158a73ed6c7d4eaf at test.example.com IP=99.66.137.139
> Jun 29 22:06:55 [27474] DBG:core:parse_headers: flags=ffffffffffffffff
> Jun 29 22:06:55 [27474] DBG:core:decode_mime_type: Decoding MIME type
> for:[application/sdp]
> Jun 29 22:06:55 [27474] DBG:rtpproxy:force_rtp_proxy: force rtp proxy
> with param1 <roc> and param2 <192.168.2.20>
> Jun 29 22:06:55 [27474] DBG:core:parse_headers: flags=40
> Jun 29 22:06:55 [27474] DBG:rtpproxy:force_rtp_proxy: Forcing body:
> [v=0
> o=sbcsas 1384291552 1 IN IP4 34.34.12.23
> s=sbcsas SIP STACK v1.0
> c=IN IP4 34.34.12.23
> t=0 0
> m=audio 20770 RTP/AVP 18 101
> a=rtpmap:18 G729/8000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:18 annexb=no
> a=fmtp:101 0-15
> a=sendrecv
> a=nortpproxy:yes
> ]
> Jun 29 22:06:55 [27474] DBG:tm:t_should_relay_response: T_code=100, new_code=183
> Jun 29 22:06:55 [27474] DBG:tm:relay_reply: branch=1, save=0, relay=1
> Jun 29 22:06:55 [27474] DBG:tm:run_trans_callbacks: trans=0xa70be8b8,
> callback type 8, id 0 entered
> Jun 29 22:06:55 [27474] DBG:dialog:push_reply_in_dialog: 0xa70baf8c
> totag in rpl is <sbcsas_1_C11418_20140629220648445_b59sb13> (44)
> Jun 29 22:06:55 [27474] DBG:dialog:push_reply_in_dialog: new branch
> with tag <sbcsas_1_C11418_20140629220648445_b59sb13>
> Jun 29 22:06:55 [27474] DBG:core:parse_headers: flags=ffffffffffffffff
> Jun 29 22:06:55 [27474] DBG:dialog:init_leg_info: route_set , contact
> sip:99.66.137.139:5060, cseq 102 and bind_addr udp:192.168.2.20:5080
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_add_leg_info: set leg 1 for
> 0xa70baf8c: tag=<sbcsas_1_C11418_20140629220648445_b59sb13>
> rcseq=<102>
> Jun 29 22:06:55 [27474] DBG:core:parse_headers: flags=ffffffffffffffff
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_th_onreply: peer_leg = 0
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_th_onreply: first RR hdr = (nil)
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_th_onreply: deleted rr stuff
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_th_onreply: via len = 65
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_th_onreply: allocated via_str 0xb6c0953c
> Jun 29 22:06:55 [27474] DBG:dialog:dlg_th_onreply: inserting via
> headers - [Via: SIP/2.0/UDP
> 192.168.2.10:5060;branch=z9hG4bK0fcb736c;rport
> ]
> Jun 29 22:06:55 [27474] DBG:core:build_res_buf_from_sip_res: old
> size: 717, new size: 733
> Jun 29 22:06:55 [27474] DBG:core:build_res_buf_from_sip_res: copied
> size: orig:359, new: 375, rest: 358 msg=
> SIP/2.0 183 Session Progress
> Via: SIP/2.0/UDP 192.168.2.10:5060;branch=z9hG4bK0fcb736c;rport
> From: "Unavailable" <sip:'555-555-5555'@test.example.com>;tag=as6af147bf
> To: <sip:447949185140 at 192.168.2.20:5080>;tag=sbcsas_1_C11418_20140629220648445_b59sb13
> Call-ID: 66c7328526dc365a158a73ed6c7d4eaf at test.example.com
> Contact: <sip:192.168.2.20:5080;did=3eb.00abd186>
> CSeq: 102 INVITE
> Server: sbc_3
> Content-Type: application/sdp
> Content-Length: 269
>
> v=0
> o=sbcsas 1384291552 1 IN IP4 34.34.12.23
> s=sbcsas SIP STACK v1.0
> c=IN IP4 34.34.12.23
> t=0 0
> m=audio 20770 RTP/AVP 18 101
> a=rtpmap:18 G729/8000
> a=rtpmap:101 telephone-event/8000
> a=fmtp:18 annexb=no
> a=fmtp:101 0-15
> a=sendrecv
> a=nortpproxy:yes
>
> Jun 29 22:06:55 [27474] DBG:tm:run_trans_callbacks: trans=0xa70be8b8,
> callback type 64, id 0 entered
> Jun 29 22:06:55 [27474] DBG:dialog:next_state_dlg: dialog 0xa70baf8c
> changed from state 1 to state 2, due event 2
> Jun 29 22:06:55 [27474] DBG:dialog:run_dlg_callbacks:
> dialog=0xa70baf8c, type=128
>
> U 2014/06/29 22:06:55.773520 192.168.2.20:5080 -> 192.168.2.10:5060
> SIP/2.0 183 Session Progress.
> Via: SIP/2.0/UDP 192.168.2.10:5060;branch=z9hG4bK0fcb736c;rport.
> From: "Unavailable" <sip:'555-555-5555'@test.example.com>;tag=as6af147bf.
> To: <sip:447949185140 at 192.168.2.20:5080>;tag=sbcsas_1_C11418_20140629220648445_b59sb13.
> Call-ID: 66c7328526dc365a158a73ed6c7d4eaf at test.example.com.
> Contact: <sip:192.168.2.20:5080;did=3eb.00abd186>.
> CSeq: 102 INVITE.
> Server: sbc_3.
> Content-Type: application/sdp.
> Content-Length: 269.
> .
> v=0.
> o=sbcsas 1384291552 1 IN IP4 34.34.12.23.
> s=sbcsas SIP STACK v1.0.
> c=IN IP4 34.34.12.23.
> t=0 0.
> m=audio 20770 RTP/AVP 18 101.
> a=rtpmap:18 G729/8000.
> a=rtpmap:101 telephone-event/8000.
> a=fmtp:18 annexb=no.
> a=fmtp:101 0-15.
> a=sendrecv.
> a=nortpproxy:yes.
>
>
>
> I have the full debug with embeded SIP trace if needed.
>
> Kind Regards,
>
> Nick.
More information about the Users
mailing list