[cisco-voip] SRST & Line Groups (non public DN's)

[Matthew Linsemier]

LOL... Actually it's not down that often at all, but I just want to make
sure that I have service when it is (I think we had like one 5 minute outage
in the last year).

I was looking into the CME solution, but I wasn't sure if this was licensed
the same way as SRST or if there was more to purchase.  I will check out the
updated SRND for sure.


On 4/27/09 11:29 AM, "Paul" <asobihoudai at yahoo.com> wrote:

> 
> I think the bigger question to ask here is, "WTF is your MPLS WAN down so
> often?" Sounds like you need a more reliable telco.
> 
> 
> 
> 
> ________________________________
> From: Matthew Linsemier <mlinsemier at apassurance.com>
> To: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> Sent: Monday, April 27, 2009 10:10:56 AM
> Subject: [cisco-voip] SRST & Line Groups (non public DN's)
> 
> Hey all,
> 
> I¹m looking for some suggestions on what is the best way to handle a Line
> Group in a SRST situation.  In our configuration we have a few remote offices
> that have a configuration similar to the following:
> 
> 
> 1234 (real DN)
> 5100
> 5101
> 5102
> 5103
> 
> The first line is the personal DN for the employee and the remaining four
> lines are configured in a line group, hunt list, and pilot configuration.
> When call manager is up, the hunt pilots all ring to the line group starting
> at 5100, top down.
> 
> When the SRST is enabled due to the MPLS WAN being down, these lines will
> register with the phone, however the 5100-5103 numbers aren¹t valid E.164
> numbers.  Is the best way to make sure that our pilots that are in call
> manager ring down to 5100 or maybe even map one to one still to use the alias
> command?
> 
> ...
> Alias 1 5678 to 5100
> Alias 2 5679 to 5101
> ...
> 
> If so, is there a way to simulate line group functionality?  Any input would
> be greatly apprecaited.
> 
> Matt 
> 
> ________________________________
> 
> CONFIDENTIALITY STATEMENT
> This 
> communication and any attachments are CONFIDENTIAL and may be protected by one
> or more legal privileges. It is intended solely for the use of the addressee
> identified above. If you are not the intended recipient, any use, disclosure,
> copying or distribution of this communication is UNAUTHORIZED. Neither this
> information block, the typed name of the sender, nor anything else in this
> message is intended to constitute an electronic signature unless a specific
> statement to the contrary is included in this message. If you have received
> this 
> communication in error, please immediately contact me and delete this
> communication from your computer. Thank you.
> 
> ________________________________
> 
> 
> 
> 

CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.