What is domain based routing in the Avaya world?

[SurferdudeHB]

I'm learning SIP and ASM and I'm not fully understanding why you need a domain e.g. google.com is inserted in the "name" field under Domain Management in ASM 6.0

I found the following description in the Help section but it still doesn't make sense to me.
"The Domains screen is used to create a set of domains and sub-domains to enable an enterprise to use domain-based routing. This information is used to determine if a SIP user is part of the enterprise SIP network. Domains determine if the Session Manager Dial Plan can be used to route a particular call. Sub-domains are automatically checked if not provisioned.

 

[kyle555]

Think in terms of multi-tenanting. You have widget.com and gadget.com. If you dial 1234@widget.com it gets different treatment than 1234@gadget.com in your dial patterns in Session Manager.

Or, when I don't know what a customer's numbering plan is and I need to make something work - like Experience Portal or Aura Messaging, I can have a SIP signaling group in CM with a far end domain of "voicemail.gadget.com".

In SM, I'd have a dial pattern of "x" for domain "voicemail.gadget.com" and say "route that to the voicemail SIP entity.

Basically, combining that with traditional numbering plans adds flexibility to your call routing.

 

[SurferdudeHB]

Ok it's starting to make sense..
The 1234@widget.com domain where does that reside? In a web server? Is this packet routing on layer 7?

Should I interpret SIP traffic/sessions the same as a web traffic i.e. when your browser if fetching the content of a web page?

 

[kyle555]

You build that domain in SM, and whatever adjuncts route to SM.

So, if you have CM sending calls to SM for voicemail, the IVR, and your branch in Asia, you can have 3 separate sig/trunk groups in CM (all using the same entity link in Session manager) and put the far end domain in those sig groups as voicemail.gadget.com, ivr.gadget.com and asia.gadget.com

When SM gets those sip invites, it can factor in that domain into its routing logic to determine where to ship them off. And then the domain you setup in AAM can be "voicemail.gadget.com" and you have a sip domain of asia.gadget.com in whatever far end PBX services that area.

 

[msalvary]

kyle555, thanks for your post. Cleared up some misunderstanding I had. I have a question - in the case where you setup domains as you described, is there any special consideration for the setting up Locations, or not really?

 

[kyle555]

There aren't really any special considerations to using locations. The rules are that every SIP entity must have a "home location" defined, and it is a factor in call routing in SM just like domains. You can choose to use 1 domain for everything and 1 location and just use digit codes to get everywhere - or you can use locations, domains, or a combination of both.

Consider: you have 100 branches with Audiocodes gateways with copper trunks for 911 that are SIP connected to SM. You have 100 subnets defined in SM for "locations". When a user dials 911 through CM, and CM knows to route that to SM, SM will look at the IP address of the originating telephone and match it to the "location" of site 5 and route it to the Audiocodes gateway at site 5. That way, your dial pattern for 911 will look like:
"If you dial 911 from location 1, route to the SIP gateway at location 1"
"If you dial 911 from location 2, route to the SIP gateway at location 2"
"If you dial 911 from location 3, route to the SIP gateway at location 3"

As in my previous example, half of those sites could be @widget.com and the other at @gadget.com, but it doesn't really matter. Basically, domain based routing is factoring in whatever's after the @ symbol to choose a destination, and location based routing is using whatever the source IP was as a factor in choosing the destination.