It seems we finally got this to work as expected with 2.1(44) with some caveats.
Caveat 1: 2.1(44) has a Calller ID bug - Avaya is working to fix it.
Caveat 2: Must use G711, you can't compress the call - If you have the bandwidth you'll be fine. Compressed call quality is inconsistent while...
bsmo,
Thank you very much for your input.
I agree with you as far as the voice packet size goes, for the media streaming aspect of it, but I was wondering if the H323 registration process or packets to some kind of keep alive the IP Office sends was not being blocked.
For the current IPSec...
Well fellows, after a week or so we are still experiencing the trouble every now and then. We are still running 2.1(44)
Things I learned:
1)If we "hard code" the IP Phone IP address under VoIP tab, the trick of changing the IP address to bring the phone back up doesn't work anymore. It makes...
We have had Gatekeeper ON before. Just now is OFF. I can switch it back to ON.
As far as the IP address in the VoIP properties we tried both ways. Because we have been relying on changing the IP address of the IP Phones to get them back up, we now have a empty field right there.
The idea was...
mytelecoms, thank you so much for your reply.
To answer your question we have 4602s and, I believe, two 4612 connected to a 406 IP Office. The phone loads are the IP Office loads that came with the 2.1(44) software. All the phones experience the same problem.
Codec is G729a, Silence Suprssion...
mytelecoms, I work with jopling, and he asked me to touch base with you, because of your success with IP Office.
I'm doing this in the open forum in the hopes this can help other IP Office users.
Could you please let us know the exact software version you are running?
You also expressed a...
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.