No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

R2 trunk failed for incoming call

Publication Date:  2015-04-24 Views:  56 Downloads:  0
Issue Description

U1960 link to PSTN with 2 R2 trunk, and link to U1980 with SIP trunk, PSTN failed to dail in to U1980 huntgroup access number via U1960

Alarm Information

when dailed in, caller heared that hear the error message of that number does not exist  and hear the busy tone

Handling Process

1. We supect the huntgroup configuraiton issue,

Hunt Group

 GroupNo SubPBXNo GroupName NightServiceDn VUDn QueueTime Password RingType RedirectDn

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

31      0        ABAD                          59        ****     CIRCULAR            

TotalTimeLength RingInterval UmsNo NewMsg OldMsg

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

9999            20           255   0      0     

 

Manage

 

AllBusyManage AllOfflineManage AllQuitManage IfNoAnswerRedirect IfNeedPwdAuth

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

Queue then vu vu               vu            NO                 NO           

IfStaticGroup AutoConnect

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

YES           YES        

 Prefix

 

Prefix

------

61794 

 

HuntMember

 Member In Group

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

61749          

61750          

61751          

61752          

61753          

61754          

61755          

61756          

61757          

61758          

61759          

61760          

61761          

 ------- Matched record number : [13] -------

 ====  Command executed success !  ====

And we dialed from one extension to 61794. the huntgroup work properly, we aglied out huntgroup configuraiton issue

2. we check the U1960 number change rule, need change the callee number from 51320281 to 61794.

config add predeal index 5 changetype modify changepos 0 changelen 32 newdn 61794  ## mofidy the callee number to 61794

config modify prefix dn 51320281 callcategory basic callattribute localinter cldpredeal yes cldindex 5 officeselectcode 252 ## enable the number change rule for the prefix 51320281

After modified that, it's still failed for incoming call

3. Capture the R2 trunk trace, when dialed in, only one bit callee number received from R2 trunk. and we compare another trunk of R2, which can received full callee number, and always successful for incoming call.

Sucessful incoming call, which office no is 3:

[107][0x000025bf][2015-04-13 14:16:02.48][ccm.c 62498][dwCCMNo=  396] CCM_CallRestrict, caller numbers is:[5557351795]

[111][0x000025bf][2015-04-13 14:16:02.48][ccm.c 6741][dwCCMNo=  396] CCM_CallStartInfomationMsgProc: numbers is:[1050],1,1

[74][0x000025bf][2015-04-13 14:16:02.48][ccm.c 31690][dwCCMNo=  396] CCM_NumAnalysis

[125][0x000025bf][2015-04-13 14:16:02.48][ccm_patch_mexico300.c 574][dwCCMNo=  396] CCM_CalledDNAna: numbers is:[1050] subpbxno is: [0]

CCM_GetCallerOfficeInfo dwOfficeNo=3

Failed incoming call, callee number only one bit 0, and office no2


Root Cause

After compare the failed incoming call and sucessful incmoing call trace, we concluded that U1960 R2 trunk configuraiton is correct, PSTN side have the issue for callee number sending

Solution

PSTN side modied the configuraiton 

END