This is an issue with the limitations of the patton gateway acting as a b2bua. I used that for a while and found transferring calls did not work with another provider either.
I think doing this with a patton gateway is hazardous. It will work with most providers with DID's, but being able to transfer it after it is received is another thing. The AA will be one of the most difficult things to overcome. I don't tihink this is a sipx issue though, it's just an interoperability issue for the patton being able to do something it really wasn't really meant to do. Both your gateway and provider need to support refer, and that's the bigger issue. I'm on my 3rd ITSP already and they are NOT all the same with the options they support. Tony >>> Matus <[email protected]> 02/13/09 10:17 AM >>> hello, I'm using voxbone as a trunk provider for my sipx server ( 3.10.2 on gentoo ). When im using direct connection - voxbone is directly connecting to sipx server - it is working 100% perfectly. But when i try to use patton between voxbone and sipx then there is a problem. Autoattendant ( which is default on my sipx ) is working OK, but any forward to real human extension will end with silence after "please hold while i transfer your call" in 10% of all attempts. 90% of all connections working fine. I have no NAT, all machines using real IP's, no firewalls. In tshark i can see this message: SIP/sipfrag Request: NOTIFY sip:[email protected]:5060, with Sipfrag(SIP/2.0 503 Service Unavailable). thanks for help Matus _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
