Solved: Re: Cisco 8865 with RingCentral

ronz · ‎05-31-2022

Good afternoon,

I purchased a Cisco 8865 phone from ebay and was initially told that I'm able to use it with Ring Central. I received the phone a few days ago. I spoke to Ring Central and have been unsuccessful in getting it setup

I called Cisco tech support and they're telling me the phone is out of warranty, thus I can't speak to anyone with any sort of technical knowledge. I find it odd that I can't speak to anyone about a product THEY make and is currently still in production.

Regardless, since this is a business line, I've been doing my own research on what needs to be done so I can get my business phone back up.

Here's where I'm at:

* I discovered there are two types of 8655 phones. One with enterprise firmware and one with 3PCC. I have enterprise. If done all over, it sounds like I should have went with 3PCC. This was something that was never brought to my attention. I was just told the 8655 will work. However, it also sounds like this may not be a show stopper since the firmware can be changed through cloud migration.

* I successfully assigned the phone an ipaddress IPV4, connected via ethernet. Pinging phone ip address works.

* I've been unable to access the phone interface through web. The documentation says enter http://<ipaddress>/admin. I tried that, "https://", without admin, with "admin/admin" as recommended elsewhere, but still no luck. Ring Central was unable to connect also. We turned off Windows firewall and the Asus router firewall, but still no luck. Somewhere on this forum made me believe that there may not be a web interface for the enterprise version? Is this correct?

* I successfully updated to the latest SIP firmware via TFTP, specifically "sip8845_65.14-1-1-0001-125". Still can't access phone interface through web.

* I called Cisco licensing with questions on what I need to do to update my firmware and what the cost would be, but I feel like I'm constantly speaking to a pole and never received any answers to my questions because the phone is out of warranty. I'm willing to purchase a license if it helps, but I can't get any clear or professional guidance on what I need to do.

*Further researching, I found I can use a config script file to setup Ring Centrals information via TFTP. This route looks complicated, but I'm willing to try if I can't receive any info for above bullet.

Any additional trouble shooting ideas/suggestions or links that may help me get the phone working with Ring Central?

Leo Laohoo · ‎06-05-2022

@ronz wrote:

Any recommendation on which Yealink?

It is all up to personal preference. T5x are Android-based.

I have a heard a lot of voice service providers prefer Yealink because they are painless to integrate (individually or by bulk). Make sure to get ones with warranty in them.

Before setting a choice, make sure to run this past RC support.

View solution in original post

Jaime Valencia · ‎05-31-2022

/admin is for 3PCC, the FW version you mention is enterprise, so no /admin, if the web server is enabled, it's just the IP of the phone, but you won't find any configuration settings, it's a page to view what setting the phone has from CUCM. Enterprise FW has no configuration page on the phone, all the settings come from CUCM, so no need for it.

You do need to buy a license to migrate between 3PCC/MPP to enterprise (and viceversa)

Go to upgrade.cisco.com and you'll find documentation that explains how the process works, and what PN you would need to buy for this.

HTH

java

if this helps, please rate

ronz · ‎05-31-2022

Thanks for the response, Jaime.

I went to the link you provided, but...

I'm not able to get very far because I don't have a PAK#. How do I get one of these if this is a phone I purchased from ebay?

Leo Laohoo · ‎05-31-2022

Novice user can easily make the mistake of purchasing a Cisco-branded phone with Enterprise image because they are cheaper than the ones with 3PCC/MPP image.

There are four choices so choose wisely:

Pay "mo money" to convert the phone from Enterprise image to 3PCC/MPP image.
Return the phone to the vendor and ask them, politely, if they can send a phone with 3PCC/MPP image.
Continue to "provision" or configure the phone to register with the VSP with Enterprise image.
Get a different brand.

Let me go through them with an explanation.

OPTION 1:

The license to convert the phone is "L-CP-E2M-88XX-CNV" and the "place" to convert the phone is Cisco Cloud Upgrader. Converting the from one image to another is meant to be "straightforward" and results are a mixed bag: Sometimes it works flawless and sometimes people just want to cry themselves to sleep.

OPTION 2:

Exercise this option only when Option 1 fails but this is, by far, the easiest of the lot.

OPTION 4:

Depends on how technical the person is. If the person is not technical and cannot find anyone who is, this option is "it".

And then there is Option 3:

It is widely-known officially, that Cisco Enterprise-image can only be used to register a phone to a Cisco-branded UCM. (People want to be seen using "Cisco" branded phone as a sign of "prestige" and this is why Cisco has come up with the 3PCC/MPP firmware.) Unofficially, there is a growing number of people who have been able to successfully integrate Cisco-branded phones (68XX, 69XX, 79XX, 88XX and 99XX) to non-Cisco branded UCM like 3CX and Asterisk based. It can be done but it will take some "effort" (and maybe some hairs or some choice "swear words") involved. It can be done. Proof? I have two 9971 (including cameras), 7945 and 7970 registered to an Asterisk server hosted by a Raspberry Pi.

NOTE: I picked Cisco for my home phone because I know just how difficult it is to integrate. If I put this into my CV and someone "in the know" reads it ...

For Option 3, prepare the following:

A known working SEPmacaddress.cnf.xml configuration file
Enterprise image firmware of the phone (ZIP extension)
Dialing plan file
TFTP server to put all the files (1, 2 & 3) in.
DHCP Option 150
Disable NAT
Disable SIP ALG

ronz · ‎05-31-2022

Thanks a bunch, Leo! You give me a glimmer of hope!

My gut feel tells me to start figuring out this SEP file as my phone dealings with cisco have been pretty lame. I'm supposed to get a phone call tomorrow so maybe things will change.

RE: the SEPmacaddress.cnf.xml file you sent

I noticed the file name has "9970" in it and also noticed you mentioned you have two 9971 phones. Is this config file only for use with the 99xx series phones, or is the config file structure the same for both 99xx and 88xx phones? I understand I will need to figure it out and insert Ring Centrals information, but do you know if the file, the way it's currently structured, will load into a 88xx (8865) phone as well?

Leo Laohoo · ‎05-31-2022

The SEPmacaddress.cnf.xml is a configuration based on XML tags. This same "template" which will work with phones that uses XML tags, like 79x1 to 79x5, 7970, 7975, 78xx, 88xx.

Make sure to leave tags with USECALLMANAGER alone. Fill in the other lines.

ronz · ‎05-31-2022

Leo, again, MUCH appreciated.

Ok, I think I have my preliminary SEP file ready. I'm going to give it another look tomorrow before I try to run it. I also want to see what Cisco licensing says about the cloud upgrader.

Meanwhile, I did have some additional questions:

1) Default UN/PW. Documentation specifies "No default passwords are assigned
to either the administrator or the user account." Being that I did a factory reset when I first got the phone, is the UN: admin, PW: <blank>?

2) I saw the <tzdata> ..... </tzdata> tag near the beginning of the file. Do I need this if I'm running Windows 10? Or is this only for Linux OSs? I deleted it, but can put it back.

3) For <startMediaPort> and <stopMediaPort> ... it's not clear to me what this is. Do I leave this alone, or is it something I'd need to get from my VOIP provider (e.g., Ring Central)?

4) Where do I get the "dialing plan" file.

5) Additionally, I saw another file "softKey9971.xml" for SoftKeys. What is this, where can I get it, and can I use this for the 8865? Or is it OK if I just "blank" it off?

6) My understanding is I don't need a FeaturePolicyFile (DefaultXP.xml) per "The 8961, 9951 and 9971 models use the Feature Policy" I'm assuming it's OK to just blank this off being as I have the 8865. Is this safe?

Again, You've been the biggest help (BY FAR!!). Thanks again!

Leo Laohoo · ‎05-31-2022

@ronz wrote:

1) Default UN/PW. Documentation specifies "No default passwords are assigned
to either the administrator or the user account." Being that I did a factory reset when I first got the phone, is the UN: admin, PW: <blank>?

For Enterprise image, web access do not require any username/password because it is only "read-only".

@ronz wrote:

2) I saw the <tzdata> ..... </tzdata> tag near the beginning of the file. Do I need this if I'm running Windows 10? Or is this only for Linux OSs? I deleted it, but can put it back.

No operationally important and can be ignored/removed from the config file.

@ronz wrote:

3) For <startMediaPort> and <stopMediaPort> ... it's not clear to me what this is. Do I leave this alone, or is it something I'd need to get from my VOIP provider (e.g., Ring Central)?

3) Additionally, I saw another file "softKey9971.xml" for SoftKeys. What is this, where can I get it, and can I use this for the 8865? Or is it OK if I just "blank" it off?

4) My understanding is I don't need a FeaturePolicyFile (DefaultXP.xml) per "The 8961, 9951 and 9971 models use the Feature Policy" I'm assuming it's OK to just blank this off being as I have the 8865. Is this safe?

Leave that alone.

@ronz wrote:

4) Where do I get the "dialing plan" file.

Create a text file. Start with the following:

<DIALTEMPLATE>
 <TEMPLATE MATCH="*" TIMEOUT="5"/> <!-- Dial any number. Wait 5 seconds, then dial -->
</DIALTEMPLATE>

Make sure this file is in the same TFTP folder as the rest. Filename is very case sensitive.

ronz · ‎06-02-2022

Great!

I have yet to hear from Cisco on what it'll cost to use the "cloud upgrader." This is the 2nd time I've been told I'd receive a call in 24 hours and did not. It appears that Option 1 may actually not be an option. I'll try giving them a call again, but right now I'm not all that confident in their phone service process. Option 3 may be the only option I have, so I'm glad I already started looking into it.

Create a text file. Start with the following:

<DIALTEMPLATE>
 <TEMPLATE MATCH="*" TIMEOUT="5"/> <!-- Dial any number. Wait 5 seconds, then dial -->
</DIALTEMPLATE>

Make sure this file is in the same TFTP folder as the rest. Filename is very case sensitive.

In the above you mentioned "Start with the following". That phrase makes me believe there should be more... can you please clarify.

Leo Laohoo · ‎06-02-2022

@ronz wrote:

In the above you mentioned "Start with the following". That phrase makes me believe there should be more... can you please clarify.

Different countries have different dialling "patterns", i. e. How many digits, what numbers are allowed, etc.

Start with the one I have provided. Once the phone works, and making/taking calls work, we can improve the dialling pattern file to suit.

ronz · ‎06-02-2022

I decided to be brave and ran the file. Here's where it ended up:

From Networking Status Messages

* No trust list installed

* SEP*MAC#*.cnf.xml (TFTP) - looks like this transferred OK

* VPN not configured

* oAuth mode disabled

* Error updating user locale

* Error updating network locale

* TFTP error AppDialsRules.xml

* TFTP timeout softkeys.xml

* Error Verifying Config Info - not sure why it's doing this.

From the main phone screen:

* It hangs at "Phone is registering"

I guess this is where the true fun begins....

Leo Laohoo · ‎06-02-2022

@ronz wrote:

* Error Verifying Config Info - not sure why it's doing this.

Means the SEPmacaddress.cnf.xml file got rejected by the phone.

Please attach the file so we can have a look.
NOTE: Remove username & passwords.

ronz · ‎06-03-2022

Greetings, When I get back on the computer. I'll upload it.

I was doing some reading on RingCentral and came across this stuff: Do you think this has something to do why it's hanging on registering? I was reading in the cisco manual, by default it's set to use UDP.

I'm also wondering if I need to create a ITLFile.tlv file and do something with that as hinted below.

From: Secure Voice Transport for 3rd Party Deskphones (ringcentral.com)

Requirements:

1. Devices must support TLS 1.2 (TLS 1.0 and TLS 1.1 devices will not be supported)
2. Devices must support Secure Real-Time Transport Protocol (SRTP) Offer and Answer in the Session Description Protocol (SDP)

- Set the device’s Transport Protocol to use TLS.
- Enable the device’s SRTP (Secure Real-Time Transport Protocol) Offer and Answer.

Troubleshooting:

1. If the device is unable to register using TLS, then on some devices you may need to upload a certificate chain to the device. This is only required if your device needs to validate the certificate. After loading the certificate chain then reboot the device.

Intermediate Certificate: https://www.websecurity.symantec.com/content/dam/websitesecurity/support/digicert/thawte/ica/Thawte_EV_RSA_CA_2018.pem

Root Certificate: https://www.websecurity.symantec.com/content/dam/websitesecurity/support/digicert/thawte/root/DigiCertHighAssuranceEVRootCA.pem

From another website:

Enable SIP-TLS mode by setting transportLayerProtocol to 3 and setting deviceSecurityMode to either 2 (Authenticated) or 3 (Encrypted) in SEPMAC.cnf.xml.

ronz · ‎06-03-2022

Leo: my SepMAC.cnf.xml as you requested. I was turning on/off some of the tags to see if it would register (I was comparing it to another SepMAC file I saw online).

Leo Laohoo · ‎06-03-2022

@ronz wrote:

<transportLayerProtocol>3</transportLayerProtocol>

Let us keep it simple first: Use either 1 or 2.

Next, TMI (too much info). The SEPmacaddress.cnf.xml file has too much info, i. e. too many XML tags that are "commented out". For the time being, remove them from the file to make the config look better. We're trying to find out which one of these tags is giving the phone a hard time.

Remember, the first order of business is to get the phone working. All the decorations and icings around it will be a "later" job.

@ronz wrote:

<dialTemplate>dialplan.xml</dialTemplate>

Make sure the dialing pattern file has the same filename as this. Remember, it is very case-sensitive.

@ronz wrote:

<loadInformation>sip8845_65.14-1-1-0001-125</loadInformation>

Be prepared to downgrade the firmware to something like 11.X or 12.X.