Search results for query: *

Don't know if I'm jinxing myself, but since after finally getting ALL the system up to R5 my connectivity problems seemed to have disappeared.

Thanks for the info. No firewall in place but question if having 2 of our main systems on 4.2 while everything else is on 5.0.20 could be affecting. Last night upgraded remaining unit to 5.0.26. We'll see what happens! Guess NOW I have to go back and upgrade the units from 5.0.20 to 5.0.26.

Recently upgrade 19 of our 406V2 systems from 4.2.4 to 5.0.20. All seemed to work OK, but day or so later started having issues. One system could not make calls to other branches via IP line. Upgraded and rebooted "hub" system at HQ and all seemed well. Today one system could call internally...

Thanks for the info. Doesn't sound too promising for the "direct line users." Originally looked into putting a PRI in this location, but was cost prohibitive. Please keep the comments coming!

Forgot to mention....this is a 406V2 unit running 4.2(24) and phones are 4412D+

We have an office that has a hunt group set up with 3 incoming lines for "general callers." We also have 3 people who have a "direct line." Each of the direct line users have their own Incoming and Outgoing line ID. I have a "9N" short-code set so that these users call out on their line. The...

Mystery Solved!!! The compression mode setting for the line going to the "affected" branch had been set to G.723.1 6K3 MP-MLQ instead of G.711 ULAW 64k like all our other branch lines. Made the change, rebooted system, and ALL IS WELL! Thanks to everyone here on the forum for all your...

The affected office can call our main office (which is where PRI is located. The can call any of the Avaya 4412D+ phones, but I hooked up an IP hone in the same building, off the same switch as the phone system in our main office and no go. The IP phone can call the affected office but the...

We do have another office and yes then CAN call there. The other office is going thru a different PRI for there calls. The weird thing is, about a month ago I set up another office configured exactly the same as the office that is having issues and it works fine.

So much for "Allow direct media path"...unchecking box didn't make any difference. Open for more suggestions.

Yes, it is....but, all of our other office can call without a hitch. In fact, I believe all of our IP phones have that box checked (default) I will try unchecking the box on one of the IP phone extensions and test it, but because these phones are located at our main office I won't be able to...

We have about 20 offices using IP Office 4.2(24). Recently set up another and everything seemed OK exect that office can't seem to call one of our offices that is using IP phones. The IP phone office can call THEM but not the other way around. The "affected office" can place the call to the...

OK....What about a person who can hear the caller, but caller can't hear them....almost like MUTE is on when it's not. Does the *00 clear this as well?

What exactly does the *00 do....I thought that code was to "cancel all forwarding?

I appreciate the comments. On one of the phones recently that had tone but no dialtone, I unplugged set for a while and then replugged and dialtone had returned! We have about 20 branches running IP Office 4.2.4 on 406V2 and 412 boxes, it seems strange that only one location has had this...

OK, I checked with the Tech who did the upgrade to the devices. The proper progression to 4.2.4 was followed. Any other ideas??

I'm not 100% sure that the upgrade followed the correct progression thru 3.2.99 or direct to 4.2.4. I will try to get this info from our tech when he gets back next week.

We have one office that has an IP412 with a DS30 and DS16. Over tha past year we have reports from 3 different extensions that they pick up their handset, and all they hear is a tone (almost sounds like a stuck key, but is not.) Tried unplugging set, no change. ended up putting them on a...