Aaarghhhhh!

Asterisk Asterisk Support
1

I have tried been battling a simple problem for 5hrs and I fear I cannot see the wood for the trees.

I am sitting at my PC, with a VPN to a client site. I have SSH and Xlite running.

I am looking at the console at 192.168.1.10 which is the LAN address of the Asterisk server.

My XLITE client is registered with 192.168.1.10. sip shows peers shows it 37ms

However, when I dial (voicemail for example) I hear the dialtone and DTMF tones from the xlite client and I see the console showing ‘you have’ / ‘2 messages’ but no audio comes through the XLITE.

There should be no nat issues of course, I see no codec errors, I don’t see anything out of the ordinary when I turn on SIP debugging…

What cann it be, such a simple problem holding me up from doing some real work on my clients system!

Any suggestions greatly appreciated!

2

Is this a new system ?

Does music on hold work ?

Have you configured zaptel ?

Ian

(You think you have it bad, I got back at 05:30 after spending all night rebuliding a system that was toasted by dd being done the wrong way ;-( without taking a backup before hand)

3

Hi Iain,

Thanks for your reply.

The system is in and working for 6 months. I just wanted to do some work.

Zaptel is configured and working, the system is fully functional for all onsite users.

As it goes, MOH doesn’t work. That is one of the things I am going to look at when I get sound coming through to my softphone.

Whats the connection? I am intrigued?

By the way, I have had this working before and had chats with the staff via xlite / vpn to the site.

Any assistance appreciated…

4

Hi

The connection is that there is a “bug” that can mean playback and voicemail greetings dont work if zaptel is installed and misconfigured.

As to your problem, What does rtp debug show?

Ian

5

Hi Ian,

I hadn’t tried RTP debug, but here is the output when dialing 500 (voicemail) from 666 (my test extension).

192.168.1.202 is the address my PPTP VPN client has been allocated by the draytek router at the site.

localhostCLI>
– Executing Answer(“SIP/666-09e93ad8”, “”) in new stack
– Executing VoiceMailMain(“SIP/666-09e93ad8”, “s500@default”) in new stack
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17092, ts 160, len 160)
– Playing ‘vm-youhave’ (language ‘en’)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17093, ts 320, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17094, ts 480, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17095, ts 640, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17096, ts 800, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17097, ts 960, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17098, ts 1120, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17099, ts 1280, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17100, ts 1440, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17101, ts 1600, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17102, ts 1760, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17103, ts 1920, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17104, ts 2080, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17105, ts 2240, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17106, ts 2400, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17107, ts 2560, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17108, ts 2720, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2668, ts 2551080, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2669, ts 2551240, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17109, ts 2880, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17110, ts 3040, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2670, ts 2551400, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2671, ts 2551560, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2673, ts 2551880, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2674, ts 2552040, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17111, ts 3200, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2676, ts 2552360, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2677, ts 2552520, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17112, ts 3360, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2679, ts 2552840, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2680, ts 2553000, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2681, ts 2553160, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17113, ts 3520, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2682, ts 2553320, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17114, ts 3680, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17115, ts 3840, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2683, ts 2553480, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2684, ts 2553640, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17116, ts 4000, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2685, ts 2553800, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17117, ts 4160, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17118, ts 4320, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2686, ts 2553960, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2687, ts 2554120, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17119, ts 4480, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2688, ts 2554280, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17120, ts 4640, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17121, ts 4800, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2689, ts 2554440, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17122, ts 4960, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17123, ts 5120, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2690, ts 2554600, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2691, ts 2554760, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2692, ts 2554920, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17124, ts 5280, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2693, ts 2555080, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17125, ts 5440, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2694, ts 2555240, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17126, ts 5600, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17127, ts 5760, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2695, ts 2555400, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2696, ts 2555560, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17128, ts 5920, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2697, ts 2555720, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17129, ts 6080, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17130, ts 6240, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17131, ts 6400, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2698, ts 2555880, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17132, ts 6560, len 160)
– Playing ‘digits/4’ (language ‘en’)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2699, ts 2556040, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2700, ts 2556200, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2701, ts 2556360, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17133, ts 6720, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2702, ts 2556520, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17134, ts 6880, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17135, ts 7040, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2703, ts 2556680, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17136, ts 7200, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2704, ts 2556840, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17137, ts 7360, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2705, ts 2557000, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17138, ts 7520, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2706, ts 2557160, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2707, ts 2557320, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17139, ts 7680, len 160)
Got RTP packet from 192.168.1.202:29914 (type 8, seq 2708, ts 2557480, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17140, ts 7840, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17141, ts 8000, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17142, ts 8160, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17143, ts 8320, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17144, ts 8480, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17145, ts 8640, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17146, ts 8800, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17147, ts 8960, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17148, ts 9120, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17149, ts 9280, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17150, ts 9440, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17151, ts 9600, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17152, ts 9760, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17153, ts 9920, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17154, ts 10080, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17155, ts 10240, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17156, ts 10400, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17157, ts 10560, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17158, ts 10720, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17159, ts 10880, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17160, ts 11040, len 160)
– Playing ‘vm-INBOX’ (language ‘en’)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17161, ts 11200, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17162, ts 11360, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17163, ts 11520, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17164, ts 11680, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17165, ts 11840, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17166, ts 12000, len 160)
Sent RTP packet to 192.168.1.202:29914 (type 8, seq 17167, ts 12160, len 160)
== Spawn extension (internal, 500, 2) exited non-zero on 'SIP/666-09e93ad8’
localhostCLI>

6

Well theres the problem.

I thought you said that you were on 192.168.1.10

what is the IP of the server and what is the localnet setting

try setting the sip.conf for 666 to have nat=yes

Ian

7

Hi Iain,

Thanks for your help I appreciate it.

192.168.1.10 was hypothetical - sorry for any confusion.

My actual home IP is 192.168.2.243
My PPTP Dial up (vpn) address is 192.168.1.202
The Asterisk Server is on 192.168.1.250

I will try NAT=YES in the softphone definition but I suspect I may have tried it unsuccessfully last night / this morning in the twilight hours.

I will have a fresh try now and let you know.

Cheers,

Sean

8

Hi from asterisk can you ping 192.168.2.243 ?

Im guessing you may need to do some port forwarding. or can you run the pptp client on your desktop and not the router as it proberly will work then

Ian

9

Hi Ian,

The VPN is between my PC and the Router at site.

The PC only has one address 192.168.2.243 until I establish the VPN dialup connection at which point I get allocated 192.168.1.202 also.

From the asterisk box, I cannot ping 192.168.2.243 but I can ping 192.168.1.202.

A tracert from my PC to the Asterisk server looks like

Tracing route to 192.168.1.250 over a maximum of 30 hops

1 33 ms 32 ms 44 ms my.router [192.168.1.1]
2 56 ms 60 ms 33 ms 192.168.1.250

Trace complete.

my.router being the router onsite in Slough.

I am not an expert but I wouldn’t expect asterisk to be able to ping my lan IP address unless I did some forwarding on the PC although the xlite phone should be happy to use the dialup address 192.168.1.202 which is only 1 hop from the router and two hops from Asterisk.

This is a real strange situation, I have even tried other softphones with no joy… the only thing I noticed, but not sure of significance is in sip show peers… the port for my xlite phone is different to all other phones.

localhost*CLI>

-- Registered SIP '666' at 192.168.1.202 port 54410 expires 3600
-- Saved useragent "X-Lite release 1011s stamp 41150" for peer 666

localhost*CLI> sip show peers

Name/username Host Dyn Nat ACL Port Status
666/666 192.168.1.202 D N A 54410 OK (113 ms)
107/107 192.168.1.17 D N A 5060 OK (58 ms)
106/106 192.168.1.19 D N A 5060 OK (57 ms)
105/105 192.168.1.18 D N A 5060 OK (57 ms)
104/104 192.168.1.16 D N A 5060 OK (60 ms)
103/103 192.168.1.21 D N A 5060 OK (56 ms)
102/102 192.168.1.22 D N A 5060 OK (55 ms)
101/101 192.168.1.20 D N A 5060 OK (56 ms)
8 sip peers [8 online , 0 offline]
localhost*CLI>

Is the port significant?

I thought a problem might have been the Asterisk server on my lan, but switching it off made no difference…

10

Hi I know I was up late but im getting confused.

can you list all the ip addresses and what they are assigned to

IE
asterisk
router(onsite)
router(you)
Your real IP
your vpn IP

asterisk localnet and externip settings.

Ian

11

Hi Iain,

Thanks again!

asterisk server (slough) - 192.168.1.250
router (slough) LAN - 192.168.1.1
router (slough) WAN - 21.121.x.x

localnet=192.168.1.0/255.255.255.0
externip=213.121.x.x

The router at slough has same external IP as extern ip.

router (cardiff) - 192.168.2.1
My PC IP (cardiff) - 192.168.2.243
My PC VPN IP (cardiff) - 192.168.1.202

If you need any more please let me know.

12

Ok I think you may have a port blocked on your router possibly or on your PC

As the rtp stream is going to the correct point but you aren seeing it…

try running wireshark on your pc and see what arrives

Ian

13

I had this problem… either shut off the firewall on the router for a quick test and if that works, open the corresponding ports (possible rtp)

14

I know this post is old but someone else may have the same problem. If your connection looks like this:

Asterisk (192.168.1.100) (Device A)
VPN Router (192.168.1.0/24) (Device B - Eth0)
External IP (MAC Device C - Eth1)
|
|
Your provider’s IP (Device D - Eth1)
Your Router (192.168.1.0/24) (Device E - Eth0)
Your Client (192.168.1.2 (Device F)

Your subnet (Eth0 on Device E) cannot be the same as your client’s local subnet (Eth0 on Device B). Otherwise a packet destined for your machine (Device F) would reach eth0 on Device B, would look like it was destined for your client’s local subnet, would not appear in the MAC Address table, would be flooded all the ports on your client’s router’s internal switch then the packet would be dropped. It would never reach your machine.

I hope this helps.