Missed call notification received on an extension not in the group call

[Pierre-Emmanuel DEGRYSE]

Hi,

I have set a group call with two extensions : 66 and 65. If no extension answers the call, it goes to the voice mail of 66. However, there is also missed call notification on extension 67 which doesn't belong to the group call. Why?

Best Regards,

 

[leejor]

Place a call that causes this, then check the 3CX Activity Log to see why extension 67 is involved.

 

[Pierre-Emmanuel DEGRYSE]

Please see attached the logs. I don't see anything relevant to extension 67.

 

[YiannisH_3CX]

Hello @Pierre-Emmanuel DEGRYSE

Are you using ext. 67 to forward the call to the group or is do you have a forwarding on one of the two extensions to ex. 67? Is ext 67 set as a mobile number for the one of the 2 extensions?

 

[Pierre-Emmanuel DEGRYSE]

We don't use ext 67 to forward the call to the group. There is DID allocated to this group. I don't see any forwarding rules from the extensions in the group towards ext 67 and it is not set as a mobile number for one of the 2 extensions

 

[leejor]

Are the sets local, or remote? If remote, do you use STUN?

 

[Jason Hille]

Check if the DID for the Hunt Group is not also listed on extension 67.

 

[Pierre-Emmanuel DEGRYSE]

Are the sets local, or remote? If remote, do you use STUN?

Hi. They are remotes and we do use STUN

 

[Pierre-Emmanuel DEGRYSE]

Check if the DID for the Hunt Group is not also listed on extension 67.

Not it is not. Ext 67 has another DID than the Hunt Group

 

[leejor]

Could extension 67 have the same local port as one of the other extensions in the ring group?

 

[Pierre-Emmanuel DEGRYSE]

Could extension 67 have the same local port as one of the other extensions in the ring group?

I guess it is possible. They are DECT phones connected to the same base station

 

[leejor]

What make/model are they?

 

[Pierre-Emmanuel DEGRYSE]

What make/model are they?

Yealink W56H

 

[leejor]

Have not used the Yealink, but have used the Panasonic and Gigaset DECT IP models. On those, more than one extension can be assigned per handset. You can then choose the default extension that is used for incoming and outgoing calls on each. I assign an extension that does have a mailbox (with mwi) assigned, to each handset, just so the message indicator will flash, even though calls do not route out on that extension.

If using Stun, all extensions provisioned on the base must be assigned a unique port number. If two extensions, on a base, were assigned the same port, then it is possible that the message waiting message is being sent to all extensions with the same port. Double check the message waiting options, on all extensions, as well.

 

[YiannisH_3CX]

Check if the handsets are correctly assigned to the Dect station as a miss-configuration could cause the issue you are describing. Each handset should be assigned to one sip account on the dect station
https://www.3cx.com/sip-phones/register-yealink-handsets/

 

[Pierre-Emmanuel DEGRYSE]

Check if the handsets are correctly assigned to the Dect station as a miss-configuration could cause the issue you are describing. Each handset should be assigned to one sip account on the dect station
https://www.3cx.com/sip-phones/register-yealink-handsets/

I have re-registered the handset but no change. Handset association looks good to me (see screenshot attached)

 

[Pierre-Emmanuel DEGRYSE]

Have not used the Yealink, but have used the Panasonic and Gigaset DECT IP models. On those, more than one extension can be assigned per handset. You can then choose the default extension that is used for incoming and outgoing calls on each. I assign an extension that does have a mailbox (with mwi) assigned, to each handset, just so the message indicator will flash, even though calls do not route out on that extension.

If using Stun, all extensions provisioned on the base must be assigned a unique port number. If two extensions, on a base, were assigned the same port, then it is possible that the message waiting message is being sent to all extensions with the same port. Double check the message waiting options, on all extensions, as well.

I have not set a port manually. I guess the base station should manage the port allocation automatically

 

[leejor]

I have not set a port manually. I guess the base station should manage the port allocation automatically

I wouldn't assume anything.