Hi all, I'm having trouble with incoming IAX2 calls on 1.2.7.1 - mostly they work, but sometimes the caller just gets dead air or disconnects. IAX2 debugs show HANGUP and INVALID codes in these cases, rather than a proper RINGING transaction. My firewall is doing NAT, and changing the source port from 4569 to something else - my IAX2 provider suggested this might be a problem. Is it? Should this work: steerpike*CLI> iax2 show registry Host Username Perceived Refresh State 64.26.157.230:4569 8886708729 64.26.155.62:14353 60 Reg 64.26.157.230:4569 6134827945 64.26.155.62:14353 60 Reg 64.26.157.230:4569 6136866597 64.26.155.62:14353 60 Reg 64.26.157.230:4569 6136866675 64.26.155.62:14353 60 Reg There are four DIDs, and all are registered to an odd port (14353). Is this OK? (I am using a Sonicwall TZ170 with "Enable Consistent NAT" on). - Mike
Dr. Michael J. Chudobiak wrote:> Hi all, > > I'm having trouble with incoming IAX2 calls on 1.2.7.1 - mostly they > work, but sometimes the caller just gets dead air or disconnects. IAX2 > debugs show HANGUP and INVALID codes in these cases, rather than a > proper RINGING transaction. > > My firewall is doing NAT, and changing the source port from 4569 to > something else - my IAX2 provider suggested this might be a problem. > Is it? Should this work: > > steerpike*CLI> iax2 show registry > Host Username Perceived Refresh State > 64.26.157.230:4569 8886708729 64.26.155.62:14353 60 Reg > 64.26.157.230:4569 6134827945 64.26.155.62:14353 60 Reg > 64.26.157.230:4569 6136866597 64.26.155.62:14353 60 Reg > 64.26.157.230:4569 6136866675 64.26.155.62:14353 60 Reg > > There are four DIDs, and all are registered to an odd port (14353). Is > this OK? (I am using a Sonicwall TZ170 with "Enable Consistent NAT" on). > > > - MikeIf memory serves me properly what you are showing looks correct. You server is registering to your provider on port 4569 as it should. Their server is seeing you register from 64.26.155.62 and using the prt 14353 which is the port that your firewall has given that outgoing connection. Possibly that the firewall is removing that connection port after some time and your provider cannot get back to your box? Try setting the reregistration time lower than 60 and see if it helps.