<div dir="ltr"><div><div>Hi Duncan,<br><br>We have "sip set debug on" and nothing is shown, even though tcpdump/ngrep on the same server does. It's very strange.<br><br></div>The output of "ip address list" is:<br>
<br>[root]# ip address list<br>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN <br> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br> inet <a href="http://127.0.0.1/8">127.0.0.1/8</a> scope host lo<br>
inet6 ::1/128 scope host <br> valid_lft forever preferred_lft forever<br>2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000<br> link/ether 44:1e:a1:4e:2f:b8 brd ff:ff:ff:ff:ff:ff<br>
inet 103.y.y.19/24 brd 103.y.y.255 scope global eth0<br> inet6 fe80::461e:a1ff:fe4e:2fb8/64 scope link <br> valid_lft forever preferred_lft forever<br>3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000<br>
link/ether 44:1e:a1:4e:2f:ba brd ff:ff:ff:ff:ff:ff<br>4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000<br> link/ether 44:1e:a1:4f:30:a4 brd ff:ff:ff:ff:ff:ff<br>5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000<br>
link/ether 44:1e:a1:4f:30:a6 brd ff:ff:ff:ff:ff:ff<br>6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100<br> link/[65534] <br> inet 172.x.x.14 peer 172.x.x.13/32 scope global tun0<br>
<br></div>The output of "netstat -rn" is:<br><br>[root]# netstat -rn<br>Kernel IP routing table<br>Destination Gateway Genmask Flags MSS Window irtt Iface<br>172.x.x.10 172.x.x.13 255.255.255.255 UGH 0 0 0 tun0<br>
172.x.x.13 0.0.0.0 255.255.255.255 UH 0 0 0 tun0<br>172.x.x.1 172.x.x.13 255.255.255.255 UGH 0 0 0 tun0<br>172.x.x.18 172.x.x.13 255.255.255.255 UGH 0 0 0 tun0<br>
192.168.234.0 172.x.x.13 255.255.255.0 UG 0 0 0 tun0<br>192.168.235.0 172.x.x.13 255.255.255.0 UG 0 0 0 tun0<br>103.y.y.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0<br>
169.z.z.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0<br>172.21.0.0 172.x.x.13 255.255.0.0 UG 0 0 0 tun0<br>10.0.0.0 172.x.x.13 255.0.0.0 UG 0 0 0 tun0<br>
0.0.0.0 103.y.y.1 0.0.0.0 UG 0 0 0 eth0<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 21 January 2014 17:44, Duncan Turnbull <span dir="ltr"><<a href="mailto:duncan@e-simple.co.nz" target="_blank">duncan@e-simple.co.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Cool<div><br></div><div>That looks like it is arriving at Asterisk - are you sure asterisk is not getting it? If you turn on sip debug in asterisk can you see the SIP packets? It maybe asterisk is ignoring them or replying to them but its going out an interface you hadn’t thought of, I have had that a few times.</div>
<div><br></div><div>I should have mentioned to print out your route table and ifconfig. Asterisk can reply on a different address to the original destination especially if it came through a tunnel. Often it will be the tunnel interface address. Usually then we set the secondary address as the outbound proxy on the phone so the phone will also respond to it. </div>
<div><br></div><div>Cheers Duncan</div><div><div class="h5"><div><br></div><div>On 21/01/2014, at 7:18 pm, David Cunningham <<a href="mailto:dcunningham@voisonics.com" target="_blank">dcunningham@voisonics.com</a>> wrote:</div>
<div><div><br><blockquote type="cite"><div dir="ltr"><div>Hi Duncan,<br><br></div>Thank you for your reply. Here's the netstat:<br><div><br>[root]# netstat -udpln | grep asterisk<br>udp 0 0 <a href="http://0.0.0.0:5000/" target="_blank">0.0.0.0:5000</a> 0.0.0.0:* 6672/asterisk <br>
udp 0 0 <a href="http://0.0.0.0:4520/" target="_blank">0.0.0.0:4520</a> 0.0.0.0:* 6672/asterisk <br>udp 0 0 <a href="http://0.0.0.0:5060/" target="_blank">0.0.0.0:5060</a> 0.0.0.0:* 6672/asterisk <br>
udp 0 0 <a href="http://0.0.0.0:4569/" target="_blank">0.0.0.0:4569</a> 0.0.0.0:* 6672/asterisk <br><br></div><div>Here's the tcpdump (tcpdump udp port 5060 -A -n -nn -i tun0) from the Kamailio server:<br>
<br>17:13:17.103771 IP 103.x.x.x.5060 > 172.y.y.y.5060: SIP, length: 1228<br>E.......@.>/g.v.............INVITE <a>sip:*1@172.y.y.y:5060;transport=udp</a> SIP/2.0<br>Record-Route: <<a>sip:103.x.x.x;lr=on</a>><br>
Via: SIP/2.0/UDP 103.x.x.x;branch=z9hG4bK584f.d0387c07.0<br>
Via: SIP/2.0/UDP 192.168.1.40:5060;received=203.z.z.z;rport=5060;branch=z9hG4bK274588850<br>From: <<a>sip:9067273@103.x.x.x</a>>;tag=1880695235<br>To: <<a>sip:*1@103.x.x.x</a>><br>Call-ID: 1898224288<br><br><br>
Here's the tcpdump (tcpdump udp port 5060 -A -n -nn -i tun0) from the Asterisk server:<br>
<br>17:13:17.093676 IP 103.x.x.x.5060 > 172.y.y.y.5060: SIP, length: 1228<br>E.......?.?/g.v.............INVITE <a>sip:*1@172.y.y.y:5060;transport=udp</a> SIP/2.0<br>Record-Route: <<a>sip:103.x.x.x;lr=on</a>><br>
Via: SIP/2.0/UDP 103.x.x.x;branch=z9hG4bK584f.d0387c07.0<br>
Via: SIP/2.0/UDP 192.168.1.40:5060;received=203.z.z.z;rport=5060;branch=z9hG4bK274588850<br>From: <<a>sip:9067273@103.x.x.x</a>>;tag=1880695235<br>To: <<a>sip:*1@103.x.x.x</a>><br>Call-ID: 1898224288<br><br></div>
<div><br>
</div>
</div><div class="gmail_extra"><br></div></blockquote></div><br></div></div></div></div><br>--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br><br clear="all"><br>-- <br>David Cunningham, Voisonics<br>
<a href="http://voisonics.com/" target="_blank">http://voisonics.com/</a><br>USA: +1 213 221 1092<br>UK: +44 (0) 20 3298 1642<br>Australia: +61 (0) 2 8063 9019<br>
</div>