Topic: Long shot. Anyone used VOIPON AIX trunk in the UK ?

[Drifting]

It is something in my config. As I have just fired up the earlier version of Sail, and that registers fine?

Not a clue now on what to look for. Shall fire an email of to Voipon in the vain hope.

Thanks for the help.

[SARK devs]

delete the trunk and redefine it.  Make sure you get the userid and password on the first pass.

See if that cures it.

S

[Drifting]

Sadly same result.

I can make a test call to them fine, but for some reason it seems not to want to register with them on IAX for incoming. I have created this truck about 5 times, and religiously entered the username and password as was sent, even have gone so far as to cut and past from the working older system.

I am not a whiz with wireshark, so is there as way for me to see what is coming back from them?

As an aside, does this new version block outgoing and incoming SIP by default on the external interface (Server Gateway mode) or do you explicitly have to do an "config setprop sailSIP status disabled" ?  Of course after doing the remoteaccess-update.
As even after that mine says :-

[root@voipsbs ~]# /etc/init.d/masq status | grep 5060
ACCEPT     udp  --  0.0.0.0/0        (external IP)        udp dpt:5060

Only reason I asked, as I noticed I was getting failed SIP request from a chancer, and that was after a short amount of time. Liked the idea of the OSSEC works well.

Regards

[SARK devs]

to see what is running on the iax trunk; at the asterisk console you can do

Code: [Select]

iax2 set debug
turn it off with

Code: [Select]

iax2 set debug off
If your older system is still working OK it occurs to me that your router may be forwarding to the wrong IP address internally.

I tested the sailSIP enable/disable and it works just fine here.   What does config show sailSIP give?   

kind regards

s

 

[Drifting]

I did try the debug, but I cannot see anything coming from Voipon. So I changed the password for the working outgoing trunk, and then saw a registration error. However I see nothing coming in when from voipon if I make an incoming call via a normal pstn line to the voipon line.

I am in server gateway mode, this is a virtual server, running on the same server as my other virtual voip server (The old working one)
One thing perhaps I should mention, I have two other IAX trunks to friends Asterisk boxes that work fine.

As requested config show sailSIP & sailIAX

[root@voipsbs ~]# config show sailSIP         
sailSIP=service
    UDPPort=5060
    access=public
    status=enabled
[root@voipsbs ~]# config show sailIAX
sailIAX=service
    UDPPort=4569
    access=public
    status=enabled

I wonder if I have the syntax right? config setprop sailSIP disabled? Will go check your site to make sure.

Regards

[SARK devs]

If you aren't seeing anything in the debug then you will need to ask VoipOn why they aren't sending, and check your external firewall and port forwards to ensure they are correct. 

config statement was correct in your previous post

Code: [Select]

config setprop sailSIP status disabled
Kind Regards

s

[Drifting]

Well I seem to be getting the run around with the trunk provider.  It takes a while to get a reply and I am running out of time to get this working. What I could really do with is a monitor for incoming IAX packets, IAX debug does not show me any anything from the trunk provider unless I miss dial a number :-
[Apr  5 10:25:02] WARNING[3286]: chan_iax2.c:9197 socket_process: Call rejected by 217.14.138.130: No such context/extension

I can call their test line still. But still no incoming. Am I down to wireshark?

Regards

[Drifting]

RESOLVED

Well I am not sure why, but I found out what it was. When I created the truck I let SARK choose the names of the peer,  I must have set the username of the "user" Now I set  this to what my login was, ie username for Voipon. It turns out it wanted the incoming line number.

Hopefully might save someone some time.

[SARK devs]

Glad you got it sorted Paul

Jeff