RSS

Translating nothing into nothing…

05 Aug

Wanna confuse a just-starting-out voice engineer quickly? Just show them voice translation rules. Seemingly simple on the surface, black magic voodoo underneath.  At least it can seem that way to someone new to voice…

The most recent dark magic I learned to perform came about on an issue I was 90% sure was a carrier issue – I like to hold out a 10% chance that the carrier actually did get it right, it’s only fair.

So a user reports that international calls to Great Britain are failing- no other international calls are failing, just those.  Now, I don’t know about your users, but mine *often* have trouble even figuring out the digits to dial to make a long distance call, so my confidence in them being able to accurately enter an international access code is low. Okay, non-existent.

So we fire up the good ole “debug isdn q931” and to my surprise the user is actually right. Surprise being the appropriate emotion since, let’s face it, that doesn’t happen everyday.  I take a capture of the call failure to Great Britain and a capture of the successful international call and conclude that the carrier must be goofing something up somewhere.

Now, I’m really not a blame-it-on-the-other-guy type of gal, but come on- the dial strings are hitting the same route pattern, sent to the same gateway, to the same dial-peer, and out the same voice port.  And only Great Britain numbers fail – thinking it’s not likely my system- seeing that there’s equal treatment to all things international on this end. I reasonably conclude the carrier switch must have some super special, surely unintentional, non-routing going on.

Arming the user with debugs, I send him on his way to confront the carrier with the proof of their Anglophobic ways. That’s when I learn I have overlooked something significant in the debugs- something the lovely carrier technician pointed out – likely with a smirk on his I-know-I’m-right face.

The q931 debugs showed the “type” for the Great Britain calls being marked with type as “International” whereas the calls for other international destinations were being marked with type of  “Unknown.”  Why is this significant?  Well, the “International” designation when received by a carrier switch causes that switch to prepend a 011 to the dialed string.  In this case, it’s extremely detrimental since 011 was already part of the digits placed on the line.

There are many ways to fix this issue, the one I liked best as you may have guessed, involves a translation pattern and was suggested by one of my brilliant coworkers.

It goes like this:

voice translation-rule 1
  rule 1 // // type any unknown plan any unknown

This rule will take anything that hits it, change any “type” to Unknown and any “plan” to Unknown.

It then needs to be added to a translation profile that will catch the called number:

voice translation-profile SET_UNKNOWN
  translate called 1

This then gets applied to the outgoing international dial peer:

dial-peer voice 10000 pots
translation-profile outgoing SET_UNKNOWN
destination-pattern 9011T
prefix 011
port 0/0/0:23

And there you have it.  Calls to the Queen Mother can now commence and users can rejoice!

In case you are still reading this and are interested in the debugs, here are some pertinent excerpts:

From the unsuccessful call (X’s added to protect calling/called parties): Note, Plan:ISDN, Type: International

Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98396
Exclusive, Channel 22
Calling Party Number i = 0x2181, ‘XXXXXX3547’
Plan:ISDN, Type:National
Called Party Number i = 0x91, ‘01144XX80212223’
Plan:ISDN, Type:International

From the successful call (X’s added to protect calling/called parties) – Note, Plan: Unknown, Type:Unknown:

Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98395
Exclusive, Channel 21
Calling Party Number i = 0x2181, ‘XXXXXX3547’
Plan:ISDN, Type:National
Called Party Number i = 0x80, ‘01133XX2087574’
Plan:Unknown, Type:Unknown

Advertisements
 
14 Comments

Posted by on 2011/08/05 in Translation Rules

 

Tags: ,

14 responses to “Translating nothing into nothing…

  1. Jeremy L. Gaddis

    2011/08/05 at 23:43

    FIRST!

     
  2. Jamie B

    2011/08/06 at 01:54

    Unless you have created a translation pattern for the spirit world – calls to the Queen Mother are unlikely to commence 🙂

     
  3. Jody Lemoine

    2011/08/06 at 07:26

    Well-written post, Amy. You definitely want to use “unknown” rather than “international” when calling the Queen Mother these days, that’s for sure. 🙂

     
  4. Marcus McCutchen (@Marcus1858)

    2011/08/06 at 08:17

    Great Post! I cracked up over the 10% part. You are far to kind! You probably made this tech’s year! I think every voice engineer has had this situation at least once, it is easy to relate to!

    Your blog will be well worth the read!
    Thanks for the laughs and informative information!

     
  5. Patrick Swackhammer (@swackhap)

    2011/08/06 at 09:30

    Well written!

     
  6. gomjabar

    2011/08/06 at 10:29

    Interesting, well-written. 😉

    Will be ringing up @Queen_UK directly.

     
  7. boondongle

    2011/08/06 at 12:31

    Awesome post. Dial plan troubleshooting is one of the last dark mysteries and your light shining on it is much appreciated.

     
  8. pilotmike

    2011/08/12 at 19:38

    Good post Amy! My first experience with this was when testing SRST after a WAN site cut to CUCM. We hit this same issue. Calls sent via MGCP had CUCM setting the value. When we took CUCM out of the loop (invoking SRST), IOS took over and had its own plans for our type field. 🙂

     
  9. Dave Holman (@CCIEVoiceGuide)

    2011/08/20 at 05:43

    Good post – this is very common when dealing with international providers (and really frustrating when it happens to you the first time).

     
  10. Josh

    2011/08/25 at 12:32

    Great post, I’m sure this will save me a huge headache some day. Quick question though, why did the GB call end up with a different Plan and Type than the other international calls?

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: