General IAUG Discussion Forum

 View Only
  • 1.  Domain Based Routing

    Posted 12-02-2021 06:59 PM
    Anyone using domain based routing in SMGR vs the traditional dial plan ranges?  I have a system running very clean by routing all DID from SBC to CM with an domain; AAR and ARS use specific trunks/signaling groups with a far end domain like or  From there SMGR has 2 entries per domain (if needed) +11@domain goes to PSTN/SBC and 11@domain stays on net and routes to whatever SIP entity I define that domain to use.

    We are preparing to deploy a new large system and I have gotten some feedback that I should use a Number Range in SMGR instead and not go to CM unless necessary.  I understand that all calls don't need to use CM but the cleanliness is so nice and Techs only need to enter routing changes in AAR or ARS and use the Trunk Group specified for where it needs to end up - SMGR sees the domain and the rest is automagic.

    Any feedback on what you are doing to simplify large DID swaths that are broken and not in large sequential groups to keep routing clean and understandable for the average day-to-day technician?


    duane belka
    SR Engineer
    Ascension Technologies
    evansville IN

  • 2.  RE: Domain Based Routing

    Posted 12-03-2021 10:23 AM

    How "large" is large?  CM is a resource constrained, it's true, but I still believe domain-base routing to be far more effective.   Additionally, there are good reasons to always pass PSTN calls into CM, esp. if your domains and signal groups are correctly configured to land the call back into the correct trunk group.  The two best reasons are COR (being able to restrict what the incoming caller can do) and channel count (because most ITSPs still sell you "channels", which you need to adhere to for both in and out).  Session Manager CACs can somewhat address the latter issue, though they don't count calls, per se, they accumulate bandwidth usage based on the codec selected in the SDP.   Makes me think I should put in a Feature Request for Locations to allow restriction by call count (vs bandwidth).


    Anyway, I'm not a fan of muddying-up the Dial Patterns in SMGR without a good reason.  One possible "good reason" is that you have more than one feature server (i.e. multiple CMs, Zoom Phone's BYOD, Teams Direct Routing).  With those you'd need to call out specific numbers to send off to the correct place (with perhaps a default to one of them).




    Sam Osheroff

    UC Engineer

    UW-IT Infrastructure - Telecom

    University of Washington

    Internal: x16362 Direct: 206.221.6362


  • 3.  RE: Domain Based Routing

    Posted 12-03-2021 11:08 AM
    Thanks for the feedback Sam.  By "large"  I mean multiple PODFX instances with multiple CM's within each POD.  SBC at edges for local PSTN delivery with failover to "core" POD SBC and the ability to route between PODS.  In the end 400K DID and 100K endpoints (SIP) across the environment.

    Upcoming PTO 
    Duane Belka
    Tech Engineering Sr Analyst
    Connect Engineering
    Ascension Technologies

    t: 248-781-1788
    m: 812-459-5863




    This email message and any accompanying data or files is confidential and may contain privileged information intended only for the named recipient(s). If you are not the intended recipient(s), you are hereby notified that the dissemination, distribution, and or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender at the email address above, delete this email from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege.

  • 4.  RE: Domain Based Routing

    Posted 12-03-2021 01:08 PM
    +1 to what Sam said as well.  The route Avaya is going is to route everything directly in Session Manager, but when you have to consider COR/COS, feature sets, media anchoring, etc., it becomes much more difficult to replicate the stuff that we are used to having CM do for us.  Also, if you have any isdn/digital/h323/analog endpoints or gateways you end up having to involve CM regardless.

    Nick Kwiatkowski
    Director of Design and Engineering
    Michigan State University
    East Lansing MI