Hmmm..have you changed the UACs on both side or at least the one that is problematic, like Juha said.
Hi AllThanks for your kind answer.The call flow looks as belowI have two doubts here1. My UA is just behind the Modem, and in Kamailio config file I have enabled WITH_NAT, will this lead to any kind of problem2. In kamailio proxy I am using force_rtp_proxy and unforce_rtp_proxy instead of rtpproxy_offer/rtpproxy_answer. Not sure whats the corresponding api for unforce_rtp_proxy.will this lead to any issues.RegardsAustin.
INVITE sip:919731573290@134.121.32.130:5060 SIP/2.0Via: SIP/2.0/UDP 192.168.1.2:53489;rport;branch=z9hG4bKPj0052793130024dda88418cf7a392b7aeMax-Forwards: 70From: sip:austin@134.121.32.130;tag=8c2e350c064e417c96bda1378470fd46Contact: <sip:austin@192.168.1.2:53489;ob>Call-ID: b637fa62393a45a0a58633c1a8f43a86CSeq: 14417 INVITERoute: <sip:134.33.8.138:5060;lr>Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONSSupported: replaces, 100rel, timer, norefersubSession-Expires: 1800Min-SE: 90User-Agent: VoIP Client v1.01Proxy-Authorization: Digest username="austin", realm="VoipSwitch", nonce="131819433109160428210053141040", uri="sip:919731573290@134.121.32.130:5060", response="935c3130fe07e2413ccf127d5fb6b9d1"Content-Type: application/sdpContent-Length: 271v=0o=- 3527202931 3527202931 IN IP4 192.168.1.2s=pjmediac=IN IP4 192.168.1.2t=0 0a=X-nat:0m=audio 4000 RTP/AVP 18 4 96a=rtcp:4001 IN IP4 192.168.1.2a=rtpmap:18 G729/8000a=rtpmap:4 G723/8000a=sendrecva=rtpmap:96 telephone-event/8000a=fmtp:96 0-15SIP/2.0 100 tryingVia: SIP/2.0/UDP 192.168.1.2:53489;rport=13341;branch=z9hG4bKPj0052793130024dda88418cf7a392b7ae;received=122.178.237.67From: sip:austin@134.121.32.130;tag=8c2e350c064e417c96bda1378470fd46Call-ID: b637fa62393a45a0a58633c1a8f43a86CSeq: 14417 INVITEServer: kamailio (3.1.5 (i386/linux))Content-Length: 0SIP/2.0 183 Session ProgressCSeq: 14417 INVITEVia: SIP/2.0/UDP 192.168.1.2:53489;branch=z9hG4bKPj0052793130024dda88418cf7a392b7aeFrom: sip:austin@134.121.32.130;tag=8c2e350c064e417c96bda1378470fd46Call-ID: b637fa62393a45a0a58633c1a8f43a86To: sip:919731573290@134.121.32.130;tag=09100511163117092280006157Contact: <sip:134.121.32.130:5060;transport=udp>Content-Type: application/sdpContent-Length: 241Record-Route: <sip:134.33.8.138;lr=on;nat=yes>v=0o=VoipSwitch 6156 7156 IN IP4 134.33.8.138s=VoipSIPi=Audio Sessionc=IN IP4 134.33.8.138t=0 0m=audio 46976 RTP/AVP 18 96a=rtpmap:18 G729/8000/1a=rtpmap:96 telephone-event/8000a=fmtp:96 0-15a=sendrecva=nortpproxy:yesSIP/2.0 200 OKCSeq: 14417 INVITEVia: SIP/2.0/UDP 192.168.1.2:53489;branch=z9hG4bKPj0052793130024dda88418cf7a392b7aeFrom: sip:austin@134.121.32.130;tag=8c2e350c064e417c96bda1378470fd46Call-ID: b637fa62393a45a0a58633c1a8f43a86To: sip:919731573290@134.121.32.130;tag=09100511163117092280006157Contact: <sip:134.121.32.130:5060;transport=udp>Content-Type: application/sdpContent-Length: 241Record-Route: <sip:134.33.8.138;lr=on;nat=yes>v=0o=VoipSwitch 6156 7156 IN IP4 134.33.8.138s=VoipSIPi=Audio Sessionc=IN IP4 134.33.8.138t=0 0m=audio 46976 RTP/AVP 18 96a=rtpmap:18 G729/8000/1a=rtpmap:96 telephone-event/8000a=fmtp:96 0-15a=sendrecva=nortpproxy:yesACK sip:134.121.32.130:5060;transport=udp SIP/2.0Via: SIP/2.0/UDP 192.168.1.2:53489;rport;branch=z9hG4bKPj73092b1de9aa4d4498adac484efacfdaMax-Forwards: 70From: sip:austin@134.121.32.130;tag=8c2e350c064e417c96bda1378470fd46To: sip:919731573290@134.121.32.130;tag=09100511163117092280006157Call-ID: b637fa62393a45a0a58633c1a8f43a86CSeq: 14417 ACKRoute: <sip:134.33.8.138;lr;nat=yes>Content-Length: 0BYE sip:austin@122.178.237.67:13341;ob SIP/2.0Max-Forwards: 10CSeq: 1 BYEVia: SIP/2.0/UDP 134.33.8.138;branch=z9hG4bK029.52d62945.0Via: SIP/2.0/UDP 134.121.32.130:5060;rport=5060;branch=z9hG4bK091005111656091709252938From: sip:919731573290@134.121.32.130;tag=09100511163117092280006157Call-ID: b637fa62393a45a0a58633c1a8f43a86To: sip:austin@134.121.32.130;tag=8c2e350c064e417c96bda1378470fd46Content-Length: 0SIP/2.0 200 OKVia: SIP/2.0/UDP 134.33.8.138;received=134.33.8.138;branch=z9hG4bK029.52d62945.0Via: SIP/2.0/UDP 134.121.32.130:5060;rport=5060;branch=z9hG4bK091005111656091709252938Call-ID: b637fa62393a45a0a58633c1a8f43a86From: <sip:919731573290@134.121.32.130>;tag=09100511163117092280006157To: <sip:austin@134.121.32.130>;tag=8c2e350c064e417c96bda1378470fd46CSeq: 1 BYEContent-Length: 0
On Sun, Oct 9, 2011 at 11:50 AM, Sammy Govind <govoiper@gmail.com> wrote:
Hey,Can you send in the SIP/SDP invites. I suspect the codecs issue here.--Regards,Sammy
On Sun, Oct 9, 2011 at 8:57 AM, Austin Einter <austin.einter@gmail.com> wrote:HiI am using Kamailio 3.1.5 . I am using RTP proxy also.I have used default kamailio.cfg.sample fiile , and just added line #!define WITH_NAT.I have another Main proxy. I wanted all my signalling and media packets should just pass through machine where Kamailio and RTP proxy are running.With this I found, call is established, all signalling and media packets are passing through kamailio / rtp-proxy.So far so good.One way audio stream (from called party to calling party) quality is good.The other audio stream (from calling party to called party is very bad.Did anybody face this issue? Please help me to sort out this issue audio quality issue.RegardsAustin_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users