Recent content by capthoward

At some point in the past, someone had a CA generated from Let's Encrypt as well as DigiCert. Those certs are old but still valid. Could that be the issue?

Using ARS tables, you can create one that backs the other up. It's not quite automatic, but it's as automatic as it can be.

You can do this with system short codes and the ARS table at the site with no trunks. Adjust the ARS table to include the 8 in the telephone number and make the line 21. If your short code is 8N, then that's all you need. Nothing needs to be in the short codes of the line itself.

Earlier in the process of setting all this up, the equinox app was telling me there was a problem with the certificate. If I logged into the app using http instead of https I would get invalid domain or some variation of that message. Now that I have finally successfully(I think!) installed the...

Hello all! I have recently upgraded a system from R9.1 to R11 and have some issues getting Equinox to recognize the certificate. Formerly, OneX was installed but never used and so the system already had the FQDN ipo.companyname.com filled in on the System>VOIP tab. I had the IT folks set up an...

Waiting for line is not what the IP Office says when a number is misdialed. Waiting for line is always when there is no trunk available to establish a call. A misdialed call will show unobtainable, incompatible, or you'll hear a message from your carrier. Again, if the screen says...

Hey guys, I've got a situation where I have a SIP provider connected to LAN1 and a Multitech FF240-IP(SIP Line) connected to LAN 2. The call comes in and I see it ringing on the faxfinder, but it never connects. It would appear that the faxfinder and SIP line are all set up properly according to...

A lot of times, there's a compatibility document for the provider that details the IPO config. Which provider are you connecting with? I typically google that provider and IP Office and most times there's a document.

I have recently had issues where Manager on my laptop will no longer talk to a particular IP500V2. What I found was that I had to hold the reset button on the back of the V2 until the orange light starting flashing. Once the system came back up, I was able to talk to it again and load my config.

I replaced an older Definity last week that had door phones connected to trunk ports. Since these lines are now out of service until they see loop current I couldn't connect them to the new combo card trunk ports. The lines would never come in service. Seems like they'd make a provision for...

As it turns out, 8.0.18 has a bug. I applied 8.0.42 and all is well. Typical Avaya.

I tried that Peter...no good. I sent the monitor trace to the carrier and they compared it to yesterday's successful call trace. They say the PAI field is missing today. I looked at the Tech Bulletin 143 and it mentions a missing PAI that is fixed in 8.0.42. Could that be it?

In monitor its saying URI not recognized. Isn't that something in the SIP URI part of the SIP line programming? It is set to * for local URI, contact name, and display. PAI is use credentials user name, registration is set to 1:XXXXXXXXXX. The X's are the customer's phone number which is how the...

They say they don't ever see a call hit their switch.

When the system was on 7.0.27 everything was fine. Upgraded to 8.0.18 and now inbound is ok, but outbound is rejected. The trace says 403 Forbidden in SSA. Any ideas what may have changed between releases?