[cisco-voip] Single Number Reach, CallerID and Avaya

[Scott Voll]

Chris--

I would either change to using the phone number mask on the phones, or setup
multiple Route Patterns with different masks in different partitions using
CSS to make them mask correctly.

IMHO I would use the line mask.

Scott

On Tue, Oct 26, 2010 at 9:57 AM, Christopher Trown <ctrown at uoregon.edu>wrote:

> On 10/26/2010 9:13 AM, Scott Voll wrote:
> > He's referring to the fact that the caller ID from the AVAYA to the Cisco
> > SNR is incorrect.
> >
> > Caller from Avaya side, calls the Cisco DN.  SNR is activated, but the
> > Caller ID coming from the Avaya is prefixed with the Cisco area code /
> > prefix instead of the avaya area code / prefix.
> >
> > Chris, correct me if I got that wrong.
> >
>
>
>      That's exactly it, Scott.
>
> Chris...
>
> >
> > On Tue, Oct 26, 2010 at 8:44 AM, Ryan Ratliff <rratliff at cisco.com>
> wrote:
> >
> >> Assuming that 61234 is defined as a remote destination for 61010 then
> this
> >> is part of how SNR works.  Any call from a remote destination shows as
> the
> >> internal DN/name.
> >>
> >> What is your problem for this behavior?  If the two phones aren't owned
> by
> >> the same person then this isn't what SNR is intended to be used for.  If
> >> they are, what does the number matter when both phones will ring when
> the IP
> >> phone is called?
> >>
> >> -Ryan
> >>
> >> On Oct 22, 2010, at 7:43 PM, Christopher Trown wrote:
> >>
> >>
> >>
> >>
> >>    Greetings.
> >>
> >>    I hope this description makes some sense.  The DIDs have been
> >> changed to protect the guilty.  ;)
> >>
> >> System description:
> >>
> >> CUCM 7.1.3 with a 2921 as a MGCP gatekeeper
> >>
> >> Avaya CM running CM 5.2.1 SP#4
> >>
> >> The two systems are interconnected using a QSIG trunk.
> >>
> >> All PSTN trunks are connected to the Avaya.  The University has two DID
> >> blocks.  We'll call them 213666XXXX and 213777[0-2]XXX.  I've allocated
> >> 21377727XX to CUCM.
> >>
> >> Stations on the Avaya system can call stations on the Cisco system and
> >> vice-versa using 5-digit extensions.  I have both systems exchanging
> >> 5-digit extensions to make inter-system calls.  Off-net calls work as
> >> well.  I have CUCM prefixing 21377 via a Calling Party Transform before
> >> submitting the call to the trunk for off-net calls.  I do this at the
> >> Route Pattern for off-net calls.
> >>
> >> I've been looking at Single Number Reach and it seems to mostly work.
> >> However, when a call from an Avaya station calls a station on CUCM, the
> >> resulting Calling Party number is incorrect.  For example, if a call is
> >> made from Avaya station 61234 to a CUCM station, the Calling Party
> >> number that gets displayed on the cell phone is 213-776-1010, rather
> >> than 213-666-1234.  Recall that I am inserting 21377 on off-net calls.
> >>
> >> Is there a way to alter this behavior on the Cisco?  Anyone have any
> >> suggestions as to where to look for a solution?
> >>
> >>    Thanks!
> >>
> >> Chris...
> >>
>
>
> --
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101026/ccec3ac1/attachment.html>