Search results for query: *

IPGuru, thanks for the suggestions. I followed your instructions: 1. Powered down 2. Removed Dual E1 card 3. Powered back up 4. In Monitor, still shows 'System Local>default' Therefore, I decided to remove IP Office Admin Suite entirely and reload Manager to match IP Office release...

Thanks for all your help guys. I have changed the System Locale to Australian (UK English), Italian, etc (rebooted the IP Office) and nothing seems to change the status of the dual PRI card to dual E1. I'm at a loss.

The card we purchased is a dual E1 card, at least that is what it says on the packaging.

I need my European brothers. I'm in the US. I'm trying to get a dual E1 card to register as an E1 card in an Avaya IP406v2. We are trying to do some testing with E1 here in the US, but for the life of me the IP406v2 won't register the dual card as E1. This is what I have: 1. IP406v2 2...

If you are located in North America, copper trunks usually denote analog lines (flat-rate business lines, 1fbs, COs, whatever you wish to call them). As such, you CANNOT have DIDs on analog facilities. DIDs are only available on digital facilities like T1, T1-PRI, and other technologies like...

10/100 full

OK, We got it up and working. Here is what we had to do. We logged in via SSH and told the IPO SE to run the old ISO. Running the upgrade / downgrade didn't work. We had to type it out via command line to run the old files. In short, downgrading the IPO SE fixed it. I'll let someone else...

Is this problem scaring off all the Tek-Tip greats? 1. amriddle01 2. tommills 3. hairlesssupportmonkey 4. tlpeter 5. westi 6. gunnaro Sorry if I've missed any of you others. Calling all you guys out by name. haha. Basically we have a dead production IPO, it sucks. I knew we shouldn't...

We have an Avaya IPO Server Edition, release 9_0_0.185 We just tried to upgrade the IPO SE to 9_0_2.085 After upgrade, web manager comes back online, voicemail pro comes back on line, system is upgraded to 9_0_2.085 but when you try to start the IP Office service is starts BUT then STOPS 5...

Jason78, Yes. After creating the user and giving the user an internal extension, like '100', you must go to the EXTENSION folder in the configuration list (along left side of Manager). If this is for a VoIP phone, you are correct Avaya always starts their random, arbitrary VoIP Base Extension...

Jason78, Here is what you need to know: 1. Program your telephone system users in the USER tab of Manager. You give them their names, full names, and extensions. Ex: John Smith, extension 100. 2. Next, associate your USER extensions (that you just created above) to the EXTENSION tab of...

You need SIP end point licenses, not 'trunks'.

intrigant, no I did not use mode config. On the Netgear FVS338, the 9641G came right up. I loaded the latest .tar files, etc from R7.0, and it works fine. I just can't get the same phone to work on a Sonicwall.

cemsenkal, please start a new thread. In reference to the thread that I started, I finally got the 9640 up and working, some minor tweaks needed to be made on the Sonicwall. We did not do the 'mode config' because that was not an option unless we were doing a 'site to site' vpn (which we were...

I have a 9640. That phone should have a good working vpn mode, correct? I'll try it (making change on the Sonicwall) and let you know. Thank you.

tlpeter, tried to be proactive and use the 'mode' config (IKE Config Mode) and I get a VPN Tunnel Error, 'Invalid Configuration' which would lead me to believe that I must change the configuration type on the Sonicwall, correct?

tlpeter, are you referring to enabling the IKE Config Mode?

Ok, I have a 9608, 9640, and 9641G (all in VPN mode) that I wish to get working off an Avaya IP Office R7.0(5). So far, no luck. After much reading and looking at the 100+ other IP Phones in VPN mode that I have done through the years, I am left to assume that since the new 9600 series do not...

AT&T told me yesterday that due to 'Unknown Dialing Plan' and 'National Numbering Plan' that their rate centers treat calls differently based on Local and Local Toll. Since customer has no idea to either dial a '1' or not before a 321 area code (which is local) then the central office needs to...

I don't have any POTS (analog) lines. Just one PRI.