Unsupported Help with Cisco CP-8941

[ottokoester]

Hi,

Anyone here has worked with CP-8941 as a SIP Phone ?

If yes, could share with me the settings XML-file because I've tried many possibilities and no one is working.

I've reached the server and also got the IP banned.

############################################################################################
E/SIP : sip_transport_init_ti_addrs : Admin has not configured a valid cucm for cucm index=VISITING_CCM=0.
E/SIP : sip_transport_init_ti_addrs : Admin has not configured a valid cucm for cucm index=SECONDARY_CCM=2.
E/SIP : sip_transport_init_ti_addrs : Admin has not configured a valid cucm for cucm index=TERTIARY_CCM=3.
E/SIP : sip_transport_init_ti_addrs : Admin has not configured a valid cucm for cucm index=SRST_CCM=4.
############################################################################################

 

[Alejandro_3CX]

Hi, these phones are not supported, you may find a list of supported IP phones in this link.

Please note that remote phones must be provisioned behind the 3cx sbc or router phones, learn more about it here.

 

[ottokoester]

Hi Alejandro,

Yes, I could see that all Cisco Phones are not supported by 3CX. "Legacy Phones (Manually configured, no support)"

Since this Phone is a SIP Phone, I was expectating to configure and get a connection.

Since 3CX System is based on SIP standard to allow calls via PSTN or via VoIP service, it has no mistery.

Basically, it should work, because it's a Cisco Phone with SIP Firmware, and like all Cisco CP Phone Series, after you change the Firmware they will work exactly as a Router Phone completely supported with Session Initiation Protocol... jus tneed to configure...

Well, I'm new here and I was thinking about the possibility that someone has used and made this before and could share the XML File with me.

As I can see... It's just getting wrong at the "Negotiation Phase"...

Here is the 3CX Log:

SIP request (REGISTER) from xxx.xxx.42.207 was rejected.
Reason: Block WAN requests is ON. .
Message:. REGISTER sip:xxx.xxx.xxx.155 SIP/2.0.
Via: SIP/2.0/TCP 192.168.xxx.xxx:44910;branch=z9hxxxx67xxxx22;received=xxx.xxx.42.207.
Max-Forwards: 70.
Contact: <sip:[email protected]:44910;user=phone;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-xxxxxxxxxxxx>";+u.sip!devicename.ccm.cisco.com="SEPxxxxxxxxxxxx";+u.sip!model.ccm.cisco.com="586";video.
To: <sip:[email protected]>. From: <sip:[email protected]>;tag=xxxxxxxxxxxx002312339192-6669b92b.
Call-ID: [email protected].
CSeq: 117 REGISTER.
Expires: 3600.
Content-Type: multipart/mixed; boundary=uniqueBoundary.
Date: Thu, 03 Jul 2025 12:22:10 GMT.
MIME-Version: 1.0. Proxy-Authorization: Digest username="xxxxxxxxxxxxxxxxxxxxxxxxx",realm="3CXPhoneSystem",uri="sip:xxx.xxx.xxx.155",response="xxxxxx1c88ea4c4f556ba8696d53b4af",nonce="xxxxxx590022cbc564:3a82627dfaacd85696028a32a7xxxxxx",algorithm=MD5.
Supported: replaces, join, sdp-anat, norefersub, resource-priority, extended-refer, X-cisco-callinfo, X-cisco-serviceuri, X-cisco-escapecodes, X-cisco-service-control, X-cisco-srtp-fallback, X-cisco-monrec, X-cisco-config, X-cisco-sis-6.0.2, X-cisco-xsi-8.5.1.
User-Agent: Cisco-CP8941/9.4.1.
Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEPxxxxxxxxxxxx ActiveLoad=SIP8941_8945.9-4-1-8 InactiveLoad=SCCP894x.9-4-1SR1-1 Last=initialized".
Content-Length: 1147. --uniqueBoundary.
Content-Type: application/x-cisco-remotecc-request+xml.
Content-Disposition: session;handling=optional. <?xml version="1.0" encoding="UTF-8"?> <x-cisco-remotecc-request> <bulkregisterreq> <contact all="true"> <register></register> </contact> </bulkregisterreq> </x-cisco-remotecc-request> . --uniqueBoundary.
Content-Type: application/x-cisco-remotecc-request+xml.
Content-Disposition: session;handling=optional. <?xml version="1.0" encoding="UTF-8"?> <x-cisco-remotecc-request> <optionsind> <combine max="6"> <remotecc> <status></status> </remotecc> <service-control></service-control> </combine> <dialog usage="hook status"> <unot></unot>  </dialog> <dialog usage="shared line"> <unot></unot>  </dialog> <presence usage="blf speed dial"> <unot></unot>  </presence> <joinreq></joinreq> <cfwdall-anyline></cfwdall-anyline> <coaching></coaching> <join-dxfer-policy>same-or-acrossline-enable</join-dxfer-policy> <oosalarm></oosalarm> <rpid-orig-called></rpid-orig-called> <gatewayrecording></gatewayrecording> <qos-tcl></qos-tcl> </optionsind> </x-cisco-remotecc-request> . --uniqueBoundary--

​

 

[leejor]

At the beginning of the log you posted it says block WAN request is on. That means in the extension settings you have not allowed a non-tunnel connection when outside the PBX. Check the settings and change that.

 

[Alejandro_3CX]

Hi Alejandro,

Yes, I could see that all Cisco Phones are not supported by 3CX. "Legacy Phones (Manually configured, no support)"

Since this Phone is a SIP Phone, I was expectating to configure and get a connection.

Since 3CX System is based on SIP standard to allow calls via PSTN or via VoIP service, it has no mistery.

Basically, it should work, because it's a Cisco Phone with SIP Firmware, and like all Cisco CP Phone Series, after you change the Firmware they will work exactly as a Router Phone completely supported with Session Initiation Protocol... jus tneed to configure...

Well, I'm new here and I was thinking about the possibility that someone has used and made this before and could share the XML File with me.

As I can see... It's just getting wrong at the "Negotiation Phase"...

Here is the 3CX Log:

SIP request (REGISTER) from xxx.xxx.42.207 was rejected.
Reason: Block WAN requests is ON. .
Message:. REGISTER sip:xxx.xxx.xxx.155 SIP/2.0.
Via: SIP/2.0/TCP 192.168.xxx.xxx:44910;branch=z9hxxxx67xxxx22;received=xxx.xxx.42.207.
Max-Forwards: 70.
Contact: <sip:[email protected]:44910;user=phone;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-xxxxxxxxxxxx>";+u.sip!devicename.ccm.cisco.com="SEPxxxxxxxxxxxx";+u.sip!model.ccm.cisco.com="586";video.
To: <sip:[email protected]>. From: <sip:[email protected]>;tag=xxxxxxxxxxxx002312339192-6669b92b.
Call-ID: [email protected].
CSeq: 117 REGISTER.
Expires: 3600.
Content-Type: multipart/mixed; boundary=uniqueBoundary.
Date: Thu, 03 Jul 2025 12:22:10 GMT.
MIME-Version: 1.0. Proxy-Authorization: Digest username="xxxxxxxxxxxxxxxxxxxxxxxxx",realm="3CXPhoneSystem",uri="sip:xxx.xxx.xxx.155",response="xxxxxx1c88ea4c4f556ba8696d53b4af",nonce="xxxxxx590022cbc564:3a82627dfaacd85696028a32a7xxxxxx",algorithm=MD5.
Supported: replaces, join, sdp-anat, norefersub, resource-priority, extended-refer, X-cisco-callinfo, X-cisco-serviceuri, X-cisco-escapecodes, X-cisco-service-control, X-cisco-srtp-fallback, X-cisco-monrec, X-cisco-config, X-cisco-sis-6.0.2, X-cisco-xsi-8.5.1.
User-Agent: Cisco-CP8941/9.4.1.
Reason: SIP;cause=200;text="cisco-alarm:25 Name=SEPxxxxxxxxxxxx ActiveLoad=SIP8941_8945.9-4-1-8 InactiveLoad=SCCP894x.9-4-1SR1-1 Last=initialized".
Content-Length: 1147. --uniqueBoundary.
Content-Type: application/x-cisco-remotecc-request+xml.
Content-Disposition: session;handling=optional. <?xml version="1.0" encoding="UTF-8"?> <x-cisco-remotecc-request> <bulkregisterreq> <contact all="true"> <register></register> </contact> </bulkregisterreq> </x-cisco-remotecc-request> . --uniqueBoundary.
Content-Type: application/x-cisco-remotecc-request+xml.
Content-Disposition: session;handling=optional. <?xml version="1.0" encoding="UTF-8"?> <x-cisco-remotecc-request> <optionsind> <combine max="6"> <remotecc> <status></status> </remotecc> <service-control></service-control> </combine> <dialog usage="hook status"> <unot></unot>  </dialog> <dialog usage="shared line"> <unot></unot>  </dialog> <presence usage="blf speed dial"> <unot></unot>  </presence> <joinreq></joinreq> <cfwdall-anyline></cfwdall-anyline> <coaching></coaching> <join-dxfer-policy>same-or-acrossline-enable</join-dxfer-policy> <oosalarm></oosalarm> <rpid-orig-called></rpid-orig-called> <gatewayrecording></gatewayrecording> <qos-tcl></qos-tcl> </optionsind> </x-cisco-remotecc-request> . --uniqueBoundary--

​

Stun is not supported, since you are using a SMB free, remote phones must be behind a 3cx sbc or router phone, this will help sending the traffic via the tunnel protocol, then you may manual configure the phone as described here.

 

[ottokoester]

At the beginning of the log you posted it says block WAN request is on. That means in the extension settings you have not allowed a non-tunnel connection when outside the PBX. Check the settings and change that.

Hi,

Yes, I was trying to find this option, I could read some questions and aswers about this, but I could not find this option at the extension setting, maybe it's because I'm SMB free and I've not configured an extra SBC for that.

 

[ottokoester]

Stun is not supported, since you are using a SMB free, remote phones must be behind a 3cx sbc or router phone, this will help sending the traffic via the tunnel protocol, then you may manual configure the phone as described here.

Ok, I've started to configure an extra SBC for that.

Why I can not use this other options?

* "Connect directly (IP Phone will be a router phone itself)"
* "Local LAN / VPN"

Because I'm free SMB ?

 

[Alejandro_3CX]

Why I can not use this other options?

* "Connect directly (IP Phone will be a router phone itself)"
* "Local LAN / VPN"

Because I'm free SMB ?

Because this is not a dedicated system, you are using a SMB free and all remote phones must be connected behind the 3cx sbc or router phone, if you want to use the phone as Local or via VPN then you need a dedicated pbx installed on premise or self hosted.