[cisco-voip] SRST Question

[Ahmed Elnagar]

Check SRST 8.5 I think it has a lot more new features but I don't know
if documents released for it yet or not!

 

Best Regards,

Ahmed Elnagar | CCIE#24697 Voice

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Daniel
Sent: Tuesday, January 18, 2011 3:57 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] SRST Question

 

Hi All,

 

Can someone briefly explain some pro's and con's between two SRST types

 

Call Manager Fallback (Cisco Unified SRST)

*	Supports more phones
*	Less Flexible
*	Less Features

 

Telephony Service (CME in SRST Mode)

*	Supports less phones max 240
*	More Flexible
*	More Features

I'm starting to think that for our company there would be a mixture of
deployments most would be just a simple one time configuration of Cisco
Unified SRST. Then for some more complex sites we could utilise the
features of CME in SRST. For example reception consoles for us are not
setup in a DR architecture so we could utilise CME in SRST mode to have
the reception phone register to CME with the pilot number instead of
just its line numbers.

 

If we are running less than 240 phones off a SRST router would Cisco
Unified SRST and CME in SRST with the "srst mode auto-provision none"
command essentially in the simplest form be the same thing?

 

The only caveat I see with CME in SRST is that if someone saves the
config while in fallback the ephone-dn config etc is saved to the
running config which when switch back occurs would make the calls
terminate at the SRST router not CUCM and the registered phone.

 

Just weighing up the possibility of making all our SRST routers "CME in
SRST mode".

 

Any thoughts would be appreciated.

 

 

Thanks,

 

Dan

 

 

Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110118/81d5f427/attachment.html>