Recent content by Wanebo

You should give Graybar a call and see if they can get them or try Fluke directly. Here in the US I would probably shop for them at sandman.com first.

No. That card will need to be pulled in order to change the jumper.

https://gist.github.com/mutin-sa/eea1c396b1e610a2da1e5550d94b0453 That site has a list of the best ntp time servers available on the net. I suggest using a couple of the NIST ones for your primary and secondary ntp servers.

list usage extension xxxxxxxx

Iwatsu stopped selling communications products in North America back in 2015. ICON Voice Networks was supplying parts for years after that but I'm unsure if they could still source newly made replacement parts at this time. An aftermarket reseller may be your best bet for any parts needs you...

Have you tried restarting JBOSS?

Most carriers will not outpulse a number that you do not own and will instead strip what you send (if it's not yours) and stuff the header with the Bill To Number (BTN). Could be what's happening to you since you state "This is not in our DID range

In current versions of CM using ASA you can display and set the daylight-savings-rules display daylight-savings-rules change daylight-savings-rules Pretty sure these applied in your version also.

It's usually best to just reboot the servers so all the application services do a full clean restart. Start by rebooting the member of the HA pair that is in standby, after that comes back up and is functioning properly, interchange the pair so the one you just rebooted becomes active, then...

Typically a server will not use new certs until certain services are restarted. So, yes, it's true.

Do a list trace of a call and the CM will tell you why it handled the call the way it did.

Looks and acts (so far) exactly the same as ASA did. Just rebranded from the looks of it. But as long as it's a supported product it's worth moving to.

That is the same exact version and SP of ASA that we are using with CM 10.1.2 and we have no issues. Have you looked on the Avaya support site to see if what you are seeing on 10.1.3 is either expected behavior, or a reported issue? Also, what are the symptoms/errors you see when trying to connect?

At the bottom of the screen you can click on the tab for "Schedule" and watch your report run. You can also right click on a running report and select "Abort" and that will stop it from continuing to run.

Look in this old thread for some recommendations. https://www.tek-tips.com/viewthread.cfm?qid=1804454