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

eSpace U1981 Cascading Call Forwarding Issue

Publication Date:  2018-02-02 Views:  37 Downloads:  1
Issue Description

Customer has configured in his unified gateway a Call Forwarding Cascade scenario where he informed us that when he is calling 2505 that has the following services activated: call forwarding to: no reply, on busy and offline instead of following the cascading scenario configured (2257-> 2336->2340->2445->2097); the call makes 2 or 3 jumps in the cascading call forward and does not work properly.

Handling Process

We have requested the following information from the customer:

 

-          Firmware version of the U1980 unified gateway

-          Configuration file from the U1981 and the data.bin file of PBX

-          If a BMU is also present in the network topology

 

After scheduling a remote session with the customer, we have checked the configuration for each of the involved extensions, re-created the scenario by dialing extensions involved in the cascading scenario individually to check if there is any pattern when calling from source 3023, collected the required logs, gathered the data.bin file in order to apply this configuration in the lab environment and reproduce.

 

We have found out that the customer has on the 5 users the global override forwarding service configured and advised customer of the service conflict list for the U1900 since the call forward is in conflict with the call forward override (global service)

 

In this scenario users A and B are available. User A enables the forwarding override permission. User B has registered the call forwarding service (unconditional, no response, busy, offline, conditional)

 

User A dials user B’s number. User B’s phone rings. User B’s forwarding service does not take effect.

Solution

The root cause of this issue is 2257 extension which has set the “call forward override” service. This function controls the next forward number and can’t proceed further with the forward of the next in line number in the cascading scenario.

 

Advised customer to proceed with the following procedure:

 

1.         Find the subscriber define the service

 

show subscriber filter newservicerights overcfx

 

1.         Delete the service .

 

config modify subscriber dn XX operatenewservice del newservicerights overcfx

END