[cisco-voip] CCM CTI redundancy

[Wes Sisk]

To have redundancy with CM down, you will need to lose that MTP 
required.  The audio path will have to be established directly between 
the phone and gateway.  Are you using the CTI based softphone or 
IPCommunicator?

If you hangup, and retry the call, the local MTP's of the secondary 
server should have re-registered to the local secondary ccm process and 
the call should go through and you will see remote media addr = 
secondary server.

Again, with MTP, you're not going to get clean call survivability.  the 
audio stream is using the MTP hosted out of the IP Voice Media Streaming 
App on the server.  When that process goes away b/c box loses network 
connectivity or server unexpectedly halts for hardware, that audio 
stream will be dropped.

Need to get around having MTP required.

/Wes

Ryan Fields wrote:

>Thanks Ryan. I think replication is working, the MTP required
>configuration on the Primary is also checked on the Backup. I have
>tried this on a similar setup using callmanager 3.1(2c) and still came
>up with the same problem. Any other workaround ?
>
>JRyan
>
>
>On Apr 6, 2005 12:23 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
>  
>
>>If you are seeing the CM as the RemoteMediaAddress it most likely means
>>that you've got MTP required checked for that gateway in CCMAdmin.
>>
>>Check to see if replication is working between the publisher and
>>subscriber.  Assuming the pub is the primary server then when it goes
>>down the sub will use it's local database and if the "MTP Required"
>>option isn't set there then that could cause this issue.
>>
>>-Ryan
>>On Apr 5, 2005, at 12:04 PM, Ryan Fields wrote:
>>
>>Hi All,
>>
>>I have a callmanager cluster using 3.3 and setup
>>cisco softphones with failover. When I use the
>>primary server, everything works well.
>>A show call active voice on the AS5400 gateway
>>showed the connection details below:
>>
>>Using Primary Callmanager Cluster (Normal Operation)
>>VOIP:
>>RemoteIPAddress=216.226.244.2
>>RemoteUDPPort=24596
>>RemoteSignallingIPAddress=216.226.244.2
>>RemoteSignallingPort=2165
>>RemoteMediaIPAddress=216.226.244.2
>>RemoteMediaPort=24596
>>RoundTripDelay=0 ms
>>SelectedQoS=best-effort
>>tx_DtmfRelay=inband-voice
>>FastConnect=FALSE
>>
>>The problems starts when I simulate a failure on
>>the primary, the backup takes over but I encounter
>>oneway audio. How come the remotemediaaddress takes
>>on the primary's ip address on a normal condition
>>and takes the address of the computer using the
>>softphone during failover?
>>
>>Using Backup Callmanager in Cluster (Failure on Primary CCM)
>>VOIP:
>>RemoteIPAddress=216.226.244.3
>>RemoteUDPPort=30942
>>RemoteSignallingIPAddress=216.226.244.3
>>RemoteSignallingPort=1034
>>RemoteMediaIPAddress=172.16.10.72
>>RemoteMediaPort=30942
>>RoundTripDelay=0 ms
>>SelectedQoS=best-effort
>>tx_DtmfRelay=inband-voice
>>FastConnect=FALSE
>>
>>Did I miss any configuration.  I made a callmanager
>>group and defined it to a device pool that
>>my softphones use. Both callmanagers are also
>>configured with 172.16.10.0/24 addresses
>>and are using a 1 to 1 static translation on the
>>gateway router.  The pc using the softphone is not
>>translated.
>>
>>Thanks,
>>Ryan
>>_______________________________________________
>>cisco-voip mailing list
>>cisco-voip at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>    
>>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>  
>