Search results for query: *

H.323 was off, once we turned it on phone started working.

So I have two Avaya phones (9650 and 9620L) that were working fine in my old house behind a sonic wall. I moved to a new house, new sonic wall, different IP address range. VPN to my office has all the ports open. Phones wouldn't get a dial tone so I figured I'd reset them. Do both RESET and...

We finally have our ones mobile app on the iPhone working well with our IPO (now on version 9 with SP1). We have the following questions/issues and was hoping someone could provide the answer. Our installer is at an Avaya U course in NJ this week (he spent most of his career on Nortel stuff so...

I just tested this on WiFi and had the same problem, so I'm guessing it has something to do with the routing/firewall rules. Working that angle now.

Everyone, thanks for the help, the second DNS entry worked. Things are working great for WiFi in the office and at my home (which is connected via a physical sonic wall), but we can't get it complete a call over LTE even though all the ports are open (and even with a VPN connection running on...

Hi folks, We are having the same problem, I think I understand the messages but just want to be clear. Right now 1xmobile and IPO have two separate and distinct IP addresses, both of of which regular public IP addresses (no NAT). Every port listed in the installation manual is open now to...

The problem with that approach is that so long as there is any chatter between the phones and the pbx the bandwidth isn't available to any other services/devices.

We have some phones in remote locations (9650s) with crappy limited DSL (i.e, upstream bandwidth peaks around 400k/second on a good day). Right now one location has a Sonicwall TZ 190, the other is getting a newer 205. In order to configure better bandwidth management I'm trying to determine...

My guy is coming to do it tomorrow at 7AM. Full disclosure, my guys were the top Nortel guys in my market by a long shot; pick a bit Nortel CS install and they did it. They are learning Avaya and are doing 2-3 IPO installs a month with all the promotions to migrate off old Nortel hardware, so...

Installer said he would get back to me, he didn't know the answer. Thought it might be something simple that we are missing.

So we have had IPO for about 6 weeks and someone walked into my office and said how the ___ do I make a call with caller ID blocked. He tried 9, *67, number, *67, 9 number and neither work. We are in a sales related field and sometimes the only way to get someone on the phone is to call with...

Just enable Flare in IPO for the user. On iPad you'll need to be authenticated to through sonicwall (we use the sonicwall client). Works well (wish the iPhone could work that way).

So is there a systemwide setting that is forcing IPO to only send out or main caller ID? Can it be disabled? Where is it?

Yes, short code overwrites the default.

With that SC code removed what gets sent when I call another number is our generic switchboard phone number. If someone calls my extension and it twins to my mobile it sends the same generic caller ID, not that of the internal caller. I went back to what I had, hopefully Avaya will fix/change...

So if I took that out, my caller ID would include my full number, not our generic main number? I guess I could test it.

I do have one to ensure that the proper caller ID gets sent out for me.

For the short code there are six options: Code - blank box Feature - Dropdown menu, on "Dial" Telephone Number - blank Line Group ID - Dropdown menu, on "O" Local - Dropdown menu - blank Force Account Code - checkbox, currently unchecked. How would I enter the short code above into this area...

What exactly is SC? I'll try making the change if I can find it on the user page.

What does this mean? "Had it not working on a customer site before and the problem was that they dialled out using User SC and not System SC." My extension is 760. When 766 dials 760 and 760 is twinned to my mobile phone, the caller ID comes up as xxx-xxx-x760, not xxx-xxx-x766...