Real World Globalization: 2 IDD Access Codes

IMMABE_VOICEIMMABE_VOICE
in CCIE Collaboration Technical

Hi Guys,

I encoutered this problem in a real life design I am doing and I have a TAC case open for about 1.5 weeks now, with no real solution. I was wondering if anyone here has encountered this and have a solution for it? (Not sure if this is even a possible CCIE Lab question though).

How does globalization and localization work, if the same site, has 2 different IDD access codes, and would like the option to pick which one they want to use. So this is not one of those where the 2 IDD access codes will translate to the same single IDD access code in the background.

Example Scenario below (A Singapore Call to Australia):

I would like the option to dial either 9001 or 9019 for an IDD call and actually use the IDD Access Code used.

 

The question, is after globalization, how do you localize the call so that the above scenario can be matched?

 

Normal Example (only 1 IDD Access Code for same site):

 

Phone A Dials 9001 61 4 3394 1147   -à +61 4 3394 1147 (Globalized on Ingress) à 9001 61 4  3394 1147 ( Localized on Egress) à H323 Voice Gateway à PSTN

 

 

Problem Example ( 2 IDD Access Code for Same Site)

 

Phone A Dials 9001 61 4 3394 1147   -à +61 4 3394 1147 (Globalized on Ingress) à 9001 61 4  3394 1147 ( Localized on Egress) à H323 Voice Gateway à PSTN

 

Phone A Dials 9019 61 4 3394 1147   -à +61 4 3394 1147 (Globalized on Ingress) à 9019 61 4  3394 1147 ( Localized on Egress) à H323 Voice Gateway à PSTN

 

This is the problem, because the called number has been globalized to the same e164 number, it is no longer Unique, and so how do you match it for localization.

 

The users wants the choice to be able to dial either 9001 or 9019, whenever they want. They cannot be localized to the same number.

 

Thanks Guys!

Darren

· Share on FacebookShare on Twitter

Comments

  • dougcrabbedougcrabbe

    If you want to localize the calls separately, then you need to keep the numbers separate.

    this is similar to how you would present local / national calling party numbers out of the gateway for different calls - you'd set the mask on the initial translation pattern.

    so what you could do is use the # as a differentiator.

    for most calls, you'd strip it at the initial translation pattern, but for this site and this idd call, you could leave it in:

     

    Phone A Dials 9001 61 4 3394 1147

    -> +61 4 3394 1147 (Globalized on Ingress)

    -> 9001 61 4 3394 1147 ( Localized on Egress)

    -> H323 Voice Gateway -> PSTN

     

    Phone A Dials 9019 61 4 3394 1147

    -> +61 4 3394 1147# (Globalized on Ingress)

    -> 9019 61 4 3394 1147 ( Localized on Egress)

    -> H323 Voice Gateway-> PSTN

     

    so for all sites where this isn't needed, the transformation pattern on the gateway simply strips pre-dot-trailing-# and adds in the access code.

    for the sites / gateways where this is needed, there are 2 transforms:

     

    one without a # that simply strips pre-dot and adds in the standard IDD

    one with a # that strips pre-dot-trailing-# and adds in the other IDD

     

    you'll need to ensure that the route pattern can deal with the optional #

    just a thought :-)

    · Share on FacebookShare on Twitter
  • Mark SnowMark Snow
    Excellent solution Doug!

    To answer your question Immabe_voice: Absolutely this is right along the type of complexity of questions that could be asked in the real lab exam!

    To pose a new one to both of you, suppose you had 3 types of IDDs possible rather than the 2 you just mentioned -- what would/could you do then to differentiate on the globalization for easy identification on the localization leg?




    Kind Regards,

    Mark Snow, CCIE #14073
    (Voice, Security)
    Instructor
    Internetwork Expert, Inc.
    INE Online Community
    INE Blog
    LinkedIn
    Toll Free: 877-224-8987
    Outside US: +1 775 826 4344

    - docendo discitur





    On Aug 23, 2011, at 6:25, dougcrabbe <[email protected]> wrote:

    If you want to localize the calls separately, then you need to keep the numbers separate.

    this is similar to how you would present local / national calling party numbers out of the gateway for different calls - you'd set the mask on the initial translation pattern.

    so what you could do is use the # as a differentiator.

    for most calls, you'd strip it at the initial translation pattern, but for this site and this idd call, you could leave it in:


    Phone A Dials 9001 61 4 3394 1147 -> +61 4 3394 1147 (Globalized on Ingress) -> 9001 61 4  3394 1147 ( Localized on Egress) -> H323 Voice Gateway -> PSTN

    Phone A Dials 9019 61 4 3394 1147 ->  +61 4 3394 1147# (Globalized on Ingress) -> 9019 61 4  3394 1147 ( Localized on Egress) -> H323 Voice Gateway-> PSTN

    so for all sites where this isn't needed, the transformation pattern on the gateway simply strips pre-dot-trailing-#  and adds in the access code.

    for the sites / gateways where this is needed, there are 2 transforms:

    one without a # that simply strips pre-dot and adds in the standard IDD

    one with a # that strips pre-dot-trailing-# and adds in the other IDD

    you'll need to ensure that the route pattern can deal with the optional #

    just a thought :-)




    INE - The Industry Leader in CCIE Preparation

    http://www.INE.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
    · Share on FacebookShare on Twitter
  • IMMABE_VOICEIMMABE_VOICE

    Hi Doug and Mark,

    Thanks so much for the reply and sorry for the delay in replying. I had been away on projects.

    Doug, I thought about using the hash as well, but gave us the thought I initially thought that it would affect my hash terminator. But after reading your reply... I realised that it actually doesn't! Thanks Doug! I was on the right track but gave up on myself too early...

    And even if the # is kept after globalization, and appears on the phone for a split second before it localizes again, I suppose it doesn't matter too much. The "placed calls" in directory only shows the localizaed number as well.

    Mark, hmmm your question to us is like a whole other level. Not too sure yet, how to differentiate the gloabalized numbers if we had more than 2 IDD access codes.. without making the display confusing to users.

    · Share on FacebookShare on Twitter
  • IMMABE_VOICEIMMABE_VOICE

    Hi Mark,

    Ok, I think I got it! ..maybe...

    Say I have 3 IDD Access Codes and calling the same number.

    1) 9001. 61 7 3333333  --Globalized--> +.61 7 3333333        ------ Lozalized ---> 9001 61 7 3333333   (Left this as number for TEHO from other sides)

    2) 9.019 61 7 3333333  --Globalized--> +.019 61 7 3333333  ------ Lozalized ---> 9019 61 7 3333333   

    3) 9.018 61 7 3333333  --Globalized--> +.018 61 7 3333333 ------ Lozalized ---> 9018 61 7 3333333

    This way, while pattern 2 and 3 will only display on the called number for a split second but very quickly show the localized number. The directory's "called Number" will display will show the called number.

    How does that sound Mark?

     

    · Share on FacebookShare on Twitter
  • Mark SnowMark Snow

    Sounds good. I like it. If it works, then it's a valid solution.

    My approach was simply going to be that if you attached a # to the end of your 2nd pattern, just attach a ## to the end of your 3rd pattern. Then, in your egress GW's CdPTPs CSS, have a CdPTP that matched with ## and strip both.

     

    Cheers,

    · Share on FacebookShare on Twitter
Sign In or Register to comment.