10 Replies Latest reply on Feb 27, 2014 1:08 PM by txcomer

    SIP Identity and DID

    txcomer New Member

      Hello,

      Is there a limit to the number of SIP Identities or DIDs that can be assigned to a user, ring-group, AA, etc?

       

      Is there an overall system limit for the number SIP Identities or DIDs that can be assigned?

       

      Thanks.

        • Re: SIP Identity and DID
          jayh Hall_of_Fame

          I'm sure that there is an absolute limit (there's only so much configuration memory in flash) but it's high enough that it hasn't been an issue for some pretty complex configurations.  How many do you need?

           

          If you need a huge number of DIDs that need to route to a destination, the voice grouped-trunk configuration might be a good place to look as it can handle wildcards and a patterns similar to regular expressions. 

            • Re: SIP Identity and DID
              txcomer New Member

              Thanks. We have customer that is going to have a 7100 with PRI and they will have 2054 DID numbers. I have found that there is a limit of 10 DIDs that can be applied to a single entity; user, ring-group, AA, etc. Just wanted to know if there is a AOS imposed limit on SIP-identies or Aliases per entity and for the system overall.

               

              There is still some data collection from the customer to be done so I may not have the whole picture but the number of DIDs gave me pause as I have not seen/supported a system with that many before.

                • Re: SIP Identity and DID
                  jayh Hall_of_Fame

                  If the DIDs are going to a PRI, then the voice grouped-trunk configuration is perfectly capable of handling it.  You can summarize if the numbers fall into logical patterns.

                   

                  For example, the 2000 numbers 312-555-0000 through 312-555-1999 can be handled with one line:

                   

                    accept 312-555-[01]XX

                  1 of 1 people found this helpful
                    • Re: SIP Identity and DID
                      txcomer New Member

                      Voice grouped-trunk number templates is for outbound calling. There would still have to be DIDs or Aliases assigned to users, ring-groups, etc so the  7100 knows where to terminate incoming calls for specific numbers.

                        • Re: SIP Identity and DID
                          jayh Hall_of_Fame

                          OK, so the PRI is the incoming feed to the 7100 and it is supporting 2054 incoming numbers to end stations rather than to a trunk going to another PBX?  In that case I'll have to defer to someone with more knowledge of this specific platform. 

                      • Re: SIP Identity and DID
                        gouc Employee

                        txcomer - I am intriguied by this customer application. Are there any details you can share on the requirements for 2000+ DIDs for a small business IP-PBX? I know I am not helping address your questions as yet, but my curiosity is getting ahead of me. Perhaps once I understand the business need behind it, I may be able to assist.

                         

                        Thanks,

                          • Re: SIP Identity and DID
                            txcomer New Member

                            Actually I am not clear on why they will have that many DIDs either. There is still data discovery to be done by the customer's account team. I just really need to know the answer to the original question so we know if the 7100 will even be able to support the customer needs.

                          • Re: SIP Identity and DID
                            jayh Hall_of_Fame

                            Possible ugly hack, if most of the numbers are going to ring the same endpoint(s):

                             

                            • Create a voice trunk type SIP with a destination of 127.0.0.1 or a loopback IP created on the 7100
                            • Create a voice grouped-trunk and put the bulk of the numbers in it.  Use DNIS substitution to collapse whatever is dialed to a single pattern. 
                            • Point the grouped-trunk to the SIP trunk created in step 1.
                            • Route the incoming calls to the appropriate endpoint.

                             

                            I haven't tried this, I don't even have a 7100, but it might work.

                             

                            Or sell them 2,054 phones. 

                        • Re: SIP Identity and DID
                          Employee

                          txcommer,

                           

                          Were you ever able to get the needed details from the customer?  If you have any additional information on this that others may benefit from, please come back to this post to provide an update. Also, if any replies assisted you, please mark them as Correct or Helpful as the case may be with the applicable buttons. This will make them visible and help other members of the community find solutions more easily. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

                           

                          Thanks,

                          Matt