Unanswered extension forwards to another extension's mobile phone

[green5]

In a remote environment, registration of yealink phones via stun, when one particular extension remains unanswered in either a direct call or ring group, the call begins to ring the mobile phone of a different extension. This has continued even after the mobile phone has been removed from the extension. Any thoughts?

 

[Alphabetic]

What happens if you put in say your mobile number and apply to that ext and see if your phone rings instead?

 

[leejor]

when one particular extension remains unanswered in either a direct call or ring group, the call begins to ring the mobile phone of a different extension. This has continued even after the mobile phone has been removed from the extension. Any thoughts?

Are the Mobiles being called using the Ring my Mobile at the same time option, on these sets? Is this options used on multiple sets in the ring group? Does a call to the ring group always cause the same mobile number to ring, or different numbers?

 

[green5]

What happens if you put in say your mobile number and apply to that ext and see if your phone rings instead?

I already had a mobile associated with that extension.

 

[green5]

Are the Mobiles being called using the Ring my Mobile at the same time option, on these sets? Is this options used on multiple sets in the ring group? Does a call to the ring group always cause the same mobile number to ring, or different numbers?

leejor no, only 1 mobile number that had been associated with one of the extensions rings. It continued to ring even after I deleted that cell number from associated extension.

Example:
dial extension 103 (which had it's own mobile number)
103 doesn't answer
Mobile phone associated with extension 105 rings.

This continued even after I deleted the associated mobile number from 105.

I checked the phone and it has no forwarding set, and neither does the extension shows a forward to that mobile number.

Neither extension had forwarding rules set to their mobile's.

I isolated it that it was extension 103 because the forward to the 105's mobile stopped after I removed extension 103 from the ring group. (it will still ring 105's mobile if it is not unanswered in a direct call)

 

[leejor]

...so Ext 103 had forwarding to a mobile number?

Always check the 3CX Activity Log, for the routing of the call. That will show why a call goes where it does and will probably save yourself a lot of time in troubleshooting.

 

[green5]

The first time I checked the log, and I could find the call. My timing my have been off. Will be on site and see if restart cleared this issue. Thanks for all the suggestions.