Solved Cisco 303 Registered But DECLINE when making calls (Why?)

[thereverend]

I have a cisco SPA303 phone that I have registered with 3cx both lines GREEN and show up as registered in the 3CX extension list. However when I go to make a call the phone gets a FAST busy and says DECLINE. I ran wireshark and it is saying SIP STATUS 603 DECLINE . This is most likely some kind of easy fix but. I cant seem to locate that setting that is causing this. Thanks in advance for any help.

 

[apostolis_3CX]

Hi thereverend

603 Decline
The destination does not wish to participate in the call, or cannot do so, and additionally the destination knows there are no alternative destinations (such as a voicemail server) willing to accept the call.
From your capture, who is sending the 603 message? The PBX or your provider?

 

[thereverend]

The 3CX PBX is sending the 603 message. Do not get as far as the trunk

 

[apostolis_3CX]

Is the phone local to the PBX or remote.
Also what is the current firmware installed on the phone.
Can you communicate with other extensions succesfully?

 

[thereverend]

Remote extension. Firmware 7.6.1
I can not communicate with any other extensions

I can call to the cisco phone BUT can not call out

 

[apostolis_3CX]

Note that these phones can not be used from a remote location or in combination with a 3CX in the cloud as stated here: https://www.3cx.com/Sip-Phones/Cisco-SPA/

What you can do is try to manual configure the phone from the phone's UI (not supported from 3CX).

 

[thereverend]

I did configure this phone thru the UI. Any idea on a setting I might want to check. Also wondering why all of a sudden 3cx stopped supporting these phones?

 

[NickD_3CX]

Under Settings --> Network --> FQDN, check what the Local SIP Domain is, then in the interface of the phone, make sure the Registrar is exactly the same. It could be that the PBX is rejecting due to wrong SIP Domain. Also of course check that the Public IP of that location has not been blacklisted.

To clarify, they are no longer supported as remote extensions. The reason is they don't support HTTPS provisioning.

 

[thereverend]

Thank you. This did the trick. Just for everyones sanity you might consider putting under your provisioning tab this trick. This drove me nuts for DAYS!!.. Thank you again..