[SR-Users] kamailio call problem
Jason Sia
jsia18 at gmail.com
Tue Jul 30 16:54:17 CEST 2013
Sorry, this test was done on a public server that's why it was showing
public IPs. I was trying out opensips and kamailio and same response for
both. Do you think this is a network firewall issue?
On Tue, Jul 30, 2013 at 2:31 PM, Gertjan Wolzak <g.wolzak at foize.com> wrote:
> Hello Jason,****
>
> ** **
>
> Well, as you can see now the error is:****
>
> ** **
>
> U 2013/07/29 18:24:03.328456 198.23.160.81:5060 -> 49.144.184.97:41998
> SIP/2.0 477 Send failed (477/TM).
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;received=49.144.184.97;branch=z9hG4bK-d8754z-1cfc096228010333-1---d8754z-;rport=41998.
> To: <sip:639195015475 at 198.23.160.81
> >;tag=eb0b3ccde0b882baee99bc071578cb61-d8d9.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 2 INVITE.
> Server: OpenSIPS (1.8.3-notls (x86_64/linux)).
> Content-Length: 0.****
>
> ** **
>
> But as I am not a guru at all and this is a Kamailio users mailing list
> and not an opensips list….****
>
> ** **
>
> I just googled the error, found that for Opensips and Kamailio it has
> something to do with not being able to make a tcp connection.****
>
> ** **
>
> So, check the port translations, make a tcpdump of wireshark dump and see
> if what is going wrong.****
>
> ** **
>
> You said that the clients and Kamailio were on the same lan, but from the
> logging you can see that you are on the internet…….****
>
> ** **
>
> Hope this helps a bit.****
>
> ** **
>
> Good luck.****
>
> ** **
>
> ** **
>
> *From:* sr-users-bounces at lists.sip-router.org [mailto:
> sr-users-bounces at lists.sip-router.org] *On Behalf Of *Jason Sia
> *Sent:* maandag 29 juli 2013 18:16
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] kamailio call problem****
>
> ** **
>
> Hi,****
>
> Thanks for the advice. Here is the ngrep logs:
>
> U 2013/07/29 18:23:52.994331 49.144.184.97:41998 -> 198.23.160.81:5060
> INVITE sip:639195015475 at 198.23.160.81 SIP/2.0.
> Via: SIP/2.0/UDP 192.168.0.107:41998;branch=****
>
> z9hG4bK-d8754z-2999840441d3d05a-1---d8754z-;rport.
> Max-Forwards: 70.
> Contact: <sip:639178864952 at 49.144.184.97:41998>.
> To: <sip:639195015475 at 198.23.160.81>.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 1 INVITE.
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO.
> Content-Type: application/sdp.
> Supported: replaces.
> User-Agent: X-Lite release 4.5.3 stamp 70576.
> Content-Length: 357.
> .
> v=0.
> o=- 1375107832761441 1 IN IP4 192.168.0.107.
> s=X-Lite 4 release 4.5.3 stamp 70576.
> c=IN IP4 192.168.0.107.
> t=0 0.
> m=audio 53084 RTP/AVP 123 9 0 8 97 100 98 101.
> a=rtpmap:123 opus/48000/2.
> a=fmtp:123 useinbandfec=1.
> a=rtpmap:97 speex/8000.
> a=rtpmap:100 speex/16000.
> a=rtpmap:98 ILBC/8000.
> a=rtpmap:101 telephone-event/8000.
> a=fmtp:101 0-15.
> a=sendrecv.
>
>
> U 2013/07/29 18:23:52.994422 198.23.160.81:5060 -> 49.144.184.97:41998
> SIP/2.0 407 Proxy Authentication Required.
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;received=49.144.184.97;branch=z9hG4bK-d8754z-2999840441d3d05a-1---d8754z-;rport=41998.
> To: <sip:639195015475 at 198.23.160.81
> >;tag=80403214130c49515b8f7d7842a4c119.ef65.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 1 INVITE.
> Proxy-Authenticate: Digest realm="198.23.160.81",
> nonce="51f67b16000000fae8c70592af760c78fa39cd43f84c1a6b".
> Server: OpenSIPS (1.8.3-notls (x86_64/linux)).
> Content-Length: 0.
> .
>
>
> U 2013/07/29 18:23:53.299025 49.144.184.97:41998 -> 198.23.160.81:5060
> ACK sip:639195015475 at 198.23.160.81 SIP/2.0.
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;branch=z9hG4bK-d8754z-2999840441d3d05a-1---d8754z-;rport.
> Max-Forwards: 70.
> To: <sip:639195015475 at 198.23.160.81
> >;tag=80403214130c49515b8f7d7842a4c119.ef65.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 1 ACK.
> Content-Length: 0.
> .
>
>
> U 2013/07/29 18:23:53.317842 49.144.184.97:41998 -> 198.23.160.81:5060
> INVITE sip:639195015475 at 198.23.160.81 SIP/2.0.
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;branch=z9hG4bK-d8754z-1cfc096228010333-1---d8754z-;rport.
> Max-Forwards: 70.
> Contact: <sip:639178864952 at 49.144.184.97:41998>.
> To: <sip:639195015475 at 198.23.160.81>.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 2 INVITE.
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO.
> Content-Type: application/sdp.
> Proxy-Authorization: Digest
> username="639178864952",realm="198.23.160.81",nonce="51f67b16000000fae8c70592af760c78fa39cd43f84c1a6b",uri="
> sip:639195015475 at 198.23.160.81
> ",response="1605e4e6b20dbbd6be5917c94dd3961e",algorithm=MD5.
> Supported: replaces.
> User-Agent: X-Lite release 4.5.3 stamp 70576.
> Content-Length: 357.
> .
> v=0.
> o=- 1375107832761441 1 IN IP4 192.168.0.107.
> s=X-Lite 4 release 4.5.3 stamp 70576.
> c=IN IP4 192.168.0.107.
> t=0 0.
> m=audio 53084 RTP/AVP 123 9 0 8 97 100 98 101.
> a=rtpmap:123 opus/48000/2.
> a=fmtp:123 useinbandfec=1.
> a=rtpmap:97 speex/8000.
> a=rtpmap:100 speex/16000.
> a=rtpmap:98 ILBC/8000.
> a=rtpmap:101 telephone-event/8000.
> a=fmtp:101 0-15.
> a=sendrecv.
>
>
> U 2013/07/29 18:23:53.318191 198.23.160.81:5060 -> 49.144.184.97:41998
> SIP/2.0 100 Giving a try.
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;received=49.144.184.97;branch=z9hG4bK-d8754z-1cfc096228010333-1---d8754z-;rport=41998.
> To: <sip:639195015475 at 198.23.160.81>.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 2 INVITE.
> Server: OpenSIPS (1.8.3-notls (x86_64/linux)).
> Content-Length: 0.
> .
>
>
> U 2013/07/29 18:24:03.328456 198.23.160.81:5060 -> 49.144.184.97:41998
> SIP/2.0 477 Send failed (477/TM).
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;received=49.144.184.97;branch=z9hG4bK-d8754z-1cfc096228010333-1---d8754z-;rport=41998.
> To: <sip:639195015475 at 198.23.160.81
> >;tag=eb0b3ccde0b882baee99bc071578cb61-d8d9.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 2 INVITE.
> Server: OpenSIPS (1.8.3-notls (x86_64/linux)).
> Content-Length: 0.
> .
>
>
> U 2013/07/29 18:24:03.582094 49.144.184.97:41998 -> 198.23.160.81:5060
> ACK sip:639195015475 at 198.23.160.81 SIP/2.0.
> Via: SIP/2.0/UDP 192.168.0.107:41998
> ;branch=z9hG4bK-d8754z-1cfc096228010333-1---d8754z-;rport.
> Max-Forwards: 70.
> To: <sip:639195015475 at 198.23.160.81
> >;tag=eb0b3ccde0b882baee99bc071578cb61-d8d9.
> From: "639178864952"<sip:639178864952 at 198.23.160.81>;tag=1b3b463c.
> Call-ID: NjhmYzk0ODZhNWVmOGE5MTU4ZWExM2Q5NjI1NDVhODg.
> CSeq: 2 ACK.
> Content-Length: 0.****
>
> ****
>
> ** **
>
>
> Thanks,
> Jason****
>
> ** **
>
> On Mon, Jul 29, 2013 at 3:33 PM, Gertjan Wolzak <g.wolzak at foize.com>
> wrote:****
>
> Hello Jason,****
>
> ****
>
> What you should do is on the Kamailio server do an ngrep, that
> information will make it possible for the people on the list to take a look
> and help you.****
>
> ****
>
> By only telling your experiences it is hard to help you.****
>
> ****
>
> Just give the command: ngrep –qt –W byline port 5060 and then do the
> test calls, so from android to xlite and vice versa.****
>
> ****
>
> Save the info and paste it in the case.****
>
> ****
>
> Good luck.****
>
> ****
>
> Gertjan****
>
> ****
>
> *From:* sr-users-bounces at lists.sip-router.org [mailto:
> sr-users-bounces at lists.sip-router.org] *On Behalf Of *Jason Sia
> *Sent:* zondag 28 juli 2013 10:52
> *To:* sr-users at lists.sip-router.org
> *Subject:* [SR-Users] kamailio call problem****
>
> ****
>
> Hi,****
>
> I installed kamailio v 3.1.6 rpm. I used the default configuration.
> Kamailio started. I have two clients one is an android phone using native
> sip client, and the other one x-lite. I can call x-lite to phone but not
> the other way around. When I restarted kamailio, I can call phone to
> x-lite but not the other way around. The first one I did when I restart
> kamailio will be the only leg that will be working, then I have to restart
> again if I want to do the reverse. Has anyone encountered this problem?
> How do I fix it? I'm on a LAN, kamailio server and the two clients are on
> the same LAN.****
>
> ****
>
> Thanks,
> Jason****
>
>
> _______________________________________________
> 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/20130730/927fa0d2/attachment-0001.html>
More information about the sr-users
mailing list