On Fri, 2009-09-11 at 10:50 -0400, M. Ranganathan wrote: > sipx proxy sends sipxbridge an INVITE through TCP. > sipxbridge tries to reply with a RINGING but cannot do so because > sipxproxy is actually not listening on port 5060 but some randomly > generated port. > Hence the 180 RINGING cannot be sent back and sipx bridge kills the > server transaction. Subsequently when a CANCEL for the server > transaction arrived, > I could not find the server transaction and rejected the cancel.
Eh? sipXproxy is supposed to be listening (both UDP and TCP) on port 5060. If it isn't, there's something seriously wrong. What does "netstat -ap" report? Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
