Jump to content

Large number of inbound DID's on a single SIP trunk


andrewgroup
 Share

Recommended Posts

Sanity Check and commentary. We should soon be installing a new client with a dedicated 10Mb Fiber SIP trunk to deliver inbound 800 calls to 6 or more agent groups. 1 ACD may receive calls from as many as 100 800 numbers. Using Aliases in the ACD seems to be our first option. We might also consider adding more SIP trunks and having group of numbers spread across more trunks. Then using ERE's in the trunks to deliver calls to extensions, we would eliminate the aliases..

 

Before make the final decision, we want to better understand limitations, benefits in functionality or reporting.

Using more SIP trunks would allow the system to scale as other servers can be installed on a departmental basis.

Managing all of the alias in ACD's is going to be a pain in the #$%#$ if you wish to move or add a 800 number, but I guess that be problemation in the ERE expressions too..

 

The total 800 number count is near 500 and likely spread across 6 acd's. Having import function on ALIAS using CSV files might help in the future. otherwise COPY PASTE...

 

Any Thoughts

Link to comment
Share on other sites

Sanity Check and commentary. We should soon be installing a new client with a dedicated 10Mb Fiber SIP trunk to deliver inbound 800 calls to 6 or more agent groups. 1 ACD may receive calls from as many as 100 800 numbers. Using Aliases in the ACD seems to be our first option. We might also consider adding more SIP trunks and having group of numbers spread across more trunks. Then using ERE's in the trunks to deliver calls to extensions, we would eliminate the aliases..

 

Before make the final decision, we want to better understand limitations, benefits in functionality or reporting.

Using more SIP trunks would allow the system to scale as other servers can be installed on a departmental basis.

Managing all of the alias in ACD's is going to be a pain in the #$%#$ if you wish to move or add a 800 number, but I guess that be problemation in the ERE expressions too..

 

The total 800 number count is near 500 and likely spread across 6 acd's. Having import function on ALIAS using CSV files might help in the future. otherwise COPY PASTE...

 

Any Thoughts

 

Alias scale very well as the table in the PBX has a index (performance). Using the "trunk sends call to ..." option in the trunk is not an option if you want to enumerate all possible destinations there (a few ERE would be fine), the PBX has to step through that list for every incoming call.

 

I would get a good text editor to generate the list of alias names. Simple as it sounds, it can save you a lot of time editing the numbers and getting them into one line. "Emacs" is a science, but maybe there are also other editors that have some macro functionality that can automate editing.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...