Recent content by Luzie67

Thank you all! Work like a charm with Twinning! (including sending extension 385 correct internal and external).

We have an IPO500v2 on R9.1 Yet we have an extension number 385. I should attach a second phone which also rings parallel on number 385. So I think of making a hunt Group, where I put in the original 385 (renumbered to e.g. 384) and a new phone 386. So on calling 385 both phones 384 and 386...

Hi, today I´m trying to change all default passwords on a single, stand-alone IPO v9.1. I discovered there is a system account calles BranchAdmin with an (yet to me) unknown default password. The account was enabled. Can I disable System Account BranchAdmin on a standalone IPO (or change...

Yes, that was cause ! You make my day and keep my boss from decapitate me :-) Thank your very much !

I today installed a new AVAYA IPO with Firmware 9.1.4.0 Build 137. There are two ISDN-Lines / 4 ISDN-channels. Now I have the problem, that I cannot forward incoming external calls to external. Forwarding the incoming external call to an internal extension is OK. Also having an three person...

I can not sure say that it´s right, but have you tried to simple rename the .bin-File to .hex ?

From: "Avaya D100 Installing and Administering IP Office D100 100174766.pdf": To update the D160 handset firmware, you must install Microsoft .NET version 4 and you must use the D160 Upgrade Jig.

I´m an idiot ... I´ve turned off SIP-Registrar in the IPO because of the Warning "No SIP Clients" in the Error-List ... But D100 needs it ;-)

Maybe the problem is back with IPO 9.1 SP4 ? So it looks for to me today. Have to test on another IPO which I upgrade from SP3 to SP4 to verify this and then report this back here ... Update: With an IPO updated from SP3 to SP4 there seem to be OK: I can delete and create D100 without...

... Update for: ...: Yes, after creating an SIP DECT Extension following the AVAYA manual "Avaya D100 Installing and Administering IP Office D100 100174766.pdf" the D100 / D160 combination works well.

Oh sorry. I mixed up some things while looking for the actual firmware for the IPO. On the above Link: https://support.avaya.com/ext/index?page=content&id=SOLN264719&group=UG_ENTITLED_CUSTOMER was a hotfix for v9.1.1 and this was before "my" version v9.1.2 which I thought was the actual IPO...

OK, I have a new IPO with v9.1.2.0.91 and I´m still having this issue with getting an D100 (Firmware Version D100_1.2.2_0.8.6 Hardware Version 4) to work. In SystemStatus I see the D100 only with IP 0.0.0.0 Before I try to downgrade, I try using HFS as Webserver instead of IPO but has no...

> For faxing I gave up on Audiocodes and use Patton M-ATA instead OK. Sorry for the delay, but I now got the MP-112 to work. Shortly before I go out to buy a Patton M-ATA ;-) Sadly I don´t know for sure what has get the MP-112 going, as I altered some settings on it and the IPO. So here are...

On: http://tek-tips.com/viewthread.cfm?qid=1696472 i found an example INI file which works with ip- and extension-changes on our IPO. and MP-112 Software Version: 6.60A.241.010 But I got now face the same problems: Phone Calls from Extension to the Fax on the MP-112 are received and I get short...

OK. Thanks for pointing me to this threads. Will try tomorrow and send my feedback.