IAX2 Inbound Connections for Additional Numbers

Hi,

I've set up additional VoipUser numbers (0844 and 0871) range to try and deliver into my * box via IAX2. I had this working previously (in June) but had taken a break from * and home VoIP due to work.

However, the config I had (following such examples as http://www.voipuser.org/forum_topic_95.html) that previously worked. It doesn't now!

iax.conf contains:

Code:

[44844484XXXX] username=riverlea45 secret=XXXXXX type=user context=incoming_iax

A corresponding context exists in extensions, currently configured to answer and play-back an announcement.

The * box is in the DMZ for my connection, so no firewall issues.

Inbound calls aren't even causing any CLI traffic on the box. I have tested by diverting the number to SIP and PSTN, and it works - so it must be something with IAX.

Any ideas, as I'm running out!

Thanks.

Hi

You need to look at the iax2 debug not the cli initally

There have been no changes here AFAIK are you sure the numbers work to another destination.

Ian

ianplain :

You need to look at the iax2 debug not the cli initally There have been no changes here AFAIK are you sure the numbers work to another destination.

thanks for the response.

I have enabled IAX2 debugging - nothing is logged at all when I dial the incoming number - just get the BT women's voice saying 'the service cannot be connected'.

I have diverted the same number via SIP to a normal phone and the call came straight through.

Some config snippets, first iax.conf:

Code:

[general] bindport=4569 authdebug=yes language=en disallow=all allow=ulaw allow=alaw allow=gsm jitterbuffer=yes dropcount=1 [448444841246] username=riverlea45 secret=abcd type=user context=incoming_iax

The entry in 'My Numbers' is:

IAX2/riverlea45:abcd@riverleapbx.homeip.net

riverleapbx.homeip.net is a valid Dynamic DNS name, verified by accessing the web server also located on it.

Any other suggestions?[/code]

riverlea45 :

I have enabled IAX2 debugging - nothing is logged at all when I dial the incoming number - just get the BT women's voice saying 'the service cannot be connected'.

I'm getting exactly the same problem. I have used * in the past but I've got very rusty. Now attempting to link up my old voipuser inbound numbers and I'm getting the same message as riverlea45.

tcpdump'ing the udp packets on the network show that nothing is hitting the * server.

The udp port tester from the download page says that 4569 is not open (with * running and without) even though it is explicitly allowed via IPtables.

Any hints would be much appreciated.

Thanks

EDIT: scratch most of that, it was a problem with the router not allowing udp/4569 through. Now I just have to sort out the crappy quality