Segregate Traffic Using Far End Domain

[Wanebo]

I'm trying to segregate SIP traffic coming from one of our phone systems, through Session Manager, and into our CM utilizing the Far-End Domain field in the signaling group. The idea is to have greater control of the trunk characteristics while not affecting traffic coming in from other systems on the main CM trunk.

So, I set my new sig group to have a far-end domain of phonesystem.sip.companyname.com and then created the trunk. I added the domain phonesystem.sip.companyname.com to the domains on the SM. I then added odstd=phonesystem.sip.companyname.com and osrcd=phonesystem.sip.companyname.com to the digitconversion adaptation for the special phone system. But I do not see the CM segregating the traffic to the new trunk. It still comes in on the main CM trunk which has a far-end domain set as sip.companyname.com. The main trunk sig group number is in the 900's and the new trunk's sig group is in the 100's.

Shouldn't the more specific domain in a lower numbered sig group tell the CM to tag the traffic as belonging to that new trunk?

 

[kyle555]

Yes, it should. Briefly, CM will grab all sig groups that match IP and port and use the lowest numbered sig group that matches AND where the entirety of 'fr end domain' fits in the received invite.

To say, sig 1 companyname.com would steal everything.

 

[mattKnight]

So you need the more specific domain to have a lower sig group number

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[Wanebo]

The CM appears to use the proper new trunk for outbound routing, but still keeps the call on the Main (less specific far-end domain name and higher sig group number) trunk for inbound calls. Packet captures show that the SM is applying the full (more specific) domain to the FROM, PAI and HISTORY headers

Is there a feature or setting to apply to get it to assign those calls on the inbound side correctly?

 

[kyle555]

Outbound is ARS/AAR - independent of this domain matching thing.
Is SM applying the more specific domain on the TO header? That's what CM is looking for. Maybe your odstd adaptation has a typo?

Now, what entity is the adaptation applied on? CM or the other thing? Cause odstd on the other thing may just apply it to calls from SM to the other thing.

Lookup iodstd in the sm admin guide. Don't have it handy, but that might take incoming stuff from other thing to SM and change the TO header to what you want.