That's definitely the problem. There's nothing in SIP that will tell the remote party how to start the conversation. They must start the conversation by sending you the first invite on port 5080/udp.
This is configurable in their equipment. And, if it's not you may need to look for a different provider. I'll note that this is the case only for IP authenticated trunks. User name / password authenticated trunks work differently and do not need to worry about this. This is because your sipXecs system initiates the trunk connection through your firewall and keeps the session open in the firewall with a keep-alive. Mike On Fri, Dec 9, 2011 at 5:59 PM, Matthew Kitchin (usenet/public) < [email protected]> wrote: > They have to send to 5080. That is likely your entire issue. > -----Original Message----- > From: Chris Wiegand <[email protected]> > Sender: [email protected] > Date: Fri, 9 Dec 2011 15:52:26 > To: [email protected]<[email protected]> > Reply-To: Discussion list for users of sipXecs software > <[email protected]> > Subject: [sipx-users] Transfers failing from AA - maybe sipXbridge is not > involved and should be? > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
