Re: IP Phone 8851 compatible PBX

kaiser-css · ‎09-18-2018

Hi!

We have 2x IP Phone 8851 and we already tried to use them with a AVM Fritzbox with SIP Firmware installed on the phones. After hours of trying and searching community sites we've given up the work. Now we just want a PBX that is enough for making calls with these phones.

Any suggestions?

kaiser-css

Dan Lukes · ‎09-18-2018

What flavor of CP 8851 you have ? Whats exact Product ID printed on sticker on bottom of phone ? What you mean "SIP Firmware installed" ? E.g. what's exact version of firmware you installed (is it 3PCC kind of firmware) ?

kaiser-css · ‎09-20-2018

Thank you for responding.

I dont't find the Product ID but there is a sticker with PID VID: CP-8851-K9 V09 maybe this is it?

I've downloaded and installed ths Firmware via TFTP Server: 8811, 8841, 8851, 8851NR and 8861 SIP IP Phone firmware files only - Compatible CUCM Versions: 9.1(2)+cmterm-88xx.12-1-1SR1-4.zip

I got it from that website: https://software.cisco.com/download/home/286255328/type/282074288/release/12.1%25281%2529

I've tried several things but nothing worked for me.

You can click the following link to a german community where I've posted the phone logs and the TFTP logs.

https://www.administrator.de/content/detail.php?id=385386#comment-1310400

Dan Lukes · ‎09-20-2018

CP-8851-K9 V09 is "enterprise" kind of phone shipped (while CP-8851-3PCC-K9 is for third party call control system).

Even enterprise phone can be used with 3rd party call control systems like FritzBox, but I have no personal experience with it. @Leo Laohoo is expert on the matter here.

Even as inexperienced user I can provide some hints. According the log you referred, you phone has requested registration:

REGISTER sip:192.168.1.254 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.205:5060;branch=z9hG4bK3ac84fc4
From: <sip:620@192.168.1.254>;tag=0027902bf2ac00076ea25342-410202ac
To: <sip:620@192.168.1.254>
Call-ID: 0027902b-f2ac0003-51e77633-6b5d9647@192.168.1.205
Max-Forwards: 70
Session-ID: c74c2a2d00105000a0000027902bf2ac;remote=00000000000000000000000000000000
Date: Fri, 07 Sep 2018 10:09:41 GMT
CSeq: 102 REGISTER
User-Agent: Cisco-CP8851/12.1.1
Contact: <sip:620@192.168.1.205:5060;transport=udp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-0027902bf2ac>";+u.sip!devicename.ccm.cisco.com="SEP0027902BF2AC";+u.sip!model.ccm.cisco.com="684"
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-7.0.0,X-cisco-xsi-8.5.1
Content-Length: 0

and FritzBox has responded it with

SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.1.205:5060;branch=z9hG4bK3ac84fc4
From: <sip:620@192.168.1.254>;tag=0027902bf2ac00076ea25342-410202ac
To: <sip:620@192.168.1.254>;tag=F6366331BDF35AFB
Call-ID: 0027902b-f2ac0003-51e77633-6b5d9647@192.168.1.205
CSeq: 102 REGISTER
User-Agent: FRITZ!OS
Content-Length: 0

FritzBox seems not to recognize 620@192.168.1.254 as identifier of device eligible to register. But only you (and administrator of the FritzBox in question) knows the correct identifier.

Leo Laohoo · ‎09-20-2018

The phone doesn't have a valid SEPmacaddress.xml.cnf file.

kaiser-css · ‎09-21-2018

Can you tell me what exactly is wrong with the SEPmacaddress.xml.cnf file?

Leo Laohoo · ‎09-21-2018

@kaiser-css wrote:

Can you tell me what exactly is wrong with the SEPmacaddress.xml.cnf file?

You may not have one. That's what is wrong.

Kindly read my first response.

kaiser-css · ‎09-21-2018

I have a SEPmacaddress.xml.cnf file. But something is wrong with it. I just want to know what could be wrong.

I posted the file in the german community that I linked before.

Leo Laohoo · ‎09-21-2018

@kaiser-css wrote:

I have a SEPmacaddress.xml.cnf file. But something is wrong with it. I just want to know what could be wrong.

I posted the file in the german community that I linked before.

Attach the SEPmacaddress.cnf.xml file here and we'll have a look.

In the meantime, check the following:

Does the service provider support ALG or not. If not, turn it off from the modem;
Does the service provider support NAT or not. If not, turn it off from the modem.

Dan Lukes · ‎09-21-2018

Just note - according the phone's REGISTER and FritzBox's response, both devices are connected in the same LAN. There seems to be no router/modem in-between.

kaiser-css · ‎09-25-2018

Here is my SEPmacaddress.cnf.xml file.

I had to change the ending to .txt to upload it.

Leo Laohoo · ‎09-25-2018

  <transportLayerProtocol>2</transportLayerProtocol>

I don't see anything wrong with the config other than the above tag missing.

Is the phone getting the correct IP address?

Is the phone able to download the configuration file?

If it phone was able to download the configuration file, what messages are appearing on the phone? Settings > Admin Settings > Status > Status Messages

Also check:

Does the service provider support ALG or not. If not, turn it off from the modem;
Does the service provider support NAT or not. If not, turn it off from the modem.

Dan Lukes · ‎09-25-2018

As I mentioned already, 8851 uses 620@192.168.1.254 in SIP REGISTER and it's rejected by FritzBox as unknown identifier. In my humble opinion, you need to discover what identifier will be accepted by FritzBox first, then you need to tweak SEPmac.cnf.xml so the required identification will be used for REGISTER. Or ...

... you can reconfigure FritzBox to accept current identifier (620@192.168.1.254) instead.

Sorry, I'm not familiar with FritzBox so I know neither how to configure it to accept particular identifier nor how to parse it's current configuration in attempt to discover correct identification.

kaiser-css · ‎09-21-2018

If 620@192.168.1.254 as identifier is wrong, what else should it be? Where can I find the correct identifier? Can I look it up in the FritzBox user interface? What should it look like?

Dan Lukes · ‎09-21-2018

If 620@192.168.1.254 as identifier is wrong, what else should it be?

Whatever the FritzBox will accept. So sorry, I'm not familiar with FritzBox and I know nothing about it's processing of peers REGISTER. Check FritzBox documentation or ask someone familiar with it.