[cisco-voip] SRST Functionality
Tim Smith
thsglobal at gmail.com
Wed Sep 10 04:06:25 EDT 2008
Look at CME in SRST mode. Gives you more features. Basically anything you
can program in CME you can have.
Most notable features are CME hunt groups, and CCM style pickup groups,
park, you can even use your HW conf resources I believe.
You configure it to auto provisions the extensions. So it auto-registers the
phones the same as SRST.
If you need a specific feature for some phones, you can attach config to the
directory number, without knowing the mac of the phone.
One of the guys mentioned a product a couple of days that syncs CCM and CME
/ SRST configs.. that sounds like it is worth a look.
Be aware there are limitations with CME-SRST, less numbers of phones
supported.. cant remember the rest of the top of my head. Check it out on
CCO.
Cheers,
Tim
On Tue, Sep 9, 2008 at 10:21 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> Unfortunately, I don't think you will find an exhaustive list of what
> SRST offers and what it does not. It's a shame really. It requires
> additional resources on our (the admin) side in order to provide
> documentation to our clients.
>
> That being said, it's easier to say what you will lose than what you will
> have during SRST. If you can't program it in SRST, then you will lose it.
> Things like internal call display are lost, call park is also lost. Line
> text labels I believe are also lost.
>
> You do have the option to put a call on hold, transfer a call (although it
> is immediate tx, once the dial peer is dialed it's off). You have conference
> bridge as well using the phone's bridge (up to three people). And you also
> have call waiting if you configure max lines 2 or something like that.
>
> Something you also lose is CDR. Yup. No CDR. And no way to import CDR into
> CCM after the fact. You need a radius server to send the CDR logs to. Plus
> good luck finding some support on how to configure CDRs for export. Turns
> out, it's all H323/RADIUS based. And you're always gonna get two records one
> for each call leg.
>
> All in all, it's great for temporary interruptions. Even extended periods.
> Of course, if you have IPCC or stuff like that , things break.
>
> Lelio
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ...seen on a Geek Squad patch cord: "While it is the same length, this 7'
> crossover cable
> is not regulation issue for most competitive Manhattan double dutch
> leagues.
>
> ----- Original Message -----
> *From:* Todd Franklin <toddnh65 at gmail.com>
> *To:* cisco-voip at puck.nether.net
> *Sent:* Tuesday, September 09, 2008 3:21 PM
> *Subject:* [cisco-voip] SRST Functionality
>
> I have 6 buildings connected with fiber. Each building has a 2801 with
> SRST and 2 POTS lines.
> Let's say that building 1 has CCM and Unity. In building 2, we lose the
> link to building 1.
> What would I lose for functionality? For instance:
>
> Could I put a call on hold? Could I park a call? transfer a call (within
> building 2 and maybe to another building?)
> We have 7914s, would they lose their text labels?
>
> Thank you!
>
> ------------------------------
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080910/6ced2558/attachment.html>
More information about the cisco-voip
mailing list