Search results for query: *

I haven't tried it with IP Office but the typical way on some systems is to add commas, so 9212551212,,,,,,,,,,,,,,,,1234567890 On those systems that accept it, each comma is a certain amount of time so you test and adjust as needed

(the new mac release will support TLS 1.3)

Here is latest from Avaya. New release on the 31st will support: Workplace 3.35 supports MacOS 14.0. Customer upgrading to MacOS 14.0 should upgrade Workplace release to 3.35. Workplace 3.35 release for MacOS is planned to be GA on 31st October ’23.

Thanks. I read that notice the other day. It basically says "don't upgrade your mac" lol I'm glad Avaya has noticed though and hopefully they will release a new version soon (or rework an old version?)

3.17 is working for us so far. 3.21 had some issue with the call reporting app apparently.

Thanks. If you have a windows emulator I've seen that work (using the windows Workplace app)

So you are using an older version on Sonoma that doesn't crash but has audio issues (silence)? What version is that if so?

Hmmm, I'm only finding 3.21 on support.avaya.com right now. Looks like the website has changed format some. I'll post back if I find one that works. I also have an old copy of 3.17...

Well I finally found some forums etc that had some info on this. location of log files: ~/Library/Logs/com.avaya.Avaya-IX-Workplace/logs/crashes: Crash dump files are not managed by the Avaya Workplace Client application and must be managed by you. For support, you might need to send these files...

Thanks. This one is an M2 macbook pro

I have a customer on IP Office 11.1.2 or something like that. This is not specifically an IP Office issue, after upgrading to OS Sonoma the mac Workplace app crashes repeatedly. Anyone else having this? I haven't gotten very far with Avaya or Apple yet. Also, the crash report below is for...

I was having this issue recently with SE 11.1.2.3 (using manager 11.1.2.4) and saw a closed post on Tek Tips about it with no answer. Issue is when logging in with Manager get IP Office: xx.xxx.xxx.xxx not found. Device might be offline or have version older than 3.2 To fix I turned off SE...

Sounds good--thanks! So make a new server and then can send the config to it? Or did you use a different sort of backup? I do see that some of the license fields are different in powered by (no VM license field for instance) so makes sense that there are some differences. Did you do all...

Other posts mention things not working if coming from Powered By to Non-select. Wondering about migrations to select though (still may not work) or just pointing to local webLM. At some point I may try it but don't have a test system to try it with quite yet...

I've opened an Avaya ticket but I'm curious if anyone has tried pointing a Powered By IPO server to a local webLM licensing source with success I'm getting tired of migrating these customers to new servers and have a very large migration coming up. If there is any way to keep the servers and...

If this IP Office assistance article is correct: " *DCP Dial 40000000,0,X,Y,0 l/g 0 (X affects internal calls and Y affects external calls) " Then the X Y codes are not working properly. X is affecting both outside and inside calls

Actually maybe those things were all the same--they just change throughout each trace. The non-working version (auto intercom) does have extra lines: 11:46:51 1209525934mS Sip: 0acd0a1a00000bd2 10.3026.1 -1 SIPTrunk Endpoint(f720c0d8) ExtractDiversionHeader: DiversionName: 11:46:51...

No, no change with turning off auto answer and then rebooting. I did roll back the ipo service to 11.0.4.4 and the call rings. Put it forward to 11.0.4.6 and the call auto answers. I sent both traces to Avaya. The only differences I see are some different numbers of media available and some...

Thanks. I have done with phones that had auto answer off already with the system rebooted. Just turning on auto answer on any phone creates the issue. But I'll look into trying your idea more directly just the same.

After upgrading Powered By systems (Basically Server Edition) to 11.0.4.6 (from 11.0.4.4 or 11.0.4.5), J179 phones with internal auto answer turned on no longer ring when called from their outside number (DID), they go to intercom. I have a ticket open with Avaya but if anyone has a fix (like...