IAX2 Unreachable in 1 Direction Only (Wrong PONG port?)

Hello All!

I have 2 PBX servers, and they are supposed to be connected by an IAX2 link. I am having issues where only 1 of the 2 servers are marked as online while the other one is unreachable. Enabling the iax2 debug log, I see that on one end (the working side) running freshly updated FreePBX17 is showing the following:

VERBOSE[145459] chan_iax2.c: Rx-Frame Retry[Yes] -- OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE	
VERBOSE[145459] chan_iax2.c: Timestamp: 00010ms SCall: 01289 DCall: 00000 <REDACTED>:4569	
VERBOSE[145459] chan_iax2.c: CALLTOKEN : Present	
VERBOSE[145459] chan_iax2.c:	
VERBOSE[145459] chan_iax2.c: Tx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG	
VERBOSE[145459] chan_iax2.c: Timestamp: 00010ms SCall: 00001 DCall: 01289 <REDACTED>:4569

For the other box, it is very similar, although there is one difference, the port used for the PONG is different (1105) compared to the 4569 that is typically used. I have no idea what would cause this, or where it would be. This other server shows unreachable and is running the latest FreePBX 16 as I haven’t yet gotten around to updating it:

VERBOSE[11260] chan_iax2.c: Tx-Frame Retry[002] -- OSeqno: 000 ISeqno: 000 Type: IAX Subclass: POKE	
VERBOSE[11260] chan_iax2.c: Timestamp: 00001ms SCall: 11263 DCall: 00000 <REDACTED>:4569	
VERBOSE[11260] chan_iax2.c:	
VERBOSE[11261] chan_iax2.c: Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX Subclass: PONG	
VERBOSE[11261] chan_iax2.c: Timestamp: 00001ms SCall: 00001 DCall: 11263 <REDACTED>:1105

For the configurations:

host=<REDACTED>
username=<REDACTED>
secret=<REDACTED>
forceencryption=yes
encryption=yes
auth=md5
type=friend
qualify=yes
context=from-internal
allow=ulaw

Any ideas? I am truly confused, this has been going on for the past few days, but has worked beforehand. I don’t know if the upgrade to PBX 17 would cause this, but I don’t see how, considering the system with the weird 1105 port is on PBX 16. Thank you for any help.

MB :>

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.