_
From: ccie_voice-boun...@onlinestudylist.com
[mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Prashant Patel
Sent: Wednesday, December 29, 2010 7:17 PM
To: Justin Brady
Cc: OSL; study2b ccie
Subject: Re: [OSL | CCIE_Voice] Single Number Reach
That was in reference to if you are using a
t;
>
>
> Justin
>
>
>
> *From:* Prashant Patel [mailto:prashantpatel...@gmail.com]
> *Sent:* Wednesday, December 29, 2010 5:02 PM
> *To:* Justin Brady
> *Cc:* study2b ccie; OSL
>
> *Subject:* Re: [OSL | CCIE_Voice] Single Number Reach
>
>
>
> When BR1 or
stin
From: Prashant Patel [mailto:prashantpatel...@gmail.com]
Sent: Wednesday, December 29, 2010 5:02 PM
To: Justin Brady
Cc: study2b ccie; OSL
Subject: Re: [OSL | CCIE_Voice] Single Number Reach
When BR1 or BR2 phones dial an HQ extension that invokes SNR, the call goes
from the local gateway of t
89
>> (703) 282-0690
>>
>> ** Cisco Silver Partner * Microsoft Gold Partner
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
ilver Partner * Microsoft Gold Partner
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Follow the Network Operations Center on Twitter:
> www.twitter.com/TSGSigCare
>
> Follow the
mber 29, 2010 1:57 PM
To: Prashant Patel
Cc: OSL
Subject: Re: [OSL | CCIE_Voice] Single Number Reach
Hi Prashant,
After further testing, I found out the problem was caused by standard local
route group, somehow it will stop routing out to SNR I set in the remote
destination profile.
I then created a
Hi Prashant,
After further testing, I found out the problem was caused by standard local
route group, somehow it will stop routing out to SNR I set in the remote
destination profile.
I then created a new, separate RP/RL/RG pointing them to the SNR on SiteB,
then it worked.
Thank you very much fo
Did the HQ1 phone have access to the route pattern to call the BR1 SNR
Number?
On Tue, Dec 28, 2010 at 6:06 PM, study2b ccie wrote:
> Hello experts,
>
> Happy Holidays!
>
> I was in a vRack session this morning. I worked on Single Number Reach.
> Here was my problem:
>
> PSTN->Br1(SNR), both Br1
Hello experts,
Happy Holidays!
I was in a vRack session this morning. I worked on Single Number Reach. Here
was my problem:
PSTN->Br1(SNR), both Br1 and PSTN rang, SNR worked.
HQ1->Br1(SNR), only Br1 rang, PSTN did not ring, but when I chose to push
the call out to mobile phone using Mobility s
I created two calling party transformation patterns.
2XXX becomes HQ 7 digit external number
3XXX becomes BR1 10 digit external number
No need to touch BR2 since everything else uses E164 anyway.
On Oct 4, 2010, at 11:00 AM, Graham Hopkins wrote:
> Yeah just glad I finally got my head aroun
Yeah just glad I finally got my head around it. For anyone having issues with
how the various patterns are matched and the transformations are applied I
suggest that is worth setting up the following:
Translation pattern -> RP > RL > Transformation Pattern at the Gateway and then
applying chan
Fantastic. Thank you for taking the time to do this and for sharing it with
everyone.
On Oct 4, 2010, at 10:08 AM, Graham Hopkins wrote:
>
> Mark,
>
> having done some further tests, I now have this working - the key here is
> that the calling number transformation pattern matches the callin
Mark,
having done some further tests, I now have this working - the key here is that
the calling number transformation pattern matches the calling number at the
time the route pattern was matched. So this is likely to be 2001 as I presume
that the external phone number masked is applied as a t
ay.com]
Skickat: den 3 oktober 2010 19:18
Till: Roger Källberg
Kopia: Graham Hopkins; CCIE Voice Maillist
Ämne: Re: [OSL | CCIE_Voice] Single Number Reach
Hmm, for Single Number Reach? If a call comes in to HQ3 and simultaneously
rings the PSTN/SNR number, and the PSTN answers the calls, I b
; Turn off privacy Roger Källberg
> > CCIE # 26199 (Voice)
> > Unified Communication Consultant
> > Cygate AB
> >
> > From: Mark Holloway [mailto:m...@markholloway.com]
> > Sent: den 2 oktober 2010 06:24
> > To: Graham Hopkins
> > Cc: CCIE Voice Mai
(Voice)
> Unified Communication Consultant
> Cygate AB
>
> From: Mark Holloway [mailto:m...@markholloway.com]
> Sent: den 2 oktober 2010 06:24
> To: Graham Hopkins
> Cc: CCIE Voice Maillist
> Subject: Re: [OSL | CCIE_Voice] Single Number Reach Is there a specific
> settin
rom: Mark Holloway [mailto:m...@markholloway.com]
>> Sent: den 2 oktober 2010 06:24
>> To: Graham Hopkins
>> Cc: CCIE Voice Maillist
>> Subject: Re: [OSL | CCIE_Voice] Single Number Reach
>>
>> Is there a specific setting to force the ip phone to display a
gt; To: Graham Hopkins
> Cc: CCIE Voice Maillist
> Subject: Re: [OSL | CCIE_Voice] Single Number Reach
>
> Is there a specific setting to force the ip phone to display an "in use"
> message in the event the pstn phone answers the incoming call?
>
>
> On Oct
Turn off privacy
Roger Källberg
CCIE # 26199 (Voice)
Unified Communication Consultant
Cygate AB
From: Mark Holloway [mailto:m...@markholloway.com]
Sent: den 2 oktober 2010 06:24
To: Graham Hopkins
Cc: CCIE Voice Maillist
Subject: Re: [OSL | CCIE_Voice] Single Number Reach
Is there a specific
Is there a specific setting to force the ip phone to display an "in use"
message in the event the pstn phone answers the incoming call?
On Oct 1, 2010, at 11:42 AM, Graham Hopkins wrote:
> Same here , I was beginning to think that no patterns are matched in calling
> number transformations -
] Single Number Reach
I'm having a hard time when an internal extension calls another internal
extension that uses SNR, the "From" phone number on the PSTN phone is 4 digits
instead of 7. For example, extension 2001 calls 2003, and 2003 simultaneously
rings a PSTN phone number. The
Same here , I was beginning to think that no patterns are matched in calling
number transformations - but I tested with a pattern of ! and a mask of 12345
and that works.
So it would appear that there is a mismatch between \+1480.! and the calling
number, which does seem odd as if you leave it
The only issue with this is you don't know if the calling party is Subscriber,
National, or International, so you can't use XXX because if BR2 or BR1
calls HQ3 the From number would only show the first 7 digits.
On Oct 1, 2010, at 11:21 AM, sisiaji wrote:
> yeah, you are right, I was refer
yeah, you are right, I was referring to RP/RL transformations...
i tested it and i got the same in my lab
so i guess, as you already mentioned before, the way to do it is to actually
put Calling Party Transform Mask to be XXX on the RL (for RG member).
On Fri, Oct 1, 2010 at 7:52 PM, Mark
When doing it under Call Routing > Transformation Pattern > Calling Party
Transformation you have to use \+
When doing it on the Calling Party transform mask on a Route Pattern or Route
List you don't use \
On Oct 1, 2010, at 10:44 AM, sisiaji wrote:
> calling party transformation is done wit
calling party transformation is done without prefix \
On Fri, Oct 1, 2010 at 7:00 PM, Mark Holloway wrote:
> The crazy thing is I tried this but I couldn't get it to work.
>
> PT_HQ_CALLING_OUT assigned to CSS_HQ_CALLING_OUT assigned to CALLING Number
> Transform on the Outbound portion of t
The crazy thing is I tried this but I couldn't get it to work.
PT_HQ_CALLING_OUT assigned to CSS_HQ_CALLING_OUT assigned to CALLING Number
Transform on the Outbound portion of the HQ gateway.
Calling Party Transformation: PT_HQ_CALLING_OUT pattern is \+1480.!(replace
480 with what your HQ
Well I'm just showing the full E.164 as that's what the lab I'm looking at
looks for. However I guess you could strip the HQ area code at the gateway with
the calling party transformation.
In the real world (plan to visit that soon) then the remote destination is
likely to be a mobile phone wh
Sorry, I meant Translation Patterns, not Profiles. Still working on the From
number presentation. I'm assuming that if HQ1 calls HQ3 the PSTN phone should
show a 7 digit From number, but if BR1 calls 2003 the PSTN should show a 10
digit From number. Would you guys agree?
On Oct 1, 2010, at
Graham, same thing here.
This is a summary of what I've done to get it working correctly. I eliminated
using Translation Profiles as I didn't find them necessary for this.
Create PT_SNR which is assigned to CSS_SNR
Create a Remote Destination Profile and assign CSS_SNR to both Calling Search
Just hit the same problem in Vol2 Lab4 and I can confirm that this doesn't work
at the RP level but does work at the RL level. Is this a known bug ?
Graham
On 1 Oct 2010, at 13:35, Tam Nhu wrote:
> Hi Mark,
> The EPNM does not work at RP for SNR. Have you try to set EPNM at RL level?
>
>
If I'm following your example correctly, Mark, then you aren't hitting on
the translation pattern.
The SNR call is matching the \+1408.6347694 RP, to go out, why would it be
hitting the translation pattern? Perhaps you meant to configure this as a
Calling Party Transformation?
mike
On Fri,
Hi Mark,
The EPNM does not work at RP for SNR. Have you try to set EPNM at RL level?
TN.
___
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
I'm having a hard time when an internal extension calls another internal
extension that uses SNR, the "From" phone number on the PSTN phone is 4 digits
instead of 7. For example, extension 2001 calls 2003, and 2003 simultaneously
rings a PSTN phone number. The display on the PSTN phone says Hq
st.com] *On Behalf Of *Omotayo
> *Sent:* Tuesday, November 10, 2009 2:17 AM
> *To:* OSL Group
> *Subject:* [OSL | CCIE_Voice] Single Number Reach
>
>
>
> Hello,
>
>
> My works but i do not see "In Use Remote" when i pick from the PSTN phone.
> Also, when
dylist.com
[mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Omotayo
Sent: Tuesday, November 10, 2009 2:17 AM
To: OSL Group
Subject: [OSL | CCIE_Voice] Single Number Reach
Hello,
My works but i do not see "In Use Remote" when i pick from the PSTN
phone. Also, when i try to use mobility
Hello,
My works but i do not see "In Use Remote" when i pick from the PSTN phone.
Also, when i try to use mobility feature, i get this message "you are not a
valid mobile phone user"
Any with any idea of what could be the cause
___
For more information
37 matches
Mail list logo