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

[James Buchanan]

Hello,

 

I think your best bet for this and other functions is to use CME as SRST
instead of just regular SRST. The SRND does a good job of explaining
this.

 

Thanks,

 

James

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Matthew
Linsemier
Sent: Monday, April 27, 2009 9:11 AM
To: cisco-voip at puck.nether.net
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. 

________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090427/3bf10dd7/attachment.html>