Right, which is why I wondered why more ITSP that send on port 5060 do not work for inbound calls.
As a test, I just set my test vitelity.net account to not use registration and forced it to use port 5060. Test call comes in and works has audio. Transfer fails...which I assume is because they don't handle refers. So it would seem that if an ITSP supported referese sipxbridge would not be needed for inbound calls...only outbound. Also, it might not be hard to get sipxproxy to detect the refer for inbound calls and then re-invite sipxbridge into the path. this would reduce the issues people have with itsp sending to port 5080. >>> Tony Graziano <[email protected]> 08/07/10 10:42 AM >>> Sipxrelay anchors the media. Sipxbridge separates trunking from pure sip and remote users and acts as a gateway out via carrier if the proxy authorizes the call. Sipxproxy sends the call (or rejects it) if there is validity to the invite to the user.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
