Solved Cannot page extension

[MannyL]

I have one extension using a Yealink T46G that I cannot seem to Page. The receiving phone drops/ends the call immediately after the page call hits it. I checked all the rights of that extension and reset/re-provisioned/factory wiped phone.

 

[YiannisH_3CX]

Hello @MannyL

Is the phone provisioned as local or remote? If remote, is it provisioned as STUN or through an SBC? Are you using the default 3CX template and the supported firmware?
What PBX version are you running? You can see the exact build number on the Dashboard under the Information column. Is the issue only with this device?

 

[MannyL]

I'm running the latest build V15.5 SP5. Extension is local using latest supported firmware and default 3CX template. I have 75+ phones but this is the only one exhibiting this behavior.

 

[YiannisH_3CX]

Can you exchange the device with another one to see if the issue stills persists? You can also assign the phone to a different extension and try to replicate the issue.

 

[MannyL]

I provisioned/swapped two extensions onto each others phone and Paging now works for both... not sure what went wrong and not sure how my actions fixed it, but thanks!

 

[YiannisH_3CX]

Glad to see the issue has been resolved.

 

[MannyL]

Hi, It looks like the problem returned to that particular extension, cause unknown. Paging worked for a few days and then stopped. No changes were made in the interim

 

[YiannisH_3CX]

At this point i would recommend using wireshark to determine why paging does not work in the particular extension. You should capture from the PBX and the web interface of the phone and compare the results. Either the paging does not reach the phone or it is being rejected for some reason.

 

[YiannisH_3CX]

@MannyL

Please be very careful when posting wireshark captures in public forums as they contain a lot of sensitive info.
From what i could see however there are 2 devices on the same extension and the second device answers the call before the Yealink. Please note that only once one device answers the other device will receive a cancel message. The device that answers has an IP ending in .170

 

[MannyL]

User had softphone running in softphone mode, not CTI. Was causing the entire issue...

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.