When you set the record format for Unity this is set system wide so all recordings will be done in that format. There is no per port/users/handler/etc... configuration that will have Unity record in different formats under different conditions. If you set us to 729a, all inbound streams will be converted on the fly to 729a if they are not already in 729a. Same deal for 711 or any other format you select using the SetRecordFormat tool.
I get the occasional request for supporting 729a and 711 at the same time but the mechanics of doing that are a little tricky. I guess per port would be the most logcial mechanism. If you had your way, how would you want the record format(s) dictated in this scenario? per user? per port?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...