Hello All, Purpose:
Need to enable SipXecs bridge to solve lack of REFER support on SIP trunk. Problem: 1. SIP trunk provider has very strict rules about changing any configuration on any component that they manage. The SIP trunk comes with a Cisco 2801 router which is managed by the Operator and the port they signal on is 5060, this is a problem because all requests from the trunk are bypassing SipXecs bridge which listens on port 5080 therefore REFER can not be influenced. 2. SIP trunk Operator will not change port on trunk 3. SIP trunk Operator will not change config on Router, so I can not do any NAT as recommended here: http://sipx-wiki.calivia.com/index.php/SIP_Trunking_with_sipXecs:_Overvi ew_and_Configuration#2._Configure_SipXbridge 4. Do not want to change SipXecs internal port to some else, sounds dangerous and messy 5. Do not want to try another sip trunk provider My solution to the problem: (please provide feedback and answer my question below) 1. Configure two physical sipX components (a) sipXbridge(only) IP Add: 192.168.0.1 Port 5060 (b) sipXpbx(proxy) IP add: 192.168.0.99 port 5060 2. Configure (b) sipXpbx with provider gateway address 123.123.123.234 3. Configure (b) sipXpbx with route under gateway config to SipXbridge(a)IP add: 192.168.0.1 4. Configure SipXbridge (a) to receive/send signalling from provider gateway and pass to/from (b) sipXpbx Questions: 1. Will this solve my problems? 2. is my suggestion possible? 3. if so, how do I configure sipXbridge? 4. if so, are there any draw backs that you are aware of by implementing this design? Your help would be much appreciated. Regards Hiral Patel, Operations Manager OnRelay Elizabeth House | 39 York Road, London SE1 7NQ, UK | +44 (0) 2079028138| [email protected] | www.onrelay.com | This electronic message transmission contains information from OnRelay, Ltd., that may be confidential or privileged. The information is intended solely for the recipient and use by any other party is not authorised. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information or any attachment, is prohibited. If you have received this electronic transmission in error, please notify us immediately by electronic mail ([email protected]) and delete this message, along with any attachments, from your computer. Registered in England No 04006093 | Registered Office 1st Floor, 236 Gray's Inn Road, London WC1X 8HL -----Original Message----- From: M. Ranganathan [mailto:[email protected]] Sent: 27 January 2010 05:20 To: Hiral Patel Cc: [email protected] Subject: Re: [sipx-users] How to map external 5060 to internal 5080 On Tue, Jan 26, 2010 at 12:41 PM, Hiral Patel <[email protected]> wrote: > My SipXecs PBX is connected an unauthenticated sip trunk for which I need to > enable SipXecs bridge to be able to work around the lack of REFER support on > the sip trunk. > > > > The sip trunk sends to sipX on port 5060 therefore any incoming dialogue > bypasses sipXbridge and hence outgoing signalling also are bypassing > sipXbridge for the same dialogue. > > > > What I would like to know is if it is possible to re-configure sipX so that > sipXbridge listens on 5060 and sipX listens on 5080? No you should not configure it this way. You should configure it as follows: 1. Allow sipx proxy server to continue to listen on port 5060. 2. Allow sipxbridge to continue to listen on port 5080 ( both of these are defaults ). 3. Set the public port in the sipxbridge configuration page to port 5060. See http://sipx-wiki.calivia.com/index.php/SIP_Trunking_with_sipXecs:_Overvi ew_and_Configuration#2._Configure_SipXbridge 4. Map your NAT to send WAN packets arriving at 5060 to port 5080 on the host where sipxbridge is configured and vice versa. Ranga > > > > I understand there is a way to map external 5060 to internal 5080, but I am > not sure how to do this, can anyone help? > > > > Also, if the above is possible does it have any implications e.g. Ranga > mentioned that remote worker maybe effected? > > > > Regards, > > > > Hiral Patel, > > OnRelay > > > > _______________________________________________ > 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/ > -- M. Ranganathan _______________________________________________ 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/
