can Session Manager replace contact header in SIP invite

[ajshetty]

My scenario: CM connected to Session Manager to Shortel
CM---- Session Manager---- Shortel

The CM sending call to Session Manager with contact header as Cmext@cmipaddress. The Session Manager can replace destination host URI and Source URI but sends the same contact header and doesn't replace it with its ip address or domain name.
The Shortel when it receives the Invite its looks at contact header and decides that the calling party is CM and not session manager. It cannot route the call since its trunk group has Session Manager IP address and not CM ip address. The other way with call from Shortel to Session manager to CM works fine with only session manager IP address.

We can make it work when we add two trunks on Shortel one with Cm IP address and one with Session Manager address.
Question: Can we modify contact header to Session manager IP address or domain name so that Shortel doesnot see CM address. This is required becuase if we have multiple CM behind Session Manager we cannot keep having so many trunks on one shortel system.
I know SBC can do it can Session Manager do this...?

[kminin]

SMGR
Home / Elements / Routing / Adaptations - Adaptation Details
odstd=Shortel osrcd=Shortel

Home / Elements / Routing / SIP Entities - SIP Entity Details -> Adaptations

[ajshetty]

odst and osrcd is for changing the headers of the invite either destination address or Source address it nevers touches contact address. The contact address is the address of the IP Phone or CM system system which is initiating the call via Session manager. Shoretel system cannot work with Avaya CM or Session Manager or SES server it requires SBC (B2BUA) to always rewrite the invite message with SBC IP address.

[domin69]

Originally Posted by ajshetty

My scenario: CM connected to Session Manager to Shortel
CM---- Session Manager---- Shortel

The CM sending call to Session Manager with contact header as Cmext@cmipaddress. The Session Manager can replace destination host URI and Source URI but sends the same contact header and doesn't replace it with its ip address or domain name.
The Shortel when it receives the Invite its looks at contact header and decides that the calling party is CM and not session manager. It cannot route the call since its trunk group has Session Manager IP address and not CM ip address. The other way with call from Shortel to Session manager to CM works fine with only session manager IP address.

We can make it work when we add two trunks on Shortel one with Cm IP address and one with Session Manager address.
Question: Can we modify contact header to Session manager IP address or domain name so that Shortel doesnot see CM address. This is required becuase if we have multiple CM behind Session Manager we cannot keep having so many trunks on one shortel system.
I know SBC can do it can Session Manager do this...?

Hello ajshetty,
Were they able to solve the problem?
I have the same problem, but with an NEC sv8300 PBX.

Thx

[singh446]

ajshetty

Hi There,

By any chance you this configuration, im struggling to work with Shoretel, same way i see CM IP as well.

[singh446]

Originally Posted by ajshetty

My scenario: CM connected to Session Manager to Shortel
CM---- Session Manager---- Shortel

The CM sending call to Session Manager with contact header as Cmext@cmipaddress. The Session Manager can replace destination host URI and Source URI but sends the same contact header and doesn't replace it with its ip address or domain name.
The Shortel when it receives the Invite its looks at contact header and decides that the calling party is CM and not session manager. It cannot route the call since its trunk group has Session Manager IP address and not CM ip address. The other way with call from Shortel to Session manager to CM works fine with only session manager IP address.

We can make it work when we add two trunks on Shortel one with Cm IP address and one with Session Manager address.
Question: Can we modify contact header to Session manager IP address or domain name so that Shortel doesnot see CM address. This is required becuase if we have multiple CM behind Session Manager we cannot keep having so many trunks on one shortel system.
I know SBC can do it can Session Manager do this...?

Hi There,

By any chance you have this config, im struggling to get it working

[jwaber]

I do not have the fix for your problem, but I do know that the way you are trying to fix the problem is not correct.

The CONTACT header must always contain the address of the originator of this message. (In the request, the CONTACT header holds the address of the requestor; in a response it contains the address of the responder.) The CONTACT header tells each User-Agent (UA) the real address of the other UA. Both UAs will store the address found in the CONTACT header and use when constructing the Request-URI of all subsequent requests. In a simple world, that means that subsequent requests would travel directly from UA to UA.

To ensure that a SIP Proxy (like Aura Session Manager (ASM)) stays part of the SIP dialog, the proxy will insert a RECORD-ROUTE header into the Request as it goes by. The receiving UA is obligated to both keep a copy of all RECORD-ROUTE headers, and to copy the set of RECORD-ROUTE headers into the response back to the requesting UA so that it gets a copy of the headers.

Each Record-Route header contains the address of the proxy (e.g. ASM) that injected it into the request.

When generating subsequent requests, both UAs are obligated to convert the RECORD-ROUTE headers into ROUTE headers and inject them into their request.

When any SIP Proxy receives a SIP Request, the proxy will look for the presence of ROUTE headers. If they exist, the Proxy is obligated to ignore the address in the Request-URI header and route the request to the address found in the top-most ROUTE header. Once that ROUTE header has served its purpose, the recipient proxy (e.g. ASM) will delete its ROUTE header from the request and then look for the presence of any more ROUTE headers. (So, note that ROUTE headers get deleted from the request by the Proxy that injected the RECORD-ROUTE header.) ROUTE headers always take precedence over the Request-URI. When there are no longer any ROUTE headers in the request, the proxy will route the request to the address found in the Request-URI.

In summary, in the requests I suggest checking whether the ROUTE headers are being correctly included and addressed. (In the responses, you should be checking the VIA headers).

It is the ROUTE header that will correctly direct the request through ASM to CM. Do not mess with the CONTACT header!