hello;
    you can start rtpproxy like "rtpproxy -l 120.76.118.128 -s udp:127.0.0.1:7722 -F -m 10000 -M 20000 -d DBUG:LOG_DAEMON"  and check message log.

After authantication ,  test only INVITE packets with nat_uac_client(8) , rtpproxy_manage can handle INVITE packet with "co" flags ( rtpproxy_manage("co") )  as specified on docs.
you can check 200 OK packet with t_on_reply packets. the same logic can you handle sdp packets.

Cheers


2016-05-06 13:14 tarihinde 王欣鑫 [via SIP Router] yazdı:
Hello ycaner!

I download rtpproxy-2.0-RC1.tar.gz from https://github.com/winer632/rtpproxy/releases/tag/V2.0-RC1
and did the following command:

tar -xzvf rtpproxy-2.0-RC1.tar.gz
cd rtpproxy-2.0-RC1
./configure
make all
make install

Then I start rtpproxy with this command:

rtpproxy -l 120.76.118.128 -s udp:localhost:7722


Then I edit kamailio.cfg in PCSCF module like this(added this lineloadmodule "rtpproxy" and modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")  )


#!ifdef WITH_NAT
loadmodule "path"
loadmodule "rtpengine"
loadmodule "rtpproxy"
loadmodule "nathelper"
#!endif

#!ifdef WITH_NAT
# ----- rtpproxy-ng params -----
#modparam("rtpengine", "rtpengine_sock", RTPPROXY_ADDRESS)
#modparam("path", "use_received", 1)
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
#!endif


Next, I register a real number(18616278715) in China unicom's IMS , this step was success.Then call another real number 18019398639, no phone ringing, but failed with "Status-Line: SIP/2.0 407 Proxy Authentication Required". Before I add rtpproxy, there is no 407 error.

5060_unicom_407_error.pcap

 Before I add rtpproxy, I can hear the callee phone ringing, and the SIP route is like this:

5060_unicom.pcap

Am I doing wrong with rtpproxy? Maybe the problem is not here?



If you reply to this email, your message will be added to the discussion below:
http://sip-router.1086192.n5.nabble.com/User-offline-tp148166p148198.html
To unsubscribe from User offline, click here.
NAML

--


View this message in context: Re: User offline
Sent from the Users mailing list archive at Nabble.com.