On Sun, 11 Sep 2011 13:54:11 -0400, Tony Graziano wrote: > either make the remote branch remote users or connect the two sites via vpn > and add the new branch sipx server as acl ti the medians and use it as a > gateway.
Thanks very much for the input. I have a better idea of what I am after now. > On Sep 11, 2011 1:34 PM, "m...@grounded.net" <m...@grounded.net> wrote: >>> without explaining what you have now in a way other than "a really good >>> LD >>> deal". >>> >> LD meaning that with our PRI services, we get a good long distance deal. >> If possible, I'd like to use our current trunks to provide 4 lines to a >> remote sipx server. >> >>> How about stating how your existing gateway or trunk is implemented? Is >>> it >>> a PRI? Is it a trunk? Is there a VPN between the two locations? >>> >> I was asking about sipx itself but see how that comes into the picture. >> >> The remote location is a small office that will need 4 trunks. >> If we had to, we would put a gateway there to convert analog phone lines >> to SIP trunks for sipx. That however adds to the cost. >> >> At the main location, we use the mediant 2000 to provide PRI/SIP trunks >> to our local sipx servers. >> >> One option could be allowing the remote server to get it's trunks >> directly off of the mediant. >> Another would be to use a virtual trunk provider to get trunks into the >> remote. >> >> My question however, was if I could use one sipx server (at our main >> location) to provide the 4 trunks needed to the remote sipx server. >> >>> Without using a PRI as the gateway or having both of the servers using >>> the >>> same sipdomain, it a lot more problematic from both a security and >>> permissions standpoint. It also depends on the capabilities on the ISTP >>> "if" it is a trunk. >>> >> We would manage the remote so it could be in the same domain. I would >> control both LAN's so could just allow the remote and local servers to >> communicate via firewall rule. >> >> Mike >> >> >>> On Sat, Sep 10, 2011 at 1:56 PM, m...@grounded.net <m...@grounded.net> >>> wrote: >>> >>>> Sorry if I've posted this multiple times, had some mailer problems and >>>> don't see it in the list so am reposting. >>>> >>> >>>> --- >>>> >>> I have to install a small system at a remote location. The system will >>> only >>> have about 4 trucks so makes no sense to order lines/gateway etc. >>> What I was wondering about is either getting SIP trunks from a provider >>> or, >>> getting them from my main sipx box? >>> >>> I have never delved into anything like this and wondering if it is >>> possible >>> to extend trunks over to a second (or more?) sipx servers. >>> Should I be looking at Branches? >>> >>> The reason I would do this is because we have a good LD deal so want to >>> take advantage of that rather than having to buy trunks. >>> >>> >>> Thanks. >>> >>> Mike >>> >>> >>> _______________________________________________ >>> sipx-users mailing list >>> sipx-users@list.sipfoundry.org >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> >>> -- >>> ====================== >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> sip: tgrazi...@voice.myitdepartment.net >>> >>> Fax: 434.465.6833 >>> >>> Email: tgrazi...@myitdepartment.net >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> sip: helpd...@voice.myitdepartment.net >>> >>> Helpdesk Contract Customers: >>> http://support.myitdepartment.net >>> >>> Blog: >>> >>> http://blog.myitdepartment.net >>> >>> >>> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >>> >>> >>> Ask about our Internet faxservices! >> _______________________________________________ >> sipx-users mailing list >> sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
