[cisco-voip] Emergency Responder Group for Multiple CM Clusters

[John Parduhn]

There was an issue in the route patterns with the calling party
transformation being checked.  We unchecked the boxes in the remote cluster
route patterns and disabled that functionality in CER and everything
worked.  The CER documentation gives conflicting instructions, so this
would've been a really difficult one to track down.  Thanks for the reply,
Mike.

John


On 12/8/06, Mike Lay (milay) <milay at cisco.com> wrote:
>
>  Nope, only one 911RP needed. You will need to ensure that your outbound
> route is good, meaning CER can successfully redirect the call to the correct
> 911 service. This will be sending the call out the correct local GW. I would
> turn up detailed CER tracing & see what in going on inside CER.
>
> Mike
>
>  ------------------------------
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *John Parduhn
> *Sent:* Friday, December 08, 2006 7:00 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Emergency Responder Group for Multiple CM Clusters
>
>
>  Do I need to set up JTAPI CTI route points on each cluster for CER and
> send 911 calls from the remote clusters to them, or is it acceptable to
> route 911 over an intercluster trunk to CTI route points built on a single
> central CM cluster.  I'm having issues with phones calling out with the
> default ERL ELIN using the latter method, even though CER sees the phone on
> the remote cluster and the switchport it's connected to has been assigned an
> ERL.  Any guidance would be appreciated.  Thanks in advance!
>
> John Parduhn
> Network Engineer-Voice
> Berbee Information Networks, Inc.
> 8725 W. Higgins Rd., Ste. 700
> Chicago, IL 60631-2716
> 630-867-6051 direct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061210/e447ebe1/attachment.html