Jump to: navigation, search

transport.routerecoverytime

Section: sip
Default Value: 30
Valid Values: Any integer in the range 1-600
Changes Take Effect: At start/restart


Specifies the recovery time in seconds for SIP static routing and DNS HA routing. When SIP static routing or DNS HA routing is enabled and the route is marked as unavailable due to error or SIP response timeout, the route will be marked as available again after the recovery time.

transport.routefailovertime

Section: sip
Default Value: 5
Valid Values: Any integer in the range 1-32
Changes Take Effect: At start/restart


Specifies the failover time in seconds for SIP static routing and DNS HA routing. If a SIP request has not received a response within the failover time, and SIP static routing or DNS HA routing is enabled, the SIP request will be retransmitted to an alternate route.

8.5.184.06

T-Server-CUCM to Media Server Connector Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
11/22/17 General X X

Helpful Links

What's New

This release contains the following new features and enhancements:


Resolved Issues

This release contains the following resolved issues:


T-Server-CUCM to Media Server Connector no longer terminates unexpectedly while processing the SIP 491 response. Previously, if T-Server-CUCM to Media Server Connector triggered a session re-INVITE at the same time the Media Server triggered a re-INVITE message, the Connector sometimes terminated unexpectedly. (GVP-24057)


T-Server-CUCM to Media Server Connector no longer supports SSL v2 for security reasons as per OpenSSL recommendations. (GVP-35323)


T-Server-CUCM to Media Server Connector now displays the transport.routefailovertime and transport.routerecoverytime parameters in its configuration. Previously, these parameters were not available to the user. (GVP-21443)


T-Server-CUCM to Media Server Connector no longer prints its version information multiple times in the log file. (GVP-20416)




Upgrade Notes

No special procedure is required to upgrade to release 8.5.184.06.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on November 22, 2017, at 23:54.