Has anyone managed to configure AAR for an intercluster trunk between a CM 4.0 cluster and a 3.3(3) cluster? I can get it to work going from the 3.3 to 4.0 cluster but not the other way.
I removed the Example Administrator account as per the Tech Note on the TAC site (Document ID 26846). This subscriber also appears to own the ch_defaulttemplate and be the message recipient for this call handler as well.There isn't anyway of changing...
You might get some ideas from this thread ...http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dd6192e/9#selected_messageYou can contact me through BluePages (I'm in Brisbane...
My usage of AAR was incorrect - failover is probably a better term. From the 3.3 side the remote cluster members are registered as H.323 gateways with the external mask and are in a route list with the trunk. If the trunk fails then it dials via the ...
I find it useful to do a router# show dialplan number 5081and see what dial-peers match the dial-pattern. If you have more than one matching, make sure the one you want has a better preference ...
