SIP phone users will not go to coverage path where h323 phones will. (With the same assigned coverage path)

Doc ID    SOLN230931
Version:    2.0
Status:    Published
Published date:    21 Mar 2017
Created Date:    14 Jun 2013
Author:   
Max Barker
 

Details

Aura 6.2 FP2 - SIP phones will not go to cover path where h323 phones will with the same cover path assigned.

Issue is simple, any call to a SIP station will not go to the assigned coverage point on all criteria in cover path. Even 'send-calls' activated will not cover. H323 stations assigned to the same cover path work ok.

=============================================================================================
This is where the SIP phones do not cover.....
=============================================================================================


11:28:55 TRACE STARTED 06/14/2013 CM Release String cold-03.0.124.0-20553
11:28:56 active station 50000 cid 0x126
11:28:56 G711A ss:off ps:20
rgn:1 [X.X.X.X]:2858
rgn:1 [X.X.X.X]:2056
11:28:59 dial 57940 route:UDP|AAR
11:28:59 term trunk-group 20 cid 0x126
11:28:59 dial 57940 route:UDP|AAR
11:28:59 route-pattern 20 preference 1 location 1/ALL cid 0x126
11:28:59 seize trunk-group 20 member 3 cid 0x126
11:28:59 Calling Number & Name NO-CPNumber NO-CPName
11:28:59 SIP>INVITE sip:[email protected] SIP/2.0
11:28:59 Call-ID: 80c8d15afe0e21dce151a6ff8600
11:28:59 Setup digits 57940
11:28:59 Calling Number & Name 50000 H323 Hardphon

From calltrace:
SUSER PRI_BUSER<0005000f> UM_TERM(cid=00120308 orig=STA_USER<0000a027> rres=R_PTTERM)

--------------------------------------------------------------------------------------------------------------------------------------------------

 

After the CM config change...

============================================================================================
This is where the SIP phones do cover....
============================================================================================
list trace station 50000 Page 1

LIST TRACE

time data

11:53:34 TRACE STARTED 06/14/2013 CM Release String cold-03.0.124.0-20553
11:53:35 active station 50000 cid 0x139
11:53:35 G711A ss:off ps:20
rgn:1 [X.X.X.X]:2858
rgn:1 [X.X.X.X]:2052
11:53:37 dial 57940
11:53:37 term station 57940 cid 0x139
11:53:37 SIP>INVITE sip:[email protected] SIP/2.0
11:53:37 Call-ID: 8020b387b2e0e2195e251a6ff8600
 

From calltrace:
SUSER STA_USER<0000a025> UM_TERM(cid=00120145 orig=STA_USER<0000a024> rres=R_PTEERM)

Problem Clarification

Aura 6.2 FP2 - SIP phones will not go to cover path where h323 phones will with the same cover path assigned.

Cause

CM configuration.

Root cause:
Dialplan Parameters had UDP first (UDP = Uniform Dial Plan)
579xx had a match in UDP and went to AAR where it matched to SIP trunk to SM
In this scenario, CM considers this not to be a station call and does not cover it.

Clues in the traces:
In list trace we see 'dial 57940 route:UDP|AAR' showing the call went through UDP|AAR'
In the calltrace the UM_TERM is to the trunk (5000f), not the SIP station UID.
Meaning - CM thought this call was terminating to a trunk and would not cover.

Solution

Solution:

Change 'UDP first' to 'Local first' in Dialplan Params (of course uderstanding the impact)
or
Change the entry for the SIP stations in UDP so it goes to 'ext' where it matches then to the SIP station.
or
Remove the entry for SIP stations in UDP entirely.

After the change:
Notice now that in list trace the call terminates to a station and call trace UM_TERM is the SIP stations UID. Therefore, the call covers.


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