I have a SIP peer set up that uses port 5065. If I use the IP address of the
peer in sip.conf, everything's dandy.

 

If I use the hostname, the REGISTER packets go to 5065, but the OPTIONS
(i.e. as a result of qualify=yes) packets go to 5060, which are unanswered
by the remote end.

 

Anyone seen this before? It's causing the peer to be marked as unreachable
even though it's registering correctly.

 

--

Nabeel Jafferali

X2 Networks

 

Reply via email to