Reserving outbound SIP channels on multi site solution

[Jake H]

Hi all,

We have a customer with an IPOSE with multiple sites, each site essentially operates as a seperate business so for billing purposes each site has a limited max channels available from the SIP trunk.

Currently we are limiting this for each site using location programming and each site has its own URI for outbound.

The issue stems from the customer then within each site needing further restrictions so there are always channels reserved for outbound, e.g. of 7 total allotted channels, 5 for incoming and 2 always available for outgoing, for a total of up to the full 7 available for outgoing when free.

I had thought about adding a second location, putting the phones that specifically need the outbound channels on a different subnet and restricting like this, however this means that these phones either only have access to 2 channels max, not the full 7, or they do have access to the full 7 but the site then has access to up to 12 channels which will upset the billing/ usage policies of the company.

I have also thought about adding a URI for incoming for each site that will restrict inbound calls on their entry to the system, and then a seperate URI for each site for outbound. The only issue with this is they currently have 7 sites and have approximately 200 DDI's. There is the potential for another 40 sites to be added to this system meaning thousands of DDI's so an individual URI per DDI will not be viable.
And by extension an Individual SIP trunk per site is not viable either.

My thoughts to develop this idea would be, can you have an inbound URI that captures a specific range of numbers, e.g. 08005000XX capturing 0800500000 to 0800500099
I'm not sure if that's possible but it might allow to restrict per entire site rather than per DDI..

Unless someone can think of a better way to do this?

 

[Pepp77]

You could create multiple Auto URIs for each incoming group - ID 200, ID 201, ID 202 etc for both in and out

Limit the number of calls on these to how many incoming calls you want and program the ICR accordingly (so DDIs to be used on ID 200, has this ID in the ICR).

You can then create multiple outgoing URIs using the IDs of 300, 301, 302 etc for both in and out.

Again limit the number of calls on these URIs to the number you want for each group.

For this to work you will not be able to have any catchall ICR entries

But would have something like this (2 company example). Line 1 is incoming company 1, line 2 is incoming company 2, line 3 is outgoing company 1, line 4 is outgoing company 2

The theory seems good to me, but never done it in practice.



| ACSS SME |