X11 services transformation

[John C. Reid]

I am using Skyetel for my trunking. Obviously if I send them 211 for Community services, 311 for Municipal government services, 411 for information services, etc. they don't know how to route it.

My question is, how do I go about doing the number transformation so if the user enters 211 it is given to Skyetell as 18552117822 so that it can be properly routed? The Outbound Routes and Trunks dial patterns don't seem to handle that. Also, is it better to do these transformations on the outbound route or the trunk?

Thank you.

 

[Halea]

My question is, how do I go about doing the number transformation so if the user enters 211 it is given to Skyetell as 18552117822 so that it can be properly routed? The Outbound Routes and Trunks dial patterns don't seem to handle that. Also, is it better to do these transformations on the outbound route or the trunk?
Thank you.

Check your feature code admin page and if they are defined there then start by changing those numbers to something else (that you actually won't use) or if your software version allows then disable them.
As a result 211, 311, 411, etc. will become free and available so that you can use them any way you want.
If they are not in "feature codes" they may be in custom destinations or extensions.
Again, once they are no longer defined in those special places they become regular numbers that you can use with outbound or trunk intercepts.

I tend to do any user oriented transformation on the outbound route, anything that relates to the upstream trunk (like for instance choice of route quality, etc.) on the trunk definition page.
For the double-one numbers I use the outbound routes.

 

[John C. Reid]

Ok, but how? I can prepend digits, and I can look for prefixes, but how do I get from 211 to 18552117822? I mean in that example if I was able to prepend and postpend I could add 1855 + 211 + 7822, but I don't know how to add the trailing 7822 digits. Aside from that there is no guarantee that the number I have to transform to will have the original number in it as a root.

 

[Halea]

Ok, but how? I can prepend digits, and I can look for prefixes, but how do I get from 211 to 18552117822? I mean in that example if I was able to prepend and postpend I could add 1855 + 211 + 7822, but I don't know how to add the trailing 7822 digits. Aside from that there is no guarantee that the number I have to transform to will have the original number in it as a root.

Oh ok!

In the above example when you dial 932 (WEA for WEATHER), the dialed number 932 is intercepted and removed, and it is replaced with 16319240517 (the last 2 digits do not show as the box is not large enough, but they are there) in the "outbound routes".
In your case you will put 211 where 932 is. And replace 16319240517 with 18552117822. You can add your other 11 numbers in additional entries.

 

[kenn10]

Like this:

You can probably add in 311 and any others like this on the same route by adding them to the dial patterns page.

 

[John C. Reid]

So you just leave the [match pattern] section completely blank?? That is not very intuitive, but I can see how we get there.

Thank you.

EDIT: I just tried that. I get an "all circuits are busy now"

EDIT 2: Nevermind, it worked.

 

[Halea]

Yes, and that works!

 

[Halea]

Do you also get the same message when you dial the full number as opposed to the abbreviated one?
Make sure that you don't have any spaces etc. leading or trailing in those boxes.

 

[Halea]

Also try the number that I gave you as an example. It should work. It's possible that your trunk doesn't take the number that you're trying to dial as 211 for some reason. (Geographic/Regional limitations etc.)

 

[John C. Reid]

I had the page open for too long and it didn't take. When I opened it again to check it had not saved. It worked, I am now in the process of trying to look up useable numbers for all of the x11 services.

Fortunately 711 for TDD worked with no modifications needed. I am hoping 911 will to, but I am not going to call it to test.