Is there a way to when the MPP sends a call to the CM to have that particular application come in on a specific trunk group. Currently have all of my inbound traffic coming in on 1 trunk and want to be able to have calls from several numbers we have in our MPP applications to come in on another inbound trunk.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Session Manager / MPP / EPM 2
- Thread starter Jsaunde7
- Start date
avayaguy23
Systems Engineer
Cm, System/session manager 8 started supporting that kind of functionality. It’s domain based routing.
- Thread starter
- #3
-
1
- #4
sip invite hits cm
cm matches IP/port on near/far end
when you have many sig groups to the same sm with same ip/port, cm matches the far end domain.
Where the full far end domain of the invite fits inside the cm sig group far end domain, it is a match.
CM begins with the lowest numbered sig group and counts up.
So, if you have 1234@something.customer.com from SM:5060 to CM:5060
and sig group 1 is between procr and SM both on port 5060 and for domain customer.com it wins and is a better match than sig group 2 with the same IP/port with domain something.customer.com
Sig group 1 wins. then, hopefully, only 1 trunk group has sig group 1 as the choice. If so, you'll always come in on that trunk group. Otherwise, I guess it'd rotate between all trunk groups that have sig group 1 defined on page 1
cm matches IP/port on near/far end
when you have many sig groups to the same sm with same ip/port, cm matches the far end domain.
Where the full far end domain of the invite fits inside the cm sig group far end domain, it is a match.
CM begins with the lowest numbered sig group and counts up.
So, if you have 1234@something.customer.com from SM:5060 to CM:5060
and sig group 1 is between procr and SM both on port 5060 and for domain customer.com it wins and is a better match than sig group 2 with the same IP/port with domain something.customer.com
Sig group 1 wins. then, hopefully, only 1 trunk group has sig group 1 as the choice. If so, you'll always come in on that trunk group. Otherwise, I guess it'd rotate between all trunk groups that have sig group 1 defined on page 1
-
1
- #5
avayaguy23
Systems Engineer
I have a feeling you have a lot to learn and will more than likely break the system as domain based routing is complicated. It needs to be completely mapped out before implementing. The same kind of approach is done when you are designing your network. I would suggest researching signaling-group and domains.
dialtonebone
Technical User
Definitely domain based routing. Read up on "End to End SIP" Volumes 1 and 2. You can google for it and find it on the support site. Once you've done that start reading up on domain based routing. I've had no trouble making it work on CM 6.3.18+, and I'm sure it works on prior releases too.
edit: also pink stars to the above posts for an accurate and clear answer
edit: also pink stars to the above posts for an accurate and clear answer
You'll have a hard time making it come in on different CM trunk groups. Yes, domain based routing is one of the keys, but making AAEP send calls to those different domains is another.
By default, AAEP works with a single 'zone'. Thing of a zone as a trunk config. So, you can have many zones with many domains and that's one way of assigning a number of channels to sales.customer.com vs service.customer.com BUT your apps dial out the 'default' zone unless explicitly developed to use the zones you've defined. If they ain't there today, odds are you're not getting your AAEP apps tweaked.
That defines how AAEP makes a call. How are you transferring? If it's consultative, AAEP makes the 2nd call and waits to bridge it, so AAEP is placing the call. If it's a blind transfer, it's be a SIP refer and telling the first thing - like the SBC - to redirect the call.
If you're using SIP refer with an SBC, you could probably do some magic there triggering on the destination number to make it hit SM for one domain vs another and in turn get the separation you're looking for on CM.
By default, AAEP works with a single 'zone'. Thing of a zone as a trunk config. So, you can have many zones with many domains and that's one way of assigning a number of channels to sales.customer.com vs service.customer.com BUT your apps dial out the 'default' zone unless explicitly developed to use the zones you've defined. If they ain't there today, odds are you're not getting your AAEP apps tweaked.
That defines how AAEP makes a call. How are you transferring? If it's consultative, AAEP makes the 2nd call and waits to bridge it, so AAEP is placing the call. If it's a blind transfer, it's be a SIP refer and telling the first thing - like the SBC - to redirect the call.
If you're using SIP refer with an SBC, you could probably do some magic there triggering on the destination number to make it hit SM for one domain vs another and in turn get the separation you're looking for on CM.
- Status
Similar threads
