Anyone have a paddle? Thank you everyone for the suggestions of the past few weeks. My saga with AT&T may be coming to an end, unfortunately in a negative way. AT&T is starting to pull at straws since they have basically denied my requests for both a port change for signaling (5080 for sipXbridge) and enabling the B2BUA feature in their managed router. Both of which I understand may have fixed my issue.
The main issue is that don't support REFER (like a lot of ITSP it sounds) which screws up transfers. This messes with incoming calls to a handset or the AA which we need when it comes to transfers. This basically renders the AA useless. I have a couple of people on their end pulling for me and looking to iron this out. Getting AT&T labs involved, etc. Couple of options I wanted to run by everyone. Looking for a sanity check if it is possible and how difficult if it could even work. Some may be crazy I know.... Lack of sleep and head is throbbing after banging it against the wall repeatedly. 1) Have AT&T configure their router to do a port mapping (incoming 5060 --> 5080) 2) Have AT&T hand this off to us not via SIP, but a PRI 3) Add something in between the SIP trunk and SipX. InGate? (stab in the dark) 4) Ditch the great system called SipX in which I was really looking forward to the 4.2 release, for some other open source or commercial product (boooooo!) Anything else? Thanks! Andrew _______________________________________________ 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/
