Troubleshooting IAX2 trunks (stop arguing)

@a5t1 wrote:

I'd really like to bring up the other thread of why SIP or IAX is better for trunking, however, I don't care.

At the end of the day I'd like to have some meaningful discussion on why my IAX2 trunks aren't talking to each other.

To recap - I have two remote systems connected over a VPN. Both FreePBX systems are running the latest release.

Here is what I see:

 iax2 show peers
Name/Username    Host                                           Mask                                      Port           Status      Description
System1/System2  172.29.122.117                           (S)  255.255.255.255                           4569  (T)      UNREACHABLE

With debug:

 iax2 set debug on
IAX2 Debugging Enabled
Rx-Frame Retry[Yes] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00014ms  SCall: 13277  DCall: 00000 172.29.122.117:4569

Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: PONG
   Timestamp: 00014ms  SCall: 00001  DCall: 13277 172.29.122.117:4569
Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: POKE
   Timestamp: 00019ms  SCall: 14434  DCall: 00000 172.29.122.117:4569

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

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

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

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

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

Here is the only other piece of information:
 tcpdump -X -s 0 -vv port 4569
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
09:14:16.864311 IP (tos 0xb8, ttl 64, id 5423, offset 0, flags [none], proto UDP (17), length 42)
    172.29.131.9.iax > 172.29.122.117.iax: [bad udp cksum f5c0!] UDP, length 14
        0x0000:  45b8 002a 152f 0000 4011 0f23 ac1d 8309  E..*./..@..#....
        0x0010:  ac1d 7a75 11d9 11d9 0016 55e1 b35b 8000  ..zu......U..[..
        0x0020:  0000 0005 0000 061e 3600                 ........6.

Notice the bad udp cksum, I wonder why?

Any thoughts?

Posts: 15

Participants: 3

Read full topic