08-27-2004 07:07 AM - edited 03-18-2019 03:28 PM
4.0.3sr1
I believe i'm having issues concerning codecs. At the local site where Unity and Call Manager is in place, voice mail can be accessed using the 711. At the remote sites that are using 729, subscribers get a fast busy when dialing the voicemail pilot.
i have done the follwing to enable 729 on the Unity server.
i manually added the "G729 Enabled" key (Dword set to 1) in this path registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Active Voice\AvSkinny
I'm still getting a fast busy at the remote sites
please advise
08-27-2004 08:11 AM
Have you installed the 729a codec? It's not installed by default... just setting the registry key manually isn't going to be sufficient. If you haven't, run sl_g729a_setup.exe application, which is located in the Utilities folder to install the codec.
08-27-2004 08:36 AM
Yes, I've run this application. Also i found this not o be a codec issue.I resolved withing the calling search spaces in Call Manager
thanks
08-27-2004 09:00 AM
A correction to Jeff's post -- we do install and enable g.729 by default. I believe we started doing it around the time that 3.0 was release so unless it has been specifically disabled by changing the registry entry, it is safe to assume that Unity can support g.729 calls.
Thanks,
Keith
09-07-2004 10:32 AM
Hi Keith,
Could you please tell me how many G729 session can unity support as well as it supports G711 session at the same time?
If I have two callmanager clusters with one unity installed on each cluster using gatekeeper to connect with G729. I am concerning to use hardware transcoding to disable unity's default G729 support. What's the disadvantage/advantage of enabling unity G729 default support?
Thanks,
Joe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide