[cisco-voip] SRST with Call manager 5.0

[Erick Bergquist]

When the site isn't in SRST fallback mode, the inbound calls should be routed to Call Manager to be handled. If H.323, with dial-peers and if MGCP then the gateway and PRI endpoint will be registered to Call Manager and controlled by Call Manager itself when not in SRST mode and MGCP connection is active and registered. 

If the gateway is MGCP, you will need to configure the ccm-manager for fallback-mgcp so the voice-ports on the router (PRI, etc) fallback to H323 mode when MGCP connection fails.  SRST and MGCP fallback are two seperate items. 

In SRST Fallback (H323 also), you should have a pots dial-peer for the PRI with direct-inward-dial on it and then inbound calls will go to IP Phones registered to router in SRST mode. You may need to configure alias and/or translation rules if you have calls going to logical numbers (hunt groups, AAs, etc) so those numbers go to a real IP phone while router is in SRST mode.

HTH, Erick

----- Original Message ----
From: zohaib shabir <zohaibshabir at gmail.com>
To: cisco-voip at puck.nether.net
Sent: Tuesday, April 3, 2007 11:56:27 AM
Subject: [cisco-voip] SRST with Call manager 5.0

Dear All,

I have scenario where one side has call manager 5.0
cluster and the remote site has SRST enabled router with PRI line
terminating on it.My question does SRST will be able handle all the PRI
calls coming in locally or handled by call manager remotely.


-- 
Regards,
Zohaib Shabir
Network Engineer(Voice and Presales)
DWP Group, TECH Division
Ph:+92-302-8232689
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip







 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070403/b9066056/attachment.html