provisioning a Cisco CP8861

[jackf723]

Hello.
I have 3cx running on a Windows Server, and am currently attempting to provision a CP8861 3ppc. I do realize there are more commonly supported phones, but none of them to my knowledge have accessibility (the 8800 phones have a screen-reader for visually impaired folks built in, so they're the only option for hardware at this point).
I checked all the xml methods and all of them seem to be for dated firmwares. WHat manual provisioning method is currently recommended to get these phones working with 3cx?
And no, before anyone suggests the app, it is very much not accessible with Talkback on Android. Might create separate thread to discuss that in more depth in the integrations forum.
Thanks!

 

[JohnS_3CX]

Hello Jack,

That model is not supported and it is much newer than the ones we currently support so the existing provisioning will probably not work. Note that the ones we do support are used as "legacy" phones and this was meant to help people transition easier into 3CX back when those (now outdated) models were more popular, and with the outlook of replacing them with supported phones in the future when the time comes.

We highly recommend using supported 3CX phones from here: https://www.3cx.com/sip-phones/

If none of the phones from that list provide you with what you need Accessibility-wise, then it might be a good idea to get help from the manufacturer of your device of choice to assist you in setting it up with 3CX.

 

[jackf723]

Hello Jack,

That model is not supported and it is much newer than the ones we currently support so the existing provisioning will probably not work. Note that the ones we do support are used as "legacy" phones and this was meant to help people transition easier into 3CX back when those (now outdated) models were more popular, and with the outlook of replacing them with supported phones in the future when the time comes.

We highly recommend using supported 3CX phones from here: https://www.3cx.com/sip-phones/

If none of the phones from that list provide you with what you need Accessibility-wise, then it might be a good idea to get help from the manufacturer of your device of choice to assist you in setting it up with 3CX.

Hello John,
Thanks for that information. Since the 8800 multiplatform pones are newer than supported phones, would any manual sip configuration work, if it technically shouldn't take issue to supporting 3cx's existing protocols? What we're after is really nothing more than provisioning a few extensions that customers would get to via an ivr, so no conferencing or anything else. For that, would any unofficial direct sip configuration from modifying one of the 3cx templates do the job?
I'll have to see if any of the phones on that list of supported ones you mentioned have open source firmware, since those might be the best chance at getting more accessible phones out there. Since even though these are unsupported, Cisco is the one company that actively works on a text to speech interface for the 8800 line, and as you mentioned this is a much newer phone than the ones currently supported.
Thanks again!

 

[JohnS_3CX]

In this case you do not need to do anything with the templates, you can just enter the SIP credentials of your extension in the phone, and it should in theory register. Not guaranteed to work but you can try the following:

Username: your extension number
Auth ID: your extension Auth ID
Password: your extension password

 

[jackf723]

Ok, great. So direct sip configuration for 3cx would be able to be done direct through the 8861 configuration panel rather than having to go through the template. Since you mentioned the aim is to replace these older phones with newer supported ones, are the 88003ppc phones among those to officially consider, since they theoretically have everything in place to get along with 3cx already provided this works?
THanks again!

 

[JohnS_3CX]

Hi Jack,

There are no plans to support those phones for the time being. What I meant was that the goal would be to replace the aging Ciscos with something from our list of currently supported phones when the time comes.

 

[jackf723]

Line 000: not registered/registration failed. Does proxy/outbound proxy require ip addressort, or just the server ip? Sip port is set to 5060, protocol is UDP. Tried with both sip100REL enabled and disabled, no dice. Username is extension 000, password is the extension password, and the auth id is the extension's id. Is there something I'm missing?
Thanks!

 

[jackf723]

Hello.
Running into more auth problems. And this must be with the phone in question, though why this is I have no idea since the 8861 MPP phone as well as Microsip (which 3cx worked on) are both SIP-enabled phones. So, as stated, Microsip works without problem. But the cp8861 doesn't, and here are the settings we have, to connect to the 3cx vps with a public ip.
Nat enabled: no
SIP TOS/DiffServ Value:
0x68
RTP TOS/DiffServ Value:
0xb8

SIP Settings
SIP Transport:
UDP
SIP Port:
5060
SIP 100REL Enable:
Yes
EXT SIP Port:
0
Auth Resync-Reboot:
Yes
SIP Proxy-Require:

SIP Remote-Party-ID:
No
Referor Bye Delay:
4
Refer-To Target Contact:
No
Referee Bye Delay:
0
Refer Target Bye Delay:
0
Sticky 183:
No
Auth INVITE:
No
Ntfy Refer On 1xx-To-Inv:
Yes

Proxy and Registration
Proxy:
149.28.127.52
Outbound Proxy:
149.28.127.52
Alternate Proxy:
149.28.127.52
Alternate Outbound Proxy:
149.28.127.52
Use OB Proxy In Dialog:
Yes
Register:
Yes
Make Call Without Reg:
No
Register Expires:
3600
Ans Call Without Reg:
No
Use DNS SRV:
No
DNS SRV Auto Prefix:
Yes
Proxy Fallback Intvl:
3600
Proxy Redundancy Method:
Normal
Dual Registration:
No
Auto Register When Failover:
No
TLS Name Validate:
Yes

Subscriber Information
Display Name: extension 000's display name
User ID:
000
Password:
extension 000's password
Auth ID:
extension 000's auth id
Reversed Auth Realm:

SIP URi: None, should a sip uri be used for 3cx?


Also, Microsip asked for the username and domain in separate fields. For the cp8861, sould the username be [email protected] or just 000?
For the record, both phones are on the same network. The mentioned cp8861 works on a Callcentric line with similar settings apart from the sip details of course. What could be the problem we are facing?
Thanks!

 

[jackf723]

Since it isn't letting me edit the post, I should mention that the cp8861 is reporting "failed no response" in the registration status.

 

[cobaltit]

In this case you do not need to do anything with the templates, you can just enter the SIP credentials of your extension in the phone, and it should in theory register. Not guaranteed to work but you can try the following:

Username: your extension number
Auth ID: your extension Auth ID
Password: your extension password

You seem to have misread this post. Auth ID is not the extension number so it shouldn't be 000 unless you manually changed the auth ID in 3CX.

 

[jackf723]

cobaltit, I see where that could be confused. To clarify: In reality the actual auth id was used, I just replaced references to any login info in the configuration. But in the actual phone's configuration the auth id is the alphanumeric auth id that 3x provided. The cp8861 asks for a user ID, which is where I put 000. The password, which is where the sip password went, and then the auth id, in which I input the auth ID of the extension. Microsip configures based on that without problem, and I am able to dial internal extensions through it as well. The cp8861 still produces registration failed, with "failed no response" as the return. I doubt it's a problem with the phone not being able to connect to anything outside the network, because the phone had no problem taking my Callcentric extension and that line registered without conflict. If this is 3cx itself refusing the connection I don't exactly see how, as Microsip provisioned without a problem. Both the machine with Microsip and the cp8861 are on the same network while attempting to connect, by the way.

 

[cobaltit]

So some devices don't like alphanumeric ids so you can try changing the auth id in 3CX to match the extension and see if that works. I also would recommend turning the logs up to verbose and see if you actually see the device hitting 3CX. And at this point make sure your IP isn't blacklisted.

 

[jackf723]

I will definitely keep that in mind when creating/provisioning new extensions. IT looks like it doesn't mind the alphanumeric authi id. After a few hours the phone seems to have registered itself, so maybe the settings were/are prperly configured all along but the server must not have liked the connecting IP. IT wasn't in the blacklist since it hadn't yet been introduced to the phone, but nevertheless rebooting the server might accellerate the process in future. DTMF is also working now, as that had to be changed to inband+info on the 8861.
Thanks!