I noticed something for the first time yesterday ( issue 6422) : 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.
( Now sipxbridge should look at the remote TCP port rport and reply to it so I fixed that - *I am not saying this is a bug with sipx proxy*. Indeed this is the last bug I fixed for 4.0.2. ) However, I could swear this all worked. i.e. sipx proxy was doing symmetric TCP signaling and had its TCP socket bound to 5060. Can somebody verify if there was a recent change in behavior? Thanks. Ranga -- M. Ranganathan
_______________________________________________ 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/
