Callee showing as "ROUTER"

[GoldenYears]

Hello!

I am in the process of upgrading all our servers to v20. I have noticed the below on a few of them. Why would the callee say "ROUTER" when they name of the extension is right there and this was not a thing in v18? It's in a department. This is an internal call from one extension to another. What did I miss to configure after the upgrade, if anything/?

 

[edossantos_sipcaller]

The "ROUTER" is a new entity in 3CX v20, which routes calls according to the logic. Where are you calling from extension 000? For example, inbound calls are sent to this ROUTER, and then this entity forwards the call according to inbound rules.

 

[GoldenYears]

The "ROUTER" is a new entity in 3CX v20, which routes calls according to the logic. Where are you calling from extension 000? For example, inbound calls are sent to this ROUTER, and then this entity forwards the call according to inbound rules.

Remotely from a cell app to another cell app in the same server.

 

[edossantos_sipcaller]

Maybe the destination is not available (DND, not registered, etc.) then the call will be handled by the ROUTER to apply the forwarding rules.

 

[GoldenYears]

Maybe the destination is not available (DND, not registered, etc.) then the call will be handled by the ROUTER to apply the forwarding rules.

Naw. I have the extension provisioned to my cell and it rings when called as expected.

 

[Ecki]

Hi all,
we have noticed the same issue after upgrading to v20, this extends to the API function "ActiveCalls" as well.
In v18 (via the unofficial Web-Interface API solution) the ActiveCalls function reported this correctly.

With Queues, Ring Groups and the Digital Receptionist this problem does not occur.

Currently we have a workaround with Ring Groups in place, which solves this problem.
-> Create a Ring Group for every extension

Any chance that this is a Bug?