- Joined
- Dec 15, 2023
- Messages
- 26
- Reaction score
- 5
Hi everyone,
I have a snom m400 dect base that I want to add to a customers on prem v18.9 installation on windows server 2022. I have followed the manual under https://www.3cx.com/sip-phones/snom-dect-phones/ as best as I can. I am getting the following error right on the DECT Base:
Firewall check comes back positive.
Phone shows up in the old UI under Telephones as new, don't know if that's supposed to happen.
Any ideas what is causing the provisioning to fail?
I have a snom m400 dect base that I want to add to a customers on prem v18.9 installation on windows server 2022. I have followed the manual under https://www.3cx.com/sip-phones/snom-dect-phones/ as best as I can. I am getting the following error right on the DECT Base:
I have checked that I can download the config file under the config URL in the 3cx network as well as externally. Both works.Sent to udp:224.0.1.75:5060 at 04/06/2024 15:47:11 (723 bytes)
SUBSCRIBE sip:MAC%[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.20.120;branch=z9hG4bK53nchxumz4jeqyi2mg38hg4r
Max-Forwards: 70
From: <sip:[email protected]>;tag=2nr55x7j
To: <sip:MAC%[email protected]>
Call-ID: [email protected]
CSeq: 57322 SUBSCRIBE
Contact: <sip:[email protected]>
Allow: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, INFO, PRACK, UPDATE
Allow-Events: dialog,message-summary
Event: ua-profile;profile-type="device";vendor="snom";model="snomM400";version="06.10.0005"
Expires: 0
Supported: replaces,100rel
User-Agent: snomM400/06.10.0005 (MAC=000413D12956; SER= 00000; HW=3)
Content-Length: 0
Received from udp:192.168.20.139:5060 at 04/06/2024 15:47:11 (306 bytes)
SIP/2.0 500 Server Internal Error
Via: SIP/2.0/UDP 192.168.20.120;branch=z9hG4bK53nchxumz4jeqyi2mg38hg4r
To: <sip:MAC%[email protected]>;tag=88383c00
From: <sip:[email protected]>;tag=2nr55x7j
Call-ID: [email protected]
CSeq: 57322 SUBSCRIBE
Content-Length: 0
Firewall check comes back positive.
Phone shows up in the old UI under Telephones as new, don't know if that's supposed to happen.
Any ideas what is causing the provisioning to fail?