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>Search

Reminder

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

upgrade
Knowledge Base

CFU service doesn't work on AR1220

Publication Date:  2015-06-28  |   Views:  178  |   Downloads:  0  |   Author:  SU1001299054  |   Document ID:  EKB1000080550

Contents

Issue Description

AR1200 device connected with Carrier with PRA trunk, and there are some extension(Huawei eSpace 7900 IP Phone) registered to AR1200. when the PRA incoming call go to extension 8888(one IP Phone, and this IP Phone have set CFU service to another mobile phone number), then this call fail.

here is topology about this issue. the fail scenario like this:

A make a call to extension 8888, and 8888 have enabled CFU to B, but B don't ring normally.


Alarm Information

CFU service fail. the caller mobile phone get a response "the called number is not accessable"

Handling Process

1, chece the extension number have the right or not.

[R8-AR1220-voice]display voice pbxuser 1202 service-right 
  Abbreviated dialing                               : Enable
  Call barring                                      : Enable
  Call forwarding busy                              : Enable
  Call forwarding condition                         : Enable
  Call forwarding no reply                          : Enable
  Call forwarding offline                           : Enable
  Call forwarding unconditional                     : Enable

2.check the CFU service prefix.

[R8-AR1220-voice]display voice callprefix *21*
[R8-AR1220-voice]display voice callprefix *22*

 3. double-check with our customer about service using procedure, and make sure custoemr use it normally and the service is enabled in the AR side after we check the confiuration again.

4.suggest our customer to reproduce the issue, and feedback the log and configuration.

Root Cause

 after check the feedback log, we found the configuration missing.

customer have three dn-set

enterprise default
  crbt enable
  crbt-file flash:/ringbacktone.wav status pass
  dn-set pbx
  dn-set indigo
  dn-set oneill

and the incoming call come with this trunk-group, and this mean this incoming call with dn-set pbx.

trunk-group oneill dss1-user
  enterprise default dn-set pbx
  callroute 0
  trunk-pra 2/0/0

but there aren't prefix match with this dn-set.

callprefix 0
  enterprise default dn-set oneill
  prefix 0
  call-type category basic-service attribute 1
  digit-length 1 32
  callroute 0                            
#
callprefix 00
  enterprise default dn-set indigo
  prefix 0
  call-type category basic-service attribute 1
  digit-length 1 32
  callroute 0

Solution

we add one new callprefix for dn-set pbx.

 #

callprefix 000              //添加dn-setpbx的出局字冠

  enterprise default dn-set pbx          

  prefix 0

  call-type category basic-service attribute 1

  digit-length 1 32

  callroute 0

#

afterroute-change 000                   

  callprefix 000

  trunk-group oneill

  caller del-then-Insert 1 32 31568888

  called del 1 3

#

Suggestions

NULL