I don't think this is possible within sipxbridge. It sounds like they are sitting on a non-routed network that you have local access to, in which case this is plain routing and could be connected to with an unmanaged gateway (since it does not use authentication).
Can you route to the network the ITSP gateway is on from sipx without nat? If so, did you add it as a intranet subnet? Have you tried it as an unmanaged gateway? If the provider supports REFER, it should be as simple as adding an unmanaged gateway, which means sipxbridge role can be deselected altogether. This means you can still run remote users through media relay, if it is needed to support them. What you are asking for is two different IP's for sipx (one for users and one for trunking) to the outside world. You can only do this with an independent SBC that can manipulate the headers to pass on the IP's the ITSP wants. sipXbridge was not designed for this type of deployment in its current form. Hope this makes sense. 2011/1/9 Irena Dolovčak <[email protected]> > I am referring to the <global-address> and <external address> from > <bridge-configuration> located in > the sipx bridge configuration file (sipxbridge.xml) > > Without getting too deep into the reasons and problems; I need to have two > different public IP > addresses in this particular sipx deployment. > One standard public IP for sipx in general and a different one just for one > of the sipx bridges. > > The reason for this is that the main voice provider for this customer is > deploying SIP trunks over > physical private network without authentication and they demand that the > sipx has a private IP > address in a particular given subnet and the invites from field must > contain this address in order for > SIP trunk to work. The only way I can get this SIP trunk to work is if I > setup this private IP address > instead of the sipx public IP address. But this messes up a bunch of other > things (which I can get > around with complicated routing, but I would rather not..) > > So I plan to change the public IP address just for one of the sipx bridges > (there are two sipx bridges > with multiple SIP trunks from multiple providers). I intend to do this > manually through changing the > sipxbridge.xml configuration file. > > For this reason I ask what is the <global-address> for and what is the > <external address> for in the > sipx bridge configuration file? > > > > 2011/1/8 Tony Graziano <[email protected]> > > I don't follow the terminology you are using. >> >> Public address is used in two places. Once by sipxbridge and once by media >> relay (for remote users). >> >> When used by sipxbridge it is used for setting up calls to the ITSP so the >> ITSP knows it is coming from the "internet facing address" of sipx. This >> means the ITSP is contacting (usually, your firrewall) the system directly >> to send packets and is not handling nat traversal for you. >> >> When used by media relay, it is so media relay knows when destination >> pacckets arrive at it for invites TO sipx or REGISTER on port 5060, that >> they originated via that IP address, which helps the system construct your >> registration and calls. >> >> Please explain in better detail what you mean by >> >> external-address and global-address? where are you picking up those terms >> so your question can be answered. >> >> sipxbridge only has one address, the public facing one, since it only >> really communicates publicly, everything else it does is inside sipx... >> >> 2011/1/8 Irena Dolovčak <[email protected]> >> >> oh yes, my bad.. >>> >>> I just wanted to know what is the difference between external-address and >>> global-address in sipxbridge..? >>> >>> >>> On Sat, Jan 8, 2011 at 1:53 PM, Tony Graziano < >>> [email protected]> wrote: >>> >>>> sipxbridge is not used for remote workers. >>>> >>>> sipxbridge is for trunking >>>> media relay is for remote workers >>>> >>>> >>>> >>>> On Sat, Jan 8, 2011 at 7:49 AM, Irena Dolovčak < >>>> [email protected]> wrote: >>>> >>>>> Tony thanks for your reply.. >>>>> And the global-address is used for remote workers, right? >>>>> >>>>> >>>>> >>>>> On Sat, Jan 8, 2011 at 1:40 PM, Tony Graziano < >>>>> [email protected]> wrote: >>>>> >>>>>> Public address? It is the contact ip the itsp uses to connect to >>>>>> sipxbridge. This is the most common configuration becase a lot of itsp's >>>>>> do >>>>>> not handle nat traversal on sip trunks for you. >>>>>> >>>>>> On Sat, Jan 8, 2011 at 7:24 AM, Irena Dolovčak < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi to all! >>>>>>> >>>>>>> I have just one quick question.. In the configuration of sipxbridge >>>>>>> what is the "external-address" used for? >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> -- >>>>>>> Irena Dolovčak >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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/ >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Irena Dolovčak >>>>> >>>>> _______________________________________________ >>>>> sipx-users mailing list >>>>> [email protected] >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>>> >>>> >>>> >>>> >>>> -- >>>> ====================== >>>> Tony Graziano, Manager >>>> Telephone: 434.984.8430 >>>> sip: [email protected] >>>> Fax: 434.326.5325 >>>> >>>> Email: [email protected] >>>> >>>> LAN/Telephony/Security and Control Systems Helpdesk: >>>> Telephone: 434.984.8426 >>>> sip: [email protected] >>>> >>>> Helpdesk Contract Customers: >>>> http://support.myitdepartment.net >>>> >>>> <http://support.myitdepartment.net>Blog: >>>> http://blog.myitdepartment.net >>>> >>>> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>>> >>>> >>>> _______________________________________________ >>>> sipx-users mailing list >>>> [email protected] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>>> >>> >>> >>> >>> -- >>> Irena Dolovčak >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.326.5325 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Contract Customers: >> http://support.myitdepartment.net >> >> <http://support.myitdepartment.net>Blog: >> http://blog.myitdepartment.net >> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Irena Dolovčak > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
