On Fri, 30 Dec 2011 11:34:58 -0500, Tony Graziano wrote: > using ip based acl (this is not authentication as registration is), was > answered in the first reply.i have a flowroute connection also and this is > how i configured it and i expressed how it works. I don't understand the > need to beat this discussion as it was answered exactly how to configure it > and use it.
I believe the beating part had little to do with my question and mostly about my use of the VPRI term and then the discussion which that in turn created. > I have only seen one provider require IP based ACL and normal > authentication to place calls, Level3. They are unique and sipx wont do > what they want without a carefully designed sbc connection. Flowroute just > gives you a choice of registration or ip based acl. ... use the > bandwidth.com template and be done with it. I described in more detail to Joegen what it is I am trying to find out about. > i still think of a vpri as a hardware based solution to share a > (hardware/circuit based) PRI. A PRI is a PRI. A sip trunk is not a PRI... And I think a washroom is a washroom and some argue that it's a bathroom. Go figure. Mike > > happy 2012 > > > kill this thread please? > > > On Fri, Dec 30, 2011 at 11:18 AM, m...@grounded.net <m...@grounded.net> > wrote: >> On Fri, 30 Dec 2011 21:59:38 +0800, Joegen Baclor wrote: >> I won't touch the subject of VPRI because it is not relevant to the >> actual issue. >> > >> I simply meant a virtual pri which is a term I saw somewhere and figured >> it's pretty self explanatory anyhow. > I'll explain it in case someone comes across this thread. > > The term "Virtual PRI" is just marketing but obviously, it is becoming very > well known with voip providers. > It is more or less just a billing method for a pool of channels which > multiple DID's can be used over. Basically the SIP version of a physical > PRI. > Say you need 8 simultaneous calls, you order a virtual PRI with 8 channels. > That will allow you to have 8 active calls. > It is SIP based which means it doesn't have the usual PRI signaling or a > physical copper circuit requirement. > >> either authenticated via user name or password or via an ACL which we >> here call IP Auth. What receives them on the other end can have any >> > >> Usually, when using an ITSP, we just set up a gateway on Sipx which >> allows for name/password for authentication. >> > However, when I spoke to a flowroute support tech, he told me that if I > used a virtual pri, that I should allow the pbx to authenticate via IP > rather than user name and password. He said this would prevent each server > from having to authenticate multiple times and that it would be a bit > better on their side. > >> On the flowroute gui, there is an 'inbound routes' section which allows >> one to define routing and authentication for each DID. >> > So my question is about sipx and how I can make use of the virtual PRI. If > I don't use the name/password authentication section in the Gateway fields, > > What I don't know is if Sipx might have any configuration requirements in > order to use the multiple channels. > > In the Gateway/Details/ITSP Account section, there is a Username and > Password section. If I leave these blank and flowroute is set to use > IP/Auth, will sipx see this gateway as a multi channel one (like my > audiocodes MK2 for example) or is there something else I need to set up. > > >> Mike > >> >> On 12/30/2011 06:10 AM, m...@grounded.net wrote: >>> I need to install 4 separate sipx systems in four separate locations. No >>> interoffice communications. >>> All of the sipx systems could benefit from the use of a VPRI rather than >>> traditional. >>> >>> I use ITSP's for individual lines when we need an area code that our >>> local telco cannot handle. >>> On sipx, I usually just create an ITSP device in the gateway section >>> and >>> let it authenticate via user name/password. >>> >>> In this case, due to the number of lines per server (4 to 8), it doesn't >>> seem like a good idea to authenticate each and every DID individually >>> for >>> example and would prefer using an IP based authentication for the whole >>> server. >>> >>> I'll be using flowroute for the systems but am not sure how to configure >>> sipx to authenticate once based on IP over a user name/password. I don't >>> see anything which would allow me to do this in the Gateway >>> configuration >>> section. >>> >>> Can someone shed some light on this please. >>> >>> Thanks very much. >>> >>> Mike >>> >>> _______________________________________________ >>> 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/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
