[SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
Sammy Govind
govoiper at gmail.com
Mon Jan 9 15:43:28 CET 2012
Hi again,
How are you taking traces on Kamailio+rtpproxy server !?
Since it has multiple interfaces and SIP packets maybe too big for default
packet length in capture so what i do is.
#tcpdump -i any -s 0 -w maycapture.pcap -vvvvv
-i any [listens to both interfaces for traffic]
-s 0 [let the length of each packet captured reach infinity :) ]
Also check for tcpdump params for IPv6 special flags if any.
Paste the new SIP traces.
Regards.
Sammy.
On Mon, Jan 9, 2012 at 7:36 PM, nunu abe <nunu_abe at yahoo.com> wrote:
> Thank you very much Sammy :)
>
> I am now better aquinted with rtpproxy, but my problem still exists. The
> rtpproxy server does infact try to do its job. It replaces the IN IP
> address by its own address everytime it forwards SIP INVITE messages but
> the callee UA does not respond. The wireshark output says that the packets
> are too long or unrecognised SIP header.
> Any ideas ???
>
> Thank you for your help?
>
> Regards
> Maedot
> *From:* Sammy Govind <govoiper at gmail.com>
> *To:* nunu abe <nunu_abe at yahoo.com>
> *Cc:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List <sr-users at lists.sip-router.org>
> *Sent:* Friday, January 6, 2012 12:02 PM
>
> *Subject:* Re: [SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
>
> Congrats so now RTPproxy issue has been resolved and Kamailio is saying
> that support for it has been enables.
> Next thing is ...ignore the reverse resolving of IPv6 IP !! thats not an
> issue at all for now.
>
> The error you are receiving is due to sip PUBLISH method ... that can be a
> bug in Kamailio or anything on which I can't comment any better than you.
>
> I hope some other gy take over the thread from here and see if this _IS_
> really an issue or not, if so why is this here then !!
>
> Regards,
> Sammy.
>
>
> On Fri, Jan 6, 2012 at 3:37 PM, nunu abe <nunu_abe at yahoo.com> wrote:
>
> Hi,
>
> I commented out the unix socket in the modparam as instructed and there is
> still no change.
>
> 1. The rtpproxy was listening to port 7722, but to make sure I stopped it
> and restarted it with the command:
> xxx at DualStackCS:~$ sudo netstat -pln |grep rtpp
> udp 0 0 127.0.0.1:7722 0.0.0.0:*
> 860/rtpproxy
>
> xxx at DualStackCS:~$ sudo /etc/init.d/rtpproxy restart
> Restarting RTP relay: rtpproxy.
>
> xxxxx at DualStackCS:~$ sudo netstat -pln |grep rtpp
> udp 0 0 127.0.0.1:7722 0.0.0.0:*
> 2303/rtpproxy
>
> xxxx at DualStackCS:~$ sudo /etc/init.d/rtpproxy stop
> Stopping RTP relay: rtpproxy.
>
> xxxxx at DualStackCS:~$ sudo netstat -pln |grep rtpp
> xxxxx at DualStackCS:~$ sudo rtpproxy -F -l 10.10.10.10 -6
> /3001:0:0:1::10 -s udp:127.0.0.1:7722
> xxxxx at DualStackCS:~$ sudo netstat -pln |grep rtpp
> udp 0 0 127.0.0.1:7722 0.0.0.0:*
> 2366/rtpproxy
>
> 2.Kamailio service started without error message but with this warning:
> 0(1549) WARNING: <core> [socket_info.c:1275]: WARNING: fix_hostname:
> could not rev. resolve 3001:0:0:1:0:0:0:10
>
> 16(2422) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child
> (11): nathelper
> 16(2422) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child
> (11): rtpproxy
> 15(2421) INFO: rtpproxy [rtpproxy.c:1415]: rtp proxy
> <udp:localhost:7722> found, support for it enabled
>
> 3.As soon as clients register, these errors appear in the logs
> (similar errors appear even more frequently while making a call, shown in
> the attachment):
> 7(2407) DEBUG: <core> [parser/msg_parser.c:630]: method: <PUBLISH>
> 7(2407) DEBUG: <core> [parser/msg_parser.c:632]: uri: <sip:300@
> [3001:0:0:1::10]>
> 7(2407) DEBUG: <core> [parser/msg_parser.c:634]: version: <SIP/2.0>
> 7(2407) DEBUG: <core> [parser/parse_via.c:1288]: Found param type 232,
> <branch> = <z9hG4bK3847>; state=16
> 7(2407) DEBUG: <core> [parser/parse_via.c:2563]: end of header reached,
> state=5
> 7(2407) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers: Via
> found, flags=2
> 7(2407) DEBUG: <core> [parser/msg_parser.c:517]: parse_headers: this is
> the first via
> 7(2407) DEBUG: <core> [receive.c:147]: After parse_msg...
> 7(2407) DEBUG: <core> [receive.c:188]: preparing to run routing scripts...
> 7(2407) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=464 a=6 n=route
> 7(2407) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=573 a=17 n=if
> 7(2407) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=568 a=26 n=mf_process_maxfwd_header
>
> 6(2406) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=744 a=26 n=is_method
> 6(2406) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=767 a=25 n=consume_credentials
> 6(2406) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=780 a=3 n=return
> 6(2406) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=489 a=26 n=remove_hf
> 6(2406) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=500 a=6 n=route
> 6(2406) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=704 a=27 n=sl_send_reply
>
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=467 a=6 n=route
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=789 a=17 n=if
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=789 a=57 n=force_rport
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=799 a=17 n=if
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=790 a=26 n=nat_uac_test
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=795 a=17 n=if
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=791 a=26 n=is_method
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=792 a=25 n=fix_nated_register
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=796 a=40 n=setflag
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=799 a=3 n=return
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=470 a=6 n=route
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=617 a=17 n=if
> 4(2458) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg]
> l=582 a=25 n=has_totag
>
> So still lost in this issue.
> Thanks for your help!
>
> Regards,
> Maedot
> *From:* Sammy Govind <govoiper at gmail.com>
> *To:* nunu abe <nunu_abe at yahoo.com>; SIP Router - Kamailio (OpenSER) and
> SIP Express Router (SER) - Users Mailing List <
> sr-users at lists.sip-router.org>
> *Sent:* Friday, January 6, 2012 10:06 AM
>
> *Subject:* Re: [SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
>
> Don't forget to change the modparams for RTPproxy as
>
> modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722")
> # modparam("rtpproxy", "rtpproxy_sock",
> "unix:/var/run/rtpproxy/rtpproxy.sock")
>
>
> On Fri, Jan 6, 2012 at 2:05 PM, Sammy Govind <govoiper at gmail.com> wrote:
>
> Hi,
>
> Kamailio is trying to communicate to RTproxy using port 7722 , execute
> the command
>
> # netstat -pln | grep rtpp
>
> and see if your rtpproxy is even listening on that interface, which it
> isn't for sure.
>
> No if above is true then stop rtpproxy and start rtpproxy using the b/m
> command
>
> #sudo rtpproxy -F -l 10.10.10.10 -6 /3001:0:0:1::10 -s udp:127.0.0.1:7722
>
> confirm using the netstat command that RTPproxy is indeed listening on
> 7722 port, if yes restart Kamailio and make sure you don't see kamailio
> complaining about not connecting to RTPproxy anymore.
>
>
> Regards,
> Sammy.
>
> On Fri, Jan 6, 2012 at 1:31 PM, nunu abe <nunu_abe at yahoo.com> wrote:
>
> Hi,
>
> I have already posted this message but it was sent only to Sammy Govind
> somehow, not to the mailing list. So I am posting it again to the list. I
> am sorry if this is double posting or if this is not the right way to do it.
>
> **Original message***
>
>
> Hi Sammy
> These are the params from my kamilio cfg file. Just a reminder, the
> whole cfg file is copied from the link:
> http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6, i just edited the
> IP addresses and DB_URL line to fit my settings.
> #!ifdef WITH_NAT
> # ----- rtpproxy params -----
> # modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722")
> modparam("rtpproxy", "rtpproxy_sock",
> "unix:/var/run/rtpproxy/rtpproxy.sock")
>
> # ----- nathelper params -----
> modparam("nathelper", "natping_interval", 30)
> modparam("nathelper", "ping_nated_only", 1)
> modparam("nathelper", "sipping_bflag", FLB_NATSIPPING)
> modparam("nathelper", "sipping_from", "sip:pinger at kamailio.org")
>
> # params needed for NAT traversal in other modules
> modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)")
> modparam("usrloc", "nat_bflag", FLB_NATB)
> #!endif
> I have tried to use both unix and UDP sockets each at a time.I removed the
> square braces from the IP addresses in the rtpproxy default files and its
> no more complainig about the "rtpproxy: setbindhost: No addressassociated with hostname"
> but still have the same messages in the logs.
> Thank you four your help.
> Regards,
> Maedot
>
> *From:* Sammy Govind <govoiper at gmail.com>
>
> *To:* nunu abe <nunu_abe at yahoo.com>; SIP Router - Kamailio (OpenSER) and
> SIP Express Router (SER) - Users Mailing List <
> sr-users at lists.sip-router.org>
> *Sent:* Thursday, January 5, 2012 8:13 PM
>
> *Subject:* Re: [SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
>
> hi,
>
> quick look at your logs,
>
> 14(1596) ERROR: rtpproxy [rtpproxy.c:1466]: can't connect to RTP proxy
> 15(1597) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (10): nathelper
> 14(1596) ERROR: rtpproxy [rtpproxy.c:1538]: proxy <unix:/var/run/rtpproxy/rtpproxy.sock> does not respond, disable it
> 5(1584) DEBUG: db_mysql [km_my_con.c:123]: server version is 5.1.41-3ubuntu12.10
> 14(1596) WARNING: rtpproxy [rtpproxy.c:1395]: can't get version of the RTP proxy
> 14(1596) WARNING: rtpproxy [rtpproxy.c:1432]: support for RTP proxy <unix:/var/run/rtpproxy/rtpproxy.sock> has been disabled temporarily
> 14(1596) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (9): debugger
> 5(1584) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (5): nathelper
> 14(1596) DEBUG: debugger [debugger_mod.c:124]: rank is (9)
> 5(1584) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (5): rtpproxy
> 5(1584) ERROR: rtpproxy [rtpproxy.c:1466]: can't connect to RTP proxy
> 5(1584) ERROR: rtpproxy [rtpproxy.c:1538]: proxy <unix:/var/run/rtpproxy/rtpproxy.sock> does not respond, disable it
> 5(1584) WARNING: rtpproxy [rtpproxy.c:1395]: can't get version of the RTP proxy
> 5(1584) WARNING: rtpproxy [rtpproxy.c:1432]: support for RTP proxy <unix:/var/run/rtpproxy/rtpproxy.sock> has been disabled temporarily
> 5(1584) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (5): debugger
> 5(1584) DEBUG: debugger [debugger_mod.c:124]: rank is (5)
> 15(1597) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (10): rtpproxy
> 15(1597) ERROR: rtpproxy [rtpproxy.c:1466]: can't connect to RTP proxy
> 15(1597) ERROR: rtpproxy [rtpproxy.c:1538]: proxy <unix:/var/run/rtpproxy/rtpproxy.sock> does not respond, disable it
> 15(1597) WARNING: rtpproxy [rtpproxy.c:1395]: can't get version of the RTP proxy
> 15(1597) WARNING: rtpproxy [rtpproxy.c:1432]: support for RTP proxy <unix:/var/run/rtpproxy/rtpproxy.sock> has been disabled temporarily
> 15(1597) DEBUG: <core> [sr_module.c:892]: DEBUG: init_mod_child (10): debugger
>
>
>
> paste the rtpproxy/nathelper module params lines which are in your
> kamailio.cfg.
>
> regards,
> sammy
>
>
> On Wed, Jan 4, 2012 at 7:59 PM, nunu abe <nunu_abe at yahoo.com> wrote:
>
> Thank you Sammy for noticing :)
>
> Now I have a bit of different but same problem. After the earlier posting
> the message I decided to start everything from scratch and I installed
> everything new.
> But I still have problem. The rtpproxy server is not working, it fails to
> replace the IP address of the sender in the SDP and hence there is no RTP
> communication.
> These are the steps I followed:
>
>
> 1. Freshly installed kamailio 3.2.1 on Kubuntu from GIT
>
> 2. Installed mysql server
>
> 4. installed rtpproxy, changed its user to be kamailio.
>
> 3.Copied the provided kamailio.cfg file from the link and edited the IP
> addresses and the DBURL to reflect my settings
>
> 4. Uncommented the Control socket line and added these lines in the
> /etc/default/rtpproxy file
> CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
> ADDR_IPV4=[10.10.10.10]
> ADDR_IPV6=[3001:0:0:1::10]
> EXTRA_OPTS="-l {ADDR_IPV4} -6 /{ADDR_IPV6}"
>
> *** I aslso tried without adding the last three lines, but it made no
> difference.***
>
> 5. Started rtpproxy in a bridge mode
>
> xxxx at DualStackCS:~$ sudo rtpproxy -F -l 10.10.10.10 -6 /3001:0:0:1::10
> *** I have also tried to start it this way :xxxx at DualStackCS:~$ sudo
> rtpproxy -F -l 10.10.10.10 -6 /3001:0:0:1::10 -s
> unix:/var/run/rtpproxy/rtpproxy.sock - but no difference****
>
> xxxx at DualStackCS:~$ ps aux|grep rtpproxy
> root 1522 0.0 0.0 11384 696 ? Ssl 15:31 0:00 rtpproxy
> -F -l 10.10.10.10 -6 3001:0:0:1::10
> xxxx 1528 0.0 0.0 3324 804 pts/1 S+ 15:31 0:00 grep
> --color=auto rtpproxy
>
> xxxxx at DualStackCS:~$ sudo /etc/init.d/kamailio start
>
>
> 6. Started kamailio
> @DualStackCS:~$ sudo /etc/init.d/kamailio restart
>
> I have attached the log file.
>
> Many thanks for your help.
>
> Regards,
>
> Maedot
>
> *From:* Sammy Govind <govoiper at gmail.com>
> *To:* miconda at gmail.com; SIP Router - Kamailio (OpenSER) and SIP Express
> Router (SER) - Users Mailing List <sr-users at lists.sip-router.org>
> *Sent:* Tuesday, January 3, 2012 2:04 PM
> *Subject:* Re: [SR-Users] RTPproxy on Kamailio 3.2.1 difficulty.
>
> Hi,
>
> I had a good laugh when I read the reply, but going through the whole
> thread again I found this:
> " It displays the same message even when I replace ADDR_IPV4 and
> ADDR_IPV6 with IP addresses. "
>
> So there _IS_ some problem here.
>
> Nuno, can you please copy paste the exact command which you executing,
> plus paste the logs,
>
> --
> Regards,
> Sammy.
>
> On Tue, Jan 3, 2012 at 2:22 PM, Daniel-Constantin Mierla <
> miconda at gmail.com> wrote:
>
> Hello,
>
> the ADDR_IPV4 and ADDR_IPV6 have to be replaced with real IP addresses
> that you have on the system runnin RTPProxy.
>
> Cheers,
> Daniel
>
>
> On 1/3/12 8:56 AM, nunu abe wrote:
>
> Dear Daniel,
> Greetings and Happy New year to you all! I would like to thank you very
> much for your detailed and well structured tutorials on Kamailio. I am
> resending this email as I sent the earlier one before I was a member of the
> mailing list and I thought it may have been sent to the spam folder. If not
> then, I apologize for double posting.
> I was trying to design a similar scenario like the one " Run your own
> SIP VoIP service on both IPv4 and IPv6 " as explained on Asipto web-page(
> http://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6). However I ran
> into difficulties with rtpproxy. The proxy is not routing media packets
> as it should. I followed the instruction regarding the kamailio.cfg file
> and edited the necessary lines according to my settings. I think my problem
> comes from setting up the rtpproxy.
> 1. I edited the /etc/default/rtpproxy file. i.e. I uncommented the line
> - CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
> 2. I started the rtpproxy with this command: rtpproxy -F -l ADDR_IPV4 -6
> /ADDR_IPV6 . However, after this command the system returns the message : rtpproxy:
> setbindhost: No address associated with hostname
> It displays the same message even when I replace ADDR_IPV4 and ADDR_IPV6
> with IP addresses.
>
> 3. I have also tried using the udp socket:- CONTROL_SOCK=udp:
> 127.0.0.1:22222, of course I have replaced the unix socket by this udp
> socket in the kamilio.cfg file.
> So my question is, what did I do wrong with the settings that SIP
> messages are traversing normal from IPv4 client to IPv6 client and vice
> versa but media files(RTP packets) are not? The rtpproxy receives the media
> files from one client but fails to forward them to the other client.
> Thanks for your help.
> Maedot
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at 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 at 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 at 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 at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120109/515ac764/attachment-0001.htm>
More information about the sr-users
mailing list