I am setting up a new Sipx server (4.0.2) with a gateway to Vitelity
through sipxBridge. I am able to call outbound OK on this trunk, but
inbound calls don't complete successfully. The Sipx server is on an
internal -subnet IP address that is 1:1 NATed to an external IP
address that routes to the Monowall firewall serving my site.
When looking at a Wireshark trace, I can see the incoming invite from
Vitelity. Sipx sends back a 100 trying message to the vitelity IP
address. All good so far.
However, the next set of packets, and all subsequent ones, consist of
SIP packets (invite, trying, etc.) that are sent back and forth from
internal IP to the external IP and vice versa. For example,
immediately following the first 2 packets above come:
1. an INVITE from INTERNAL IP to EXTERNAL IP
2. an INVITE from EXTERNAL IP to INTERNAL IP
3. a TRYING from INTERNAL IP to EXTERNAL IP
4. a TRYING from EXTERNAL IP to INTERNAL IP
Packets like these go on an on, intermixed with "TCP segment of a
reassembled PDU" and other TCP messages until you finally start to
see "SIP Status 483 - too many hops, with sipfrag"
After the second packet (TRYING back to Vitelity IP) no packet ever
again goes to or from Vitelity. It looks like things are looping
back and forth between the firewall and sipx server.
Does anyone have a clue as to what is going on and how to fix it?
I'll be glad to send the actual traces, if you care to look at them.
Thanks!
Jeff
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
