Is there any "best practice" procedure for downgrading a new TCS from s5.3 to s5.1 to allow communication with a Kontiki server? The Kontiki is currently working with an existing TCS running s5.1, the new TCS will operate independently and not be clustered in this scenario. Thank you
You can downgrade a TCS, open a tac case to get the procedure or send me your e-mail and i can send you the documentation with the steps tomorrow morning. However by downgradimg you will lose your data on the TCS you are downgrading.
The effort to search the best and simplest explanation of complex topic is so harder and passionate. You test, you analyze and you imagine the best schema to explain it, even the size of you drawing is taken into consideration.
This is what I did f...
view more
MARS Emergency Alerts helps an organization to create, distribute and manage enterprise wide notification to all employees in the enterprise in a systematic and efficient manner.The application allows alerts to be broadcasted to Cisco IP phones by the app...
view more
The acronym "STUN" stands for two definitions with two different meanings as follows:
STUN - Simple Traversal of User Datagram Protocol (UDP) ---> RFC 3489 published in 2003 - works only with static NAT to establish a direct connectivity between...
view more
Inbound CSS and Rerouting CSS with Cisco Unity Connection Transfer rules:Release to Switch: this type of transfer uses the SIP Refer method to reroute the call to the specified extension, it is sent in dialog in other words in the existing SIP conversatio...
view more
I just finished to write an interesting document, instead of multi SAN Certificate, this document shows how to configure different certificates for WebBridge and CallBridge using different CA Server.
