CP-3905 not registering

Status
Not open for further replies.

rasimoes

New Member
Mar 10, 2018
15
0
1
44
Hello everyone,

I'm trying to get CP-3905 working the Freeswitch, but no success...I've just tried everything.

The problem is: when the phone tries to authenticate on FS, it sends only the extension name (avoiding the domain name)...this issue brakes the multi-tenancy "magic" on FS.

Any clues?

Thanks,
Rodrigo
 

rasimoes

New Member
Mar 10, 2018
15
0
1
44
Hi DigitalDaz, thanks for replying! :)

I'm attaching the config file... If you look on processNodeName field, I'm entering the full domain of FS. But on fs_cli, it shows that the phone tries to authenticate like extension@X.X.X.X.
 

Attachments

  • SEP.txt
    1.6 KB · Views: 10

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
Ah, just realised, Cisco, its possible you may just be out of luck.

These devices where never meant to work without call manager and some recent firmwares actually made them worse. There is maybe a field in another file, I cannot remember.

I myself have a nice 7965 or something similar, fancy touch screen and everything that I eventually came to the conclusion was never going to wor correctly.
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
Not saying you won't get it going, do you set the domain for callmanager anywhere else?
 

rasimoes

New Member
Mar 10, 2018
15
0
1
44
Yes, I've tried a lot of settings...but no success.
For now, I'm forgetting this model...I'll try sometime later, when I got some free time.

Thanks for helping me buddy! :)
 

bcmike

Active Member
Jun 7, 2018
326
54
28
53
Just taking a wild guess, but maybe throw the domain in this line:

<processNodeName>sip.xyz</processNodeName>
 

rasimoes

New Member
Mar 10, 2018
15
0
1
44
Just taking a wild guess, but maybe throw the domain in this line:

<processNodeName>sip.xyz</processNodeName>

That was the first thing I've tried... The problem is: the phone translate the "sip.xyz" to an IP, and tries to authenticate using the IP instead of domain name. Very frustrating :-/
 

bcmike

Active Member
Jun 7, 2018
326
54
28
53
This kind of a dumb work around, but depending on how many IP's you have to spare and how many domains you want to set up maybe just make the domain name an IP address. For example assign a bunch of IP aliases to the box, have sofia listen on them and then name your domains accordingly. Not sure that would even work and its pretty ugly but if you really want to use those phones it might be a way to do it.
 

rasimoes

New Member
Mar 10, 2018
15
0
1
44
This kind of a dumb work around, but depending on how many IP's you have to spare and how many domains you want to set up maybe just make the domain name an IP address. For example assign a bunch of IP aliases to the box, have sofia listen on them and then name your domains accordingly. Not sure that would even work and its pretty ugly but if you really want to use those phones it might be a way to do it.
Yes, sure! The only problem is that my service relies on AWS infrastructure, witch doesn't allow more than 1 public IP on each instance. But I'll consider creating a new infrastructure outside Amazon to solve this issue...I think it worth the try.
 
Status
Not open for further replies.