Hi, I have a CM 5.1 system with 2 CM's in the cluster. I have 22 voice gateways all configured as H323. I have the following dial peers configured in some variation for incoming calls on each gateway:
dial-peer voice 44 voip
voice-class codec 1
session target ipv4:10.100.1.5
dial-peer voice 45 voip
voice-class codec 1
session target ipv4:10.100.2.5
10.100.1.5 is my publisher and 10.100.2.5 is my subscriber. Everything works just fine in this configuration when all my servers are up.
The problem: My publisher went down the other day (10.100.1.5) and all incoming calls got a busy signal. All the phones were registered and could make outgoing calls just fine.
My Question: Do I have this backup dial peer for the subscriber configured correctly? Is there something in CM I need to enable for this backup dial peer to work properly? For whatever reason in this configuration calls would not get forwarded to my subscriber.
I am looking for people's input on WAAS Printing services...pros and cons discovered.
Has anyone encountered any problems or issues after configuration and implementation?
I am looking at implementing WAAS Printing (WAE-512/612's) too but want to know how reliable it is.
Do you happen to know how many printers it can service/support? I understand it only has 1 GB Spool limitation and wondered what would happen if many people began sending print jobs larger than that to it...would it crash?
Then add the following to both the dial peers you listed so they associate with the new class:
NYCgateway(config-dial-peer)voice-class h323 10
The calls were not failing over to your SUB in the inital configuration because the default for this to occur is 15 seconds. (I think.) If your calls arrived on PRI, the ISDN setup would timeout before 15 seconds. The new class will shorten the timer to 3 seconds which will provide the redundancy you wish.
With both dial-peers on your gateway, have you ran a debug on your voip dial-peer to verify that you are indeed hitting your dial-peer to your subscriber? You gateway may still be sending them to your publisher.
Run a debug voip dialpeer all
and see exactly what dialpeer you are using.
Here is a link to what the previous poster had said about the shorter time out value.
I did run the dialpeer debug and verified that it was in fact hiting the correct dialpeer. I even changed the session target to my publisher, and it worked right away.
I did verify that the Call Manager service on the subscriber was in fact started and running. I didn't want to restart the service right now since there are about 300 phones in the cluster and they are all registered to my subscriber
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...