Trying to troubleshoot issues with voicemail pro with sync issues in both a select and non-select scenario. If you read the manual, you will find that Avaya is really good (yeah right) with documentation...
To finish off this thread they have finnaly released the firmware officially:
https://www.grandstream.com/support/firmware
They have sent me many notes for various models having a firmware update go official, today was the HT8XX models. So if you have a different model, they likely fixed those...
Oh, Avaya said they don't support wildcard on SIP endpoints including Avaya Workplace:
https://documentation.avaya.com/bundle/IPOfficeSecurity/page/Certificate_Name_Content.html
When I tried it didn't work but it's been a few years.
Since you are using Avaya Workplace you have 2 choices:
1. Buy a cert from a public CA
2. Add your root CA from your SE install to the devices.
If you can easily manage the CAs on your devices, use the private CA on your SE, IMHO.
I did a certificate from GoGetSSL.com, and they let me add an...
It is specifically NOT supported by Avaya. You are required to use the cables that come with the DS30.
You could run enough copper between the buildings, 25 pair cable and 2 cat 5+ cables. When doing extensions outside the building they are required to be grounded properly.
You are going to...
Grandstream has made the firmware update available on their website as a beta release (1.0.55.5 BETA):
https://www.grandstream.com/support/firmware
Just look to the right for "General Beta Firmware
So, the current status is... it's working.. dang it. ?
If you cleared the phone, it should be downloading the chain and if it works then success...
Or did I miss something?
I don't know where the cutoff in version would be, but downgrade wasn't an option based on the release notes. I have one with 1.0.23.5 that works.
They gave me the "release version" of the update yesterday to use and report on before they finally release it. I have attached the HT802 firmware...
I'm guessing you meant to say 11.1.2.4
It's a bug in 11.1.2.4 that was fixed in 11.1.3:
https://www.tek-tips.com/viewthread.cfm?qid=1821220
Just another mention of the same thing most likely:
https://www.tek-tips.com/viewthread.cfm?qid=1824097
I have a cert like Ekster, but get my cert from a vendor who will also include the IP address. I would recommend letting IPO generate the 46xsettings.txt and use 46xxspecials.txt for any customization.
For many customers I use a 46xxspecials.txt file like the following, it has more in it than...
I found I was unable to generate and apply a new certificate on my Server Edition systems. You can click the button, and it pretends to do something, but nothing actually happens.
There is a small bug where it puts a space in front of any " IP:X.X.X.X" you see in the SAN field.
Solution...
I have 8 or so Grandstream ATAs (HT802/HT801) used by customers and myself at remote locations. Some of them stopped staying registered. I figured out it would happen after the PBX rebooted or the internet went down somewhere between the PBX and the ATA. Rebooting the ATA fixed it. I just lived...
I don't have a R9.0 config to look at, R9.1 definitely has the SIP Advanced "Cache Auth Credentials", which I have unchecked for my nexVortex customers.
I THINK nexVortex can just use a static IP, but I'm not positive about that. Good luck.
I only post to say what I did using what was said above in the hopes it makes it as simple as possible for someone else.
I used BFG9K's solution at first. I found that if I use that XML file and fixed my manager, I could connect to all my customers systems and simply re-choose the TZ and save...
I noticed this recently on HT802s. I believed it was TLS related. I turned off SIPS (went straight SIP) and they seem to be reliable again. To fix them before I had to reboot the ATA.
Assuming you didn't just upgrade to 11.1.2.4, I have no help.
If you did upgrade to 11.1.2.4 there was a bug with 30Bs, maybe it also effects 16Bs. They have a hotfix, and/or you could go with 11.1.3 which lists the fix in the notes. But it does specifically mention 30B. I have done the fix on...
Ah, the power of borrowing. So the module that was doing the final transfer after dial by name literally said "DialByName ($)" in the source of transfer. I suspect IP Office was getting hung up on the $ in the header of the audio file and that's how it choked. I changed it to $CLID and they...
...OPUS to WAV wondering if that was the issue). When I leave a voicemail without DialByName it works as expected. The only fix is for them to dial *17 and delete the offending voicemail via the TUI.
Anyone else run into this?
I do have a SR open with Avaya and I expect a fix for this at some...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.