Hello,
We have setup kamalio at server and it is working at some DNS with call/chat.
At some IP chat is working but when we call then it is not working. At some DNS(Net IP) it is working .
What can be problem at server?
Following is login for SIP test user:
tester1@23.253.110.48
123456
Host IP : 23.253.110.48
I have attached mu kamalio config file.
Let me know what we need to change at config file or server
Thanks
Hello,
look at the sip traffic on server to see if it is forwarded or not, and if yes, where. You can use ngrep, like:
ngrep -d any -qt -W byline "sip" port 5060
Also, check your syslog file to see if any error message is printed there.
It is not possible to guess what a fix would be if the real issue is not known.
Cheers, Daniel
On 19/03/15 09:59, Yogendra Gupta wrote:
Hello,
We have setup kamalio at server and it is working at some DNS with call/chat.
At some IP chat is working but when we call then it is not working. At some DNS(Net IP) it is working .
What can be problem at server?
Following is login for SIP test user:
tester1@23.253.110.48
123456
Host IP : 23.253.110.48
I have attached mu kamalio config file.
Let me know what we need to change at config file or server
Thanks
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
Hello,
Thanks for nice support.
When we call to test2 user and run this command at server
ngrep -d any -qt -W byline "sip" port 5060
then we found following response at server:
--------
U 2015/03/19 10:34:19.151351 202.157.76.21:62838 -> 23.253.110.48:5060
OPTIONS sip:23.253.110.48 SIP/2.0.
Call-ID: 35a382b70612890608da333133a632ab@0:0:0:0:0:0:0:0.
CSeq: 720 OPTIONS.
From: "test2" sip:test2@23.253.110.48;tag=7d797c77.
To: "test2" sip:test2@23.253.110.48.
Via: SIP/2.0/UDP 192.168.0.33:5060;branch=z9hG4bK-333435-c6ef476f117e9956b22c4fe20c38b5bb.
Max-Forwards: 70.
Contact: "test2" sip:test2@192.168.0.33:5060;transport=udp;registering_acc=23_253_110_48.
User-Agent: Jitsi2.5.5065Linux.
Allow: INFO,OPTIONS,MESSAGE,BYE,REFER,SUBSCRIBE,ACK,CANCEL,PUBLISH,NOTIFY,INVITE.
Allow-Events: refer.
Content-Length: 0.
.
U 2015/03/19 10:34:19.151616 23.253.110.48:5060 -> 202.157.76.21:62838
SIP/2.0 407 Proxy Authentication Required.
Call-ID: 35a382b70612890608da333133a632ab@0:0:0:0:0:0:0:0.
CSeq: 720 OPTIONS.
From: "test2" sip:test2@23.253.110.48;tag=7d797c77.
To: "test2" sip:test2@23.253.110.48;tag=b27e1a1d33761e85846fc98f5f3a7e58.5cf7.
Via: SIP/2.0/UDP 192.168.0.33:5060;branch=z9hG4bK-333435-c6ef476f117e9956b22c4fe20c38b5bb;rpo rt=62838;received=202.157.76.21.
Proxy-Authenticate: Digest realm="23.253.110.48", nonce="VQqnV1UKpitZOpmcEcEnk6XoUjE5xoTD".
Server: kamailio (4.1.7 (x86_64/linux)).
Content-Length: 0.
U 2015/03/19 10:34:25.691644 117.215.244.16:63347 -> 23.253.110.48:5060
OPTIONS sip:23.253.110.48 SIP/2.0.
Call-ID: 652528c610202910b534cc35b7a0e6f5@0:0:0:0:0:0:0:0.
CSeq: 371 OPTIONS.
From: "tester1" sip:tester1@23.253.110.48;tag=8f781308.
To: "tester1" sip:tester1@23.253.110.48.
Via: SIP/2.0/UDP 192.168.0.217:5060;branch=z9hG4bK-343938-1337a86e177bad29dc2bb31c99a5335a.
Max-Forwards: 70.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Allow: INFO,UPDATE,OPTIONS,MESSAGE,BYE,REFER,SUBSCRIBE,ACK,CANCEL,PUBLISH,NOTIFY,IN VITE.
Allow-Events: refer.
Content-Length: 0.
.
U 2015/03/19 10:34:25.691899 23.253.110.48:5060 -> 117.215.244.16:63347
SIP/2.0 407 Proxy Authentication Required.
Call-ID: 652528c610202910b534cc35b7a0e6f5@0:0:0:0:0:0:0:0.
CSeq: 371 OPTIONS.
From: "tester1" sip:tester1@23.253.110.48;tag=8f781308.
To: "tester1" sip:tester1@23.253.110.48;tag=b27e1a1d33761e85846fc98f5f3a7e58.d6e2.
Via: SIP/2.0/UDP 192.168.0.217:5060;branch=z9hG4bK-343938-1337a86e177bad29dc2bb31c99a5335a;rp ort=63347;received=117.215.244.16.
Proxy-Authenticate: Digest realm="23.253.110.48", nonce="VQqnXVUKpjHpaaepMRRwl7GlLf5XnOUJ".
Server: kamailio (4.1.7 (x86_64/linux)).
Content-Length: 0.
I have also downloaded syslog at same time and did not get any error about SIP
-------
Mar 19 06:39:01 telezang-app CRON[32320]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 07:09:01 telezang-app CRON[1839]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 07:17:01 telezang-app CRON[2273]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 19 07:39:01 telezang-app CRON[3520]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 07:57:05 telezang-app kernel: [1297024.377220] Bluetooth: Core ver 2.17
Mar 19 07:57:05 telezang-app kernel: [1297024.377241] NET: Registered protocol family 31
Mar 19 07:57:05 telezang-app kernel: [1297024.377243] Bluetooth: HCI device and connection manager initialized
Mar 19 07:57:05 telezang-app kernel: [1297024.377256] Bluetooth: HCI socket layer initialized
Mar 19 07:57:05 telezang-app kernel: [1297024.377258] Bluetooth: L2CAP socket layer initialized
Mar 19 07:57:05 telezang-app kernel: [1297024.377262] Bluetooth: SCO socket layer initialized
Mar 19 07:57:05 telezang-app kernel: [1297024.380356] Netfilter messages via NETLINK v0.30.
Mar 19 08:09:01 telezang-app CRON[5273]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 08:17:01 telezang-app CRON[5708]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 19 08:39:01 telezang-app CRON[6920]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 09:09:01 telezang-app CRON[8629]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 09:17:01 telezang-app CRON[9066]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 19 09:39:01 telezang-app CRON[10422]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 10:09:01 telezang-app CRON[12294]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Mar 19 10:17:01 telezang-app CRON[12789]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Let me know what it has error.
Thanks
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, March 19, 2015 3:31 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamalio call issue
Hello,
look at the sip traffic on server to see if it is forwarded or not, and if yes, where. You can use ngrep, like:
ngrep -d any -qt -W byline "sip" port 5060
Also, check your syslog file to see if any error message is printed there.
It is not possible to guess what a fix would be if the real issue is not known.
Cheers, Daniel
On 19/03/15 09:59, Yogendra Gupta wrote:
Hello,
We have setup kamalio at server and it is working at some DNS with call/chat.
At some IP chat is working but when we call then it is not working. At some DNS(Net IP) it is working .
What can be problem at server?
Following is login for SIP test user:
tester1@23.253.110.48
123456
Host IP : 23.253.110.48
I have attached mu kamalio config file.
Let me know what we need to change at config file or server
Thanks
_______________________________________________ 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
Hello,
OPTIONS is not the request for initiating the calls, that is INVITE. You would need to know SIP a bit in order to be able to understand and configure Kamailio.
If you don't see any INVITE on kamailo server via ngrep when you call, then the issue is on client side or there is a firewall dropping it.
Cheers, Daniel
On 19/03/15 11:39, Yogendra Gupta wrote:
Hello,
Thanks for nice support.
When we call to test2 user and run this command at server
ngrep -d any -qt -W byline "sip" port 5060
then we found following response at server:
Hello,
When I am calling with other SIP user then I did not see any INVITE . that have issue with DNS.
If we call with different DNS that is working fine then we see INVITE option like
U 2015/03/19 12:39:01.744616 117.215.244.16:63380 -> 23.253.110.48:5060
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: d83c4bc1e75e54df5ebd06b74f9089ef@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=ef809ce0.
To: sip:tester2@23.253.110.48;tag=23a5eaea.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKa1a3.21d8ef51bac2678fc26eca5975ae7b00.0,SIP/2.0/ UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-6f1017bcd9e693a4959717c9eabdc26e.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 12:39:01.744870 23.253.110.48:5060 -> 115.252.208.170:62554
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: d83c4bc1e75e54df5ebd06b74f9089ef@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=ef809ce0.
To: sip:tester2@23.253.110.48;tag=23a5eaea.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-6f1017bcd9e693a4959717c9eabdc26e.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48; alias=117.215.244.16~63380~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
Can you tell me what can be issue of firewall dropping?
When I checked at server firewall:
sudo ufw status
Status: inactive
Let me know what can be other issue for it..
Thanks
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, March 19, 2015 5:50 PM To: Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Kamalio call issue
Hello,
OPTIONS is not the request for initiating the calls, that is INVITE. You would need to know SIP a bit in order to be able to understand and configure Kamailio.
If you don't see any INVITE on kamailo server via ngrep when you call, then the issue is on client side or there is a firewall dropping it.
Cheers, Daniel
On 19/03/15 11:39, Yogendra Gupta wrote:
Hello,
Thanks for nice support.
When we call to test2 user and run this command at server
ngrep -d any -qt -W byline "sip" port 5060
then we found following response at server:
These are replies to INVITE requests, but if you see them, the INVITE passed through the server as well.
If you are not aware of a firewall, then perhaps you don't have one unless is a default installation with it enabled or one on the network.
I suggest you do sip tracing on the client machine to see if the invite requests leave to the proper IP.
Ultimately can be also a problem caused by a NAT router with ALG, if the client is behind such device.
Cheers, Daniel
On 19/03/15 13:50, Yogendra Gupta wrote:
Hello,
When I am calling with other SIP user then I did not see any INVITE . that have issue with DNS.
If we call with different DNS that is working fine then we see INVITE option like
U 2015/03/19 12:39:01.744616 117.215.244.16:63380 -> 23.253.110.48:5060
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: d83c4bc1e75e54df5ebd06b74f9089ef@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=ef809ce0.
To: sip:tester2@23.253.110.48;tag=23a5eaea.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKa1a3.21d8ef51bac2678fc26eca5975ae7b00.0,SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-343938-6f1017bcd9e693a4959717c9eabdc26e.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 12:39:01.744870 23.253.110.48:5060 -> 115.252.208.170:62554
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: d83c4bc1e75e54df5ebd06b74f9089ef@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=ef809ce0.
To: sip:tester2@23.253.110.48;tag=23a5eaea.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-343938-6f1017bcd9e693a4959717c9eabdc26e.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48;alias=117.215.244.16~63380~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
Can you tell me what can be issue of firewall dropping?
When I checked at server firewall:
sudo ufw status
Status: inactive
Let me know what can be other issue for it..
Thanks
*From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Sent:* Thursday, March 19, 2015 5:50 PM *To:* Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' *Subject:* Re: [SR-Users] Kamalio call issue
Hello,
OPTIONS is not the request for initiating the calls, that is INVITE. You would need to know SIP a bit in order to be able to understand and configure Kamailio.
If you don't see any INVITE on kamailo server via ngrep when you call, then the issue is on client side or there is a firewall dropping it.
Cheers, Daniel
On 19/03/15 11:39, Yogendra Gupta wrote:
Hello, Thanks for nice support. When we call to test2 user and run this command at server ngrep -d any -qt -W byline "sip" port 5060 then we found following response at server:-- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com
Hello,
When we can change our DNS IP then it works with following :
U 2015/03/20 10:06:06.504009 23.253.110.48:5060 -> 202.157.76.21:64051
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 SIP/2.0.
Call-ID: 143610160aa023568302b9c999b79f45@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bK7.601b877c92120368c17b3c0da0802af6.0.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=63789;received=202.157.76.21;branch=z9hG4bK-353035- 5aa153400d9ce60dfc573738a4b55232.
From: "tester1" sip:tester1@23.253.110.48;tag=3fdb1d0f.
To: "tester2" sip:tester2@23.253.110.48;tag=31532119.
Max-Forwards: 69.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48; alias=202.157.76.21~63789~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
But when we used another DNS IP (internet) and call then it showing only initialize..
If it has firewall issue then it will not work at all DNS IPs.
I have attached before my config file for kamalio.
Can you tell me what can be issue that it works at some DNS IP and not at all?
Thanks
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 20, 2015 2:14 AM To: Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Kamalio call issue
These are replies to INVITE requests, but if you see them, the INVITE passed through the server as well.
If you are not aware of a firewall, then perhaps you don't have one unless is a default installation with it enabled or one on the network.
I suggest you do sip tracing on the client machine to see if the invite requests leave to the proper IP.
Ultimately can be also a problem caused by a NAT router with ALG, if the client is behind such device.
Cheers, Daniel
On 19/03/15 13:50, Yogendra Gupta wrote:
Hello,
When I am calling with other SIP user then I did not see any INVITE . that have issue with DNS.
If we call with different DNS that is working fine then we see INVITE option like
U 2015/03/19 12:39:01.744616 117.215.244.16:63380 -> 23.253.110.48:5060
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: d83c4bc1e75e54df5ebd06b74f9089ef@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48 sip:tester1@23.253.110.48;tag=ef809ce0.
To: sip:tester2@23.253.110.48 sip:tester2@23.253.110.48;tag=23a5eaea.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKa1a3.21d8ef51bac2678fc26eca5975ae7b00.0,SIP/2.0/ UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-6f1017bcd9e693a4959717c9eabdc26e.
Record-Route: sip:23.253.110.48;lr=on;nat=yes sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 12:39:01.744870 23.253.110.48:5060 -> 115.252.208.170:62554
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: d83c4bc1e75e54df5ebd06b74f9089ef@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48 sip:tester1@23.253.110.48;tag=ef809ce0.
To: sip:tester2@23.253.110.48 sip:tester2@23.253.110.48;tag=23a5eaea.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-6f1017bcd9e693a4959717c9eabdc26e.
Record-Route: sip:23.253.110.48;lr=on;nat=yes sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48; alias=117.215.244.16~63380~1 sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48; alias=117.215.244.16~63380~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
Can you tell me what can be issue of firewall dropping?
When I checked at server firewall:
sudo ufw status
Status: inactive
Let me know what can be other issue for it..
Thanks
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, March 19, 2015 5:50 PM To: Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Kamalio call issue
Hello,
OPTIONS is not the request for initiating the calls, that is INVITE. You would need to know SIP a bit in order to be able to understand and configure Kamailio.
If you don't see any INVITE on kamailo server via ngrep when you call, then the issue is on client side or there is a firewall dropping it.
Cheers, Daniel
On 19/03/15 11:39, Yogendra Gupta wrote:
Hello,
Thanks for nice support.
When we call to test2 user and run this command at server
ngrep -d any -qt -W byline "sip" port 5060
then we found following response at server:
Hello,
again, if the SIP messages don't get to kamailio box, then the problem is on client side, not on server side.
If the request gets to kamailio and cannot do dns requests or they don't resolve, you will see a sip reply from kamailio.
There is not an issue that can be revealed by the config of kamailio. On the client side, try to use tools like host, dig and see what happens with dns requests. Also, use there ngrep to see if there are sip packets sent out of that box.
Cheers, Daniel
On 20/03/15 11:20, Yogendra Gupta wrote:
Hello,
When we can change our DNS IP then it works with following :
U 2015/03/20 10:06:06.504009 23.253.110.48:5060 -> 202.157.76.21:64051
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48SIP/2.0.
Call-ID: 143610160aa023568302b9c999b79f45@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bK7.601b877c92120368c17b3c0da0802af6.0.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=63789;received=202.157.76.21;branch=z9hG4bK-353035-5aa153400d9ce60dfc573738a4b55232.
From: "tester1" sip:tester1@23.253.110.48;tag=3fdb1d0f.
To: "tester2" sip:tester2@23.253.110.48;tag=31532119.
Max-Forwards: 69.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48;alias=202.157.76.21~63789~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
But when we used another DNS IP (internet) and call then it showing only initialize..
If it has firewall issue then it will not work at all DNS IPs.
I have attached before my config file for kamalio.
Can you tell me what can be issue that it works at some DNS IP and not at all?
Thanks
*From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Sent:* Friday, March 20, 2015 2:14 AM *To:* Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' *Subject:* Re: [SR-Users] Kamalio call issue
These are replies to INVITE requests, but if you see them, the INVITE passed through the server as well.
If you are not aware of a firewall, then perhaps you don't have one unless is a default installation with it enabled or one on the network.
I suggest you do sip tracing on the client machine to see if the invite requests leave to the proper IP.
Ultimately can be also a problem caused by a NAT router with ALG, if the client is behind such device.
Cheers, Daniel
Hello,
Thanks for nice support.
When kamalio is not working at some DNS with audio call then how we can know what is issue at client side?
Can you give us any online communication like Skype or hangout ID?
So we can check it is server or client side issue?
Thanks
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 20, 2015 5:24 PM To: Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Kamalio call issue
Hello,
again, if the SIP messages don't get to kamailio box, then the problem is on client side, not on server side.
If the request gets to kamailio and cannot do dns requests or they don't resolve, you will see a sip reply from kamailio.
There is not an issue that can be revealed by the config of kamailio. On the client side, try to use tools like host, dig and see what happens with dns requests. Also, use there ngrep to see if there are sip packets sent out of that box.
Cheers, Daniel
On 20/03/15 11:20, Yogendra Gupta wrote:
Hello,
When we can change our DNS IP then it works with following :
U 2015/03/20 10:06:06.504009 23.253.110.48:5060 -> 202.157.76.21:64051
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48SI P/2.0.
Call-ID: 143610160aa023568302b9c999b79f45@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bK7.601b877c92120368c17b3c0da0802af6.0.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=63789;received=202.157.76.21;branch=z9hG4bK-353035- 5aa153400d9ce60dfc573738a4b55232.
From: "tester1" sip:tester1@23.253.110.48 sip:tester1@23.253.110.48;tag=3fdb1d0f.
To: "tester2" sip:tester2@23.253.110.48 sip:tester2@23.253.110.48;tag=31532119.
Max-Forwards: 69.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48; alias=202.157.76.21~63789~1 sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48; alias=202.157.76.21~63789~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
But when we used another DNS IP (internet) and call then it showing only initialize..
If it has firewall issue then it will not work at all DNS IPs.
I have attached before my config file for kamalio.
Can you tell me what can be issue that it works at some DNS IP and not at all?
Thanks
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 20, 2015 2:14 AM To: Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Kamalio call issue
These are replies to INVITE requests, but if you see them, the INVITE passed through the server as well.
If you are not aware of a firewall, then perhaps you don't have one unless is a default installation with it enabled or one on the network.
I suggest you do sip tracing on the client machine to see if the invite requests leave to the proper IP.
Ultimately can be also a problem caused by a NAT router with ALG, if the client is behind such device.
Cheers, Daniel
We got following response:
U 2015/03/19 13:00:00.888887 23.253.110.48:5060 -> 115.252.208.170:62554
SIP/2.0 180 Ringing.
CSeq: 2 INVITE.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: sip:tester2@23.253.110.48;tag=53a85e1d.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-bbb85207996f538b1ac664a6a065d1fc.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48; alias=117.215.244.16~63380~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 13:00:01.829846 117.215.244.16:63380 -> 23.253.110.48:5060
SIP/2.0 200 OK.
CSeq: 2 INVITE.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: sip:tester2@23.253.110.48;tag=53a85e1d.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKf5a.b579cd6dc493912136143f67112a87f5.0,SIP/2.0/U DP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-bbb85207996f538b1ac664a6a065d1fc.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Content-Type: application/sdp.
Content-Length: 430.
.
v=0.
o=tester2-jitsi.org 0 0 IN IP4 192.168.0.100.
s=-.
c=IN IP4 192.168.0.100.
t=0 0.
m=audio 0 RTP/AVP 96 97 98 9 100 102 0 8 103 3 104 4 101.
m=video 5061 RTP/AVP 105 99.
a=inactive.
a=rtpmap:105 H264/90000.
a=fmtp:105 profile-level-id=4DE01f;packetization-mode=1.
a=imageattr:105 send * recv [x=[0-1600],y=[0-900]].
a=rtpmap:99 H264/90000.
a=fmtp:99 profile-level-id=4DE01f.
a=imageattr:99 send * recv [x=[0-1600],y=[0-900]].
U 2015/03/19 13:00:01.851782 23.253.110.48:5060 -> 115.252.208.170:62554
SIP/2.0 200 OK.
CSeq: 2 INVITE.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: sip:tester2@23.253.110.48;tag=53a85e1d.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-bbb85207996f538b1ac664a6a065d1fc.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48; alias=117.215.244.16~63380~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Type: application/sdp.
Content-Length: 449.
.
v=0.
o=tester2-jitsi.org 0 0 IN IP4 23.253.110.48.
s=-.
c=IN IP4 23.253.110.48.
t=0 0.
m=audio 0 RTP/AVP 96 97 98 9 100 102 0 8 103 3 104 4 101.
m=video 24322 RTP/AVP 105 99.
a=inactive.
a=rtpmap:105 H264/90000.
a=fmtp:105 profile-level-id=4DE01f;packetization-mode=1.
a=imageattr:105 send * recv [x=[0-1600],y=[0-900]].
a=rtpmap:99 H264/90000.
a=fmtp:99 profile-level-id=4DE01f.
a=imageattr:99 send * recv [x=[0-1600],y=[0-900]].
a=nortpproxy:yes.
U 2015/03/19 13:00:02.141163 115.252.208.170:62554 -> 23.253.110.48:5060
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48;a lias=117.215.244.16~63380~1 SIP/2.0.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 192.168.0.217:5060;branch=z9hG4bK-343938-155090537c14abf0495a2fba45f5683a.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: "tester2" sip:tester2@23.253.110.48;tag=53a85e1d.
Max-Forwards: 70.
Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 13:00:02.141537 23.253.110.48:5060 -> 117.215.244.16:63380
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 SIP/2.0.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKf5a.1f70aef5a57bc3412e94ec02b865d6b1.0.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-155090537c14abf0495a2fba45f5683a.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: "tester2" sip:tester2@23.253.110.48;tag=53a85e1d.
Max-Forwards: 69.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48; alias=115.252.208.170~62554~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 13:00:02.345295 117.215.244.16:63380 -> 23.253.110.48:5060
SIP/2.0 200 OK.
CSeq: 2 INVITE.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: sip:tester2@23.253.110.48;tag=53a85e1d.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKf5a.b579cd6dc493912136143f67112a87f5.0,SIP/2.0/U DP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-bbb85207996f538b1ac664a6a065d1fc.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Content-Type: application/sdp.
Content-Length: 430.
.
v=0.
o=tester2-jitsi.org 0 0 IN IP4 192.168.0.100.
s=-.
c=IN IP4 192.168.0.100.
t=0 0.
m=audio 0 RTP/AVP 96 97 98 9 100 102 0 8 103 3 104 4 101.
m=video 5061 RTP/AVP 105 99.
a=inactive.
a=rtpmap:105 H264/90000.
a=fmtp:105 profile-level-id=4DE01f;packetization-mode=1.
a=imageattr:105 send * recv [x=[0-1600],y=[0-900]].
a=rtpmap:99 H264/90000.
a=fmtp:99 profile-level-id=4DE01f.
a=imageattr:99 send * recv [x=[0-1600],y=[0-900]].
U 2015/03/19 13:00:02.345786 23.253.110.48:5060 -> 115.252.208.170:62554
SIP/2.0 200 OK.
CSeq: 2 INVITE.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: sip:tester2@23.253.110.48;tag=53a85e1d.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-bbb85207996f538b1ac664a6a065d1fc.
Record-Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester2" sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48; alias=117.215.244.16~63380~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Type: application/sdp.
Content-Length: 449.
.
v=0.
o=tester2-jitsi.org 0 0 IN IP4 23.253.110.48.
s=-.
c=IN IP4 23.253.110.48.
t=0 0.
m=audio 0 RTP/AVP 96 97 98 9 100 102 0 8 103 3 104 4 101.
m=video 24322 RTP/AVP 105 99.
a=inactive.
a=rtpmap:105 H264/90000.
a=fmtp:105 profile-level-id=4DE01f;packetization-mode=1.
a=imageattr:105 send * recv [x=[0-1600],y=[0-900]].
a=rtpmap:99 H264/90000.
a=fmtp:99 profile-level-id=4DE01f.
a=imageattr:99 send * recv [x=[0-1600],y=[0-900]].
a=nortpproxy:yes.
U 2015/03/19 13:00:02.632817 115.252.208.170:62554 -> 23.253.110.48:5060
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48;a lias=117.215.244.16~63380~1 SIP/2.0.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 192.168.0.217:5060;branch=z9hG4bK-343938-155090537c14abf0495a2fba45f5683a.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: "tester2" sip:tester2@23.253.110.48;tag=53a85e1d.
Max-Forwards: 70.
Route: sip:23.253.110.48;lr=on;nat=yes.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48 .
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
.
U 2015/03/19 13:00:02.633118 23.253.110.48:5060 -> 117.215.244.16:63380
ACK sip:tester2@192.168.0.100:5060;transport=udp;registering_acc=23_253_110_48 SIP/2.0.
Call-ID: 09b36cf7988131e179e345af90922a4c@0:0:0:0:0:0:0:0.
CSeq: 2 ACK.
Via: SIP/2.0/UDP 23.253.110.48;branch=z9hG4bKf5a.1f70aef5a57bc3412e94ec02b865d6b1.0.
Via: SIP/2.0/UDP 192.168.0.217:5060;rport=62554;received=115.252.208.170;branch=z9hG4bK-34393 8-155090537c14abf0495a2fba45f5683a.
From: "tester1" sip:tester1@23.253.110.48;tag=aca2e78b.
To: "tester2" sip:tester2@23.253.110.48;tag=53a85e1d.
Max-Forwards: 69.
Contact: "tester1" sip:tester1@192.168.0.217:5060;transport=udp;registering_acc=23_253_110_48; alias=115.252.208.170~62554~1.
User-Agent: Jitsi2.6.5390Windows 7.
Content-Length: 0.
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, March 19, 2015 5:50 PM To: Yogendra Gupta; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Kamalio call issue
Hello,
OPTIONS is not the request for initiating the calls, that is INVITE. You would need to know SIP a bit in order to be able to understand and configure Kamailio.
If you don't see any INVITE on kamailo server via ngrep when you call, then the issue is on client side or there is a firewall dropping it.
Cheers, Daniel
On 19/03/15 11:39, Yogendra Gupta wrote:
Hello,
Thanks for nice support.
When we call to test2 user and run this command at server
ngrep -d any -qt -W byline "sip" port 5060
then we found following response at server:
-
Daniel-Constantin Mierla -
Yogendra Gupta