IAX troubleshooting again


#1

I have one main freepbx system (SIP trunk only) (FreePBX 13.0.192.8) “system A” with an ip of 172.29.122.117

I have deployed a second freepbx system at another site, “system B” has an IP of 172.29.126.6

These two systems are connected via VPNs and can both ping each other.

I’ve tried creating an IAX trunk between the two:
System A:
name=System2
host=172.29.126.6
username=System1
secret=password
type=friend
qualify=yes
context=from-internal

SystemB:
name:System1
host=172.29.122.117
username=System2
secret=password
type=friend
qualify=yes
context=from-internal

On system B typed in:

iax2 show peer System1

  • Name : System1
    Description :
    Secret :
    Context : from-internal
    Parking lot :
    Mailbox :
    Dynamic : No
    Callnum limit: 0
    Calltoken req: No
    Trunk : Yes
    Encryption : No
    Callerid : “” <>
    Expire : -1
    ACL : No
    Addr->IP : 172.29.122.117 Port 4569
    Defaddr->IP : (null) Port (null)
    Username : System2
    Codecs : (gsm|ulaw|alaw)
    Codec Order : (ulaw|alaw|gsm)
    Status : UNREACHABLE
    Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off)

System A shows the same thing.

When running tcpdump on port 4569 I see traffic between both PBXs. Any ideas on where to go from here?


#2

To troubleshoot iax2 then from asterisk:-

iax2 set debug on

and watch what happens

p.s. username and secret are pretty pointless in a 172.16.0.0/12 network, just be friendly :wink:


#3

No, don’t be friendly. Use all the passwords and usernames you want, and make them as complex as you can.

Also, why bother with IAX2? SIP is better documented, more portable, and easier to troubleshoot. It’s 2017 and there is almost no reason to be using IAX.


#4

Here is what the debug shows:

mis-v-ontopbx*CLI> iax2 show peers
Name/Username    Host                                           Mask                                      Port           Status      Description
from-internal/t  172.29.122.117                           (S)  255.255.255.255                           4569  (T)      UNREACHABLE
System1/System2  172.29.122.117                           (S)  255.255.255.255                           4569           UNREACHABLE
2 iax2 peers [0 online, 2 offline, 0 unmonitored]
Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00001ms  SCall: 08104  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00001ms  SCall: 02791  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[001] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00001ms  SCall: 08104  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[001] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00001ms  SCall: 02791  DCall: 00000 172.29.122.117:4569

Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00009ms  SCall: 02452  DCall: 00000 172.29.122.117:4569
Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00010ms  SCall: 02977  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00009ms  SCall: 00001  DCall: 02452 172.29.122.117:4569
   Timestamp: 00010ms  SCall: 00001  DCall: 02977 172.29.122.117:4569
Rx-Frame Retry[Yes] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00009ms  SCall: 02452  DCall: 00000 172.29.122.117:4569

Rx-Frame Retry[Yes] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00009ms  SCall: 00001  DCall: 02452 172.29.122.117:4569
   Timestamp: 00010ms  SCall: 02977  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00010ms  SCall: 00001  DCall: 02977 172.29.122.117:4569
Tx-Frame Retry[002] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00001ms  SCall: 08104  DCall: 00000 172.29.122.117:4569
Tx-Frame Retry[002] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE

   Timestamp: 00001ms  SCall: 02791  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 13341  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 08530  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[001] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 13341  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[001] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 08530  DCall: 00000 172.29.122.117:4569

Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00009ms  SCall: 01995  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00009ms  SCall: 00001  DCall: 01995 172.29.122.117:4569
Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00012ms  SCall: 12743  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00012ms  SCall: 00001  DCall: 12743 172.29.122.117:4569
Rx-Frame Retry[Yes] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00009ms  SCall: 01995  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00009ms  SCall: 00001  DCall: 01995 172.29.122.117:4569
Rx-Frame Retry[Yes] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00012ms  SCall: 12743  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00012ms  SCall: 00001  DCall: 12743 172.29.122.117:4569
Tx-Frame Retry[002] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 13341  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[002] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 08530  DCall: 00000 172.29.122.117:4569

I’m willing to give SIP a try, I’ll start working on that too.


#5

I would check your trunk config you seem to have an incorrect name/username lookup result

There are examples of this etup in the wiki above and google will give you amany more


#6

Based on the other comment I deleted username / password to try and simplify the config…still get the same result.


(Tony Nichols) #7

Your config looks very close… here is the sample I always look back on when creating a link to a second server…
First Server:

Trunk Name: Second Server

Trunk Name: SECOND-SERVER

Peer details:

host=ip_second_server
username=FIRST-SERVER
secret=some_secret
type=friend
context=from-internal
qualify=5000
trunk=yes

Second Server:

Trunk Name: First Server

Trunk Name: FIRST-SERVER

Peer details:

host=ip_first_server
username=SECOND-SERVER
secret=some_secret
type=friend
context=from-internal
qualify=5000
trunk=yes

There is no need for the user details.


#8

https://wiki.freepbx.org/pages/viewpage.action?pageId=4161588


#9

thanks, I’ve copied the config out of the wiki, still unreachable.

I noticed on one pbx it’s a IAX2 trunk, on the other it’s IAX…could that be the problem?


#10

I’ve upgrade both PBXs to the same updated version. Now I see an option for IAX2 trunk on both system.

I’ve rebuilt the trucks with the following:
Name=System2
host=172.29.131.9
username=System1
secret=password
type=friend
context=from-internal
qualify=yes
trunk=yes

name=System1
host=172.29.122.117
username=System2
secret=password
type=friend
context=from-internal
qualify=yes
trunk=yes

Using tcpdump I see traffic on both system on port 4569

iax2 show peer System1

  • Name : System1
    Description :
    Secret :
    Context : from-internal
    Parking lot :
    Mailbox :
    Dynamic : No
    Callnum limit: 0
    Calltoken req: No
    Trunk : Yes
    Encryption : No
    Callerid : “” <>
    Expire : -1
    ACL : No
    Addr->IP : 172.29.122.117 Port 4569
    Defaddr->IP : (null) Port (null)
    Username : System2
    Codecs : (gsm|ulaw|alaw)
    Codec Order : (ulaw|alaw|gsm)
    Status : UNREACHABLE
    Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off)

iax2 show peer System2

  • Name : System2
    Description :
    Secret :
    Context : from-internal
    Parking lot :
    Mailbox :
    Dynamic : No
    Callnum limit: 0
    Calltoken req: No
    Trunk : Yes
    Encryption : No
    Callerid : “” <>
    Expire : -1
    ACL : No
    Addr->IP : 172.29.131.9 Port 4569
    Defaddr->IP : 0.0.0.0 Port 0
    Username : System1
    Codecs : (gsm|ulaw|alaw)
    Codec Order : (ulaw|alaw|gsm)
    Status : UNREACHABLE
    Qualify : every 60000ms when OK, every 10000ms when UNREACHABLE (sample smoothing Off)

taken from system 2:

iax2 set debug on
IAX2 Debugging Enabled
Tx-Frame Retry[002] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00019ms SCall: 13075 DCall: 00000 172.29.122.117:4569

Rx-Frame Retry[ No] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00010ms SCall: 03022 DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] – OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG
Timestamp: 00010ms SCall: 00001 DCall: 03022 172.29.122.117:4569
Rx-Frame Retry[Yes] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00010ms SCall: 03022 DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] – OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG
Timestamp: 00010ms SCall: 00001 DCall: 03022 172.29.122.117:4569
Tx-Frame Retry[000] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00013ms SCall: 14067 DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[001] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00013ms SCall: 14067 DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[002] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00013ms SCall: 14067 DCall: 00000 172.29.122.117:4569

Rx-Frame Retry[ No] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00008ms SCall: 08250 DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] – OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG
Timestamp: 00008ms SCall: 00001 DCall: 08250 172.29.122.117:4569
Rx-Frame Retry[Yes] – OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE
Timestamp: 00008ms SCall: 08250 DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] – OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG
Timestamp: 00008ms SCall: 00001 DCall: 08250 172.29.122.117:4569

Note there are no setting under “incoming” on either trunk.

?


#11

You appear to have set up your trunks to point to themselves not the peer/friend you intended, again check your trunks against the “known working configurations”


#12

Read

https://www.voip-info.org/wiki-IAX+versus+SIP

http://www.en.voipforo.com/IAX/IAXvsSIP.php

etc. ,

What it all means that IAX2 in a private network will ALWAYS beat SIP as to efficiency and ease of deployment.

IAX stands for Inter Asterisk eXchange, the 2 for “it’s better” for any tie-lines between Asterisk servers, it IS well documented and for a “private” network, then a minimalist deployment needs then you really don’t need Auth of any form, so for a trunk:-

host=theotherend
trunk=yes
type=friend
qualify=yes
context=from-internal

on each end.

You really don’t even need the qualify if it is truly a robust local,unroutable network , but if you use it, then any NAT traversal would likely be transparent and you should add an authentication process for your protection if the IP is routable , if so you should NOT use 4569 for obvious reasons (add port=unlikelyforknuckledraggerstofind), bear in mind that the context {[rom-internal] might give more or less exposure than you need.

If you have a shorter and more efficient way with SIP, please post it.

If you have never tried it , you should.


#13

You cited voip-info.org. Not sure what to tell you. None of those sites mean anything whatsoever. The problems IAX2 solve don’t exist. It is not needed, especially in a private network.


#14

Thank you for your opinion, but why do real-world solutions not mean anything?. Many have used it for years without any problems, and yes those problems with SIP’s NAT traversal DO exist, please explain your position more fully, but better yet , offer your SIP solution with your ubiquitous routing solution.


#15

I’ve got stuff to do, but would be happy to reply later. In case someone actually stumbles on this page, though, please realize that IAX2 doesn’t “beat” SIP. It is not inherently better. It does not have some magical interoperability with Asterisk that SIP does not. What the acronym means is not important. You want to be using SIP; if you MUST have IAX2, you’ll know it. The main advantages were important more than a decade ago, but since then NAT traversal and bandwidth have become far less of a problem. I cannot think of a single reason I’d ever recommend anyone use IAX2, except maybe in very niche wireless scenarios.


#16

Again , thank you for opinion, when you are less busy, you should expand and expound, I am pretty sure anyone who has used IAX2 for the last 10+ years will disagree with you though. The magic is in the I , A and X of the protocol, one port for signalling and media,NAT traversal through multiple routers , trunk efficiency and ease of use (you can interpret that as “interoperibilty”, magic or not :wink: ) , SIP can’t do any of the above. Again, if you have a more robust SIP solution,. please post it, but please just don’t dive and duck and so waste everyone’s time.

Note the reference to “Mark Spencer”


(Avayax) #17

NAT traversal is still a major problem for SIP, will always be and it’s just something SIP sucks at big time and where IAX triumphs.
Just look at the regular posts here on the forum with no audio, one way audio problems, etc.
The solutions like STUN, ICE and whatever people came up with are insufficient workarounds for that big disadvantage.

With that in mind, IAX would theoretically be the preferred protocol in almost every scenario, except for maybe voice service providers who like to run the audio stream through other carriers, but IAX seems to have a few problems as well.

We were running an IAX trunk over the internet between our Asterisk servers and one day it starting failing one way with “Reject, cause code 50”, which we weren’t able to solve.
Then tried SIP instead, which worked and people started telling us how much better the call quality was since we had made a “change”.
People had complained about voice drop outs very often, which we had blamed the network for, but after the switch to SIP, they all went away.

But I don’t have the slightest idea why that would be, just glad it’s better. But there are probably many other users out there for whom IAX works great.

I also found IAX debug gives you very little info to properly troubleshoot.

Despite its advantages, it unfortunately never took off and saw widespread adoption, especially among voice service providers and phone manufacturers.
If that had happened, it would have been a serious competitor to SIP, especially as we would have seen continuous advances in the IAX protocol, which we haven’t.

But who knows what the future will bring, SIP might die out, with the advent of WebRTC.


#18

IAX2 requires both ends to be or at least behave like Asterisk . It does have a problem of ‘choking’ when the concurrency gets into the hundreds so many VSPs like Vitelity stopped supporting it. Cause 50 likely is exposing that problem

https://networking.ringofsaturn.com/Routers/isdncausecodes.php

It is however an ideal choice for smaller networks, in this case two machines, that it can be setup as a trunk , means the connection is always up so a real ‘tie-line’ unlike SIP which treats each call as a separate one so a lot more overhead.

True the debug is minimal but a reliable

POKE, PONG,ACK

every 60 seconds , if qualify=yes, for each trunk will confirm a) that it is working and b) the IP of the far end Asterisk, there is little else to be gleaned from the trunk apart from increasing ’ tries’ if not connected, endpoint activity is not too bad ina kinda yes/no fashio.
There is of course :-

tcpdump -X -s 0 -vv port 4569

And that can be diagnostic if there is no connectivity that dump should of course be symmetrical as to packets and origination/destination IP

So for me IAX2 between my boxen , SIP for origination and termination of PSTN calls.


#19

Not understanding how to implement NAT properly does not indicate a problem with the protocol. SIP works fine over NAT, so long as you have any idea what you’re doing.


(Avayax) #20

SIP is more work to implement in NAT and more error prone.
IAX is easier to implement in that aspect and that also means “better” in that area.
Many NAT scenarios have to be tweaked to make SIP work, that could otherwise be left untouched with IAX.