CyberData Zone Controller login issues after provisioning

[adamp]

Hi,
So we recently sold a SIP Paging zone controller to a customer we have. This is our first time selling this product, so I set it up in our office (as we also use 3CX) to confirm it would work the way we had hoped before bringing it to the customer. It worked fine here, however after provisioning the Cyberdata zone controller into the customer 3cx software, we lost our ability to log in. The "phone web page password" in the 3CX admin webpage does not work for the zone controller, nor does the default credentials. When I did this myself, the web page password (from what I remember, there was a time lapse between my testing and customer installation) allowed me to log into the pager after provisioning. Is there any explanation for this?

 

[craigreilly]

Is this setup as an extension?
Under the extension, under phone provisioning - "Phone Web Page Password"

Thats the only thing I know that would change a device password.

 

[adamp]

It has an assigned extension. I should note we’ve actually witnessed other issues with the zone controller as well. For example, I tested it off a Cisco IP phone SPA514 G and I noticed it was double dialing certain digits when prompted for a zone number. Namely 0 and 1, so the only zones you could dial when prompted were 00 and 11. Tried it on multiple of that same model, with current firmware and they all had the same result. There may be other issues our customer has experienced as well, but we can’t confirm that yet. In regards to the phone webpage password, that’s actually how it worked in our corporate office. I had our client on the other end copy and paste that password directly into the web page from 3CX in the event he was dictating it wrong, it didn’t seem to work. Is it possible the username was modified as well on the webpage? I don’t remember that happening on our end, however at this point I believe we’ve tried the extension as a username as well, which was the only other possible change I thought may have prevented correct authentication.