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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DomainAdapter or how to manipulate sip domain.

B0nes

Systems Engineer
Aug 8, 2023
3
RU
Hello everyone!

A bit about the configuration:
CM 8.x
SM 8.x
SMGR 8.x
AADS
J1xx series phones and IX Workplace
Users with SM, CM and PS profile set on SMGR. Login to IX workplace through login@domain.

The company is planning a domain change project for users. During testing, I moved one user to the new domain and started testing calls.
User 1 - 1234@abc.com
User 2 - 4321@xyz.com

Both users are registered on the same SM, with different registration ports. When User 2 calls User 1, the call goes through successfully (the adaptation odstd=abc.com is applied). However, when calling in the opposite direction, the call results in a 404 Not Found, which is logical since the user 4321 with the domain abc.com does not exist.

In the Session Manager documentation, there is a mention of the DomainAdapter, which, according to the description, seems to perform the required function, i.e., it allows changing the domain based on the dialed number. However, the documentation does not provide any details on how to use this adapter or what parameters it supports.

I also tried using the Conditions - Regular Expression Adaptations method, but when applying it to the SIP Entity, the call gets rejected with a "Request Timeout" regardless of what action I choose, even something as simple as changing the digits in the number causes the same result...

If anyone has documentation or knowledge on how use DomainAdapter or to accomplish this task, I would be extremely grateful.

PS:
Session Manager - Global Settings - Set Precedence for Routing = RegularExpressions.
 
Just spit balling here. I would think that as long as both domains are listed in Domains under routing would be all you'd need. Calls to/from/between SIP endpoints use SM database routing and not dial patterns.
 

Part and Inventory Search

Sponsor

Back
Top