snom 821 forbidden inbound calls

[paulg]

I have a snom 821 that cannot receive calls. When I dial the phone from any other phone, I receive a message stating "Call forbidden by administrator." I can however call out on the snom just fine. This is the only phone that seems to be exhibiting this behavior.
I have tried setting the phone up using manual configuration as here: http://www.3cx.com/sip-phones/snom.html
I have also tried setting up provisioning as here: http://www.3cx.com/sip-phones/Snom-provisioning.html
I have reset the phone to factory defaults.
The phone had firmware version 8.4.31. I have tried upgrading it to 8.4.32, but still no joy.

Looking at the server activity log shows the following:

13:15:13.520 [CM503008]: Call(55): Call is terminated
13:15:12.090 [CM504001]: Ext.8512: new contact is registered. Contact(s): [sip:[email protected]:5060/8512]
13:15:08.982 Session 3895 of leg C:55.1 is confirmed
13:15:08.581 [CM503007]: Call(55): Device joined: sip:[email protected]:40600;rinstance=21dd99820fea3b50
13:15:08.575 [CM503007]: Call(55): Device joined: sip:[email protected]:5062
13:15:08.573 [MS210005] C:55.1:Answer provided. Connection(proxy mode):192.168.2.1:7322(7323)
13:15:08.570 [MS210001] C:55.3:Answer received. RTP connection[unsecure]: 127.0.0.1:40720(40721)
13:15:08.568 Remote SDP is set for legC:55.3
13:15:08.565 [CM503002]: Call(55): Alerting sip:[email protected]:40600;rinstance=21dd99820fea3b50
13:15:08.423 [CM503025]: Call(55): Calling Unknown:Ext.EndCall@[Dev:sip:[email protected]:40600;rinstance=21dd99820fea3b50]
13:15:08.421 [MS210004] C:55.3:Offer provided. Connection(proxy mode): 127.0.0.1:7326(7327)
13:15:08.363 [CM503016]: Call(55): Attempt to reach <sip:[email protected]> failed. Reason: Forbidden
13:15:08.358 [CM503003]: Call(55): Call to sip:[email protected] has failed; Cause: 403 Use Proxy; from IP:192.168.2.107:3072
13:15:08.310 [CM503025]: Call(55): Calling Ext:Ext.1107@[Dev:sip:[email protected]:3072]
13:15:08.308 [MS210006] C:55.2:Offer provided. Connection(by pass mode): 192.168.2.108:11798(11799)
13:15:08.269 [CM503004]: Call(55): Route 1: Ext:Ext.1107@[Dev:sip:[email protected]:3072]
13:15:08.268 [CM503010]: Making route(s) to <sip:[email protected]>
13:15:08.268 [MS210000] C:55.1:Offer received. RTP connection: 192.168.2.108:11798(11799)
13:15:08.267 Remote SDP is set for legC:55.1
13:15:08.267 [CM505001]: Ext.1108: Device info: Device Identified: [Man: Yealink;Mod: T22;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T22P 7.60.0.100] PBX contact: [sip:[email protected]:5060]
13:15:08.258 [CM503001]: Call(55): Incoming call from Ext.1108 to <sip:[email protected]>
13:15:08.248 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.2.108:5062;branch=z9hG4bK216931468
Max-Forwards: 70
Contact: <sip:[email protected]:5062>
To: <sip:[email protected]>
From: "T22P"<sip:[email protected]>;tag=1250742924
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Proxy-Authorization: Digest username="1108",realm="3CXPhoneSystem",nonce="414d535c0468659b43:17dfb5f05c6a05e762a11384cb6ccfc5",uri="sip:[email protected]",response="8edaee0754a5e2c7295e62b20ff31499",algorithm=MD5
Supported: replaces
User-Agent: Yealink SIP-T22P 7.60.0.100
Allow-Events: talk, hold, conference, refer, check-sync
Content-Length: 0

I'm just not sure where else to go with this in order to get the phone to accept incoming calls.

 

[leejor]

Have you tried taking another set, and provisioning it with the same settings? If it fails then it is a "settings" issue. If it works then it is a "set" issue. The next step would be to provision the "bad" set as a different, working extension, if that fails then you have confirmed that the set is at fault.

You will then have to decide what to do with the phone. The manufacturer or their forum might be able to help troubleshoot.

 

[SY]

Snom phones may generate this answer in case if request is received from IP/port which is not equal to the value specified in option "SIP Proxy".
It doesn't happen if network topology is "plain"

Please provide more information about PBX host and network topology.

Thanks

 

[paulg]

Snom phones may generate this answer in case if request is received from IP/port which is not equal to the value specified in option "SIP Proxy".
It doesn't happen if network topology is "plain"

Please provide more information about PBX host and network topology.

Thanks

The 3CX server was just installed a couple of weeks ago on a Windows 2008 box. We are testing 3CX out right now. We have about 9 or 10 phones, some Yealink, some GrandStream, and this one snom. We also have some softphones on a couple of iphones and ipads. The server and all the phones are on a single class C network, 192.168.2.X. We have a DHCP server that has reservations for each of the phones. There isn't really anything special about the network layout.

For the most part, things are working as expected, with the exception of this one snom phone. We can call between the Yealinks, and also the GrandStreams, and Softphones. We are using VoicePulse right now as our outside VOIP provider, and there's no problem with dialing to the outside world, or receiving calls in.

The only issue seems to be in any of our phones calling this one snom. The snom can call any of the other phones, and can even call to the outside world just fine. If I unplug the phone (or reboot it), I can call the extension, and as expected, it just goes to voicemail. Once the phone is plugged back in, or up and running, calling that extension results in the "Forbidden" message.

 

[SY]

Please send this request to Snom technical support.
It is really weird behavior of the Snom phone.

 

[paulg]

I finally got it figured out. It was a few special settings on the snom interface.

http://wiki.snom.com/FAQ/After_an_update_to_firmware_version_4_or_above,_my_phone_isn%27t_registering_or_not_receiving_calls_anymore,_why_is_that

Line page SIP tab:

Long SIP-Contact (RFC3840) -> "off"
Support broken Registrar -> "on"

Advanced page (QOS/Security):

Filter Packets from Registrar -> "off"

Thanks to all who responded.