CM: incoming SIP trunk calls to local CM h323 extensions are routed to a PRI trunk instead of terminating on the called extension

Doc ID		SOLN293209
Version:		2.0
Status:		Published
Published date:		14 Dec 2017
Created Date:		20 Jul 2016

Author:

Levente Szabo

Details

R016x.03.0.124.0
03.0.124.0-21291

Problem Clarification

Incoming SIP trunk calls to local CM h323 extensions are routed to a PRI trunk instead of terminating on the called extension

List trace may show errors 487 Request Terminated and 483 Too Many Hops

Cause

- Authoritative Domain mismatch between the near end network region and the domain name contained in the incoming SIP message "From" header

- proxy select route pattern misconfiguration. It makes no sense to point it to a PRI trunk. It should point to a SIP trunk that connects to a Session Manager

Solution

- make sure far end sends domain name in "From" header
- make sure correct domain name is used on signaling group's near end and far end network regions' "Authoritative Domain" field.
- make sure "Proxy Sel Rte Pat” field on the “locations" form points to the correct trunk group

When CM cannot match the domain name seen on the inbound SIP message in “From” header with the domain name present on network region “Authoritative Domain” field, CM routes the calls right away to the trunk group specified in the “Proxy Sel Rte Pat” field on the “locations” form. Make sure this route pattern points to the correct trunk group. Eg: pointing this to a PRI trunk group makes no sense as the idea is if CM does not own the domain (ie. no match) then let’s pass it back to Session Manager (SM) and SM should take care of the correct routing. Thus pointing this route pattern to a PRI trunk has no use at all.

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy