Search results

I believe I have resolved the issue with the wrong IP being sent in the "Contact" header. I did this by changing the ext-rtp-ip and ext-sip-ip in the internal profile to be "auto-nat". (I previously thought it was "autonat" which caused me issues). For the external profile they are still set to...

Yes, the external5090 profile is listening on port 5090. The idea behind the 5060->5090 port forward rule is to allow roaming handsets to not configure which port to connect to, they can leave it as the default (5060 for a lot of clients) and it will work whether they are external (elsewhere on...

I think you're right about the ACK's being mis-routed, as per my last reply. I suspect the incorrect "Contact" header is set by the internal handset which assumes the other endpoint is also on the LAN. I assume there's some setting in the PBX to rewrite this header to the correct value, but...

It appears as thought the pbx is sending the internal IP in the "Contact" field, as seen below. I suspect this causes the external handset (the one which initiates the call) to send an ACK to the given contact address (which is not correct as far as the external handset is concerned), therefore...

I have tried disabling the firewall on the router, it makes no difference.

Hi all, I'm having a problem where calls are dropped after 30 seconds, even though 2 way audio is working. I suspect it's somehow a NAT issue, and by doing a siptrace I was able to determine that the call is being dropped due to no ACK being sent by the external handset. I can't figure out why...