cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6596
Views
60
Helpful
15
Replies

translation pattern not working

eicc30000
Level 1
Level 1

call manager 7 and 2821, they speak mgcp

i can make calls out the bri.

i have translation pattern for isdn calls on incoming called number to be forwarded to the receptionest extension.

but im getting a busy signal and the following on the debug isdn q931

*Jan 1 13:01:12.384: ISDN BR0/0/0 Q931: RX <- SETUP pd = 8  callref = 0x03
Sending Complete
Bearer Capability i = 0x8090A3
  Standard = CCITT
  Transfer Capability = Speech 
  Transfer Mode = Circuit
  Transfer Rate = 64 kbit/s
Channel ID i = 0x89
  Exclusive, B1
Calling Party Number i = 0x0083, '054xxxxxx'
  Plan:Unknown, Type:Unknown
Called Party Number i = 0xC1, '404xxxx'
  Plan:ISDN, Type:Subscriber(local)
*Jan 18 13:01:12.396: ISDN BR0/0/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x83
Cause i = 0x8081 - Unallocated/unassigned number

im obviously getting the called party number, and it matches my translation pattern. but the call is not forwarded to called party transformation i have set in the translation pattern...

Any Ideas?

Thanks

Glen

2 Accepted Solutions

Accepted Solutions

can you check the inbound CSS on the MGCP endpoint? (also check the number of digits to match)

the partition of the TP should be in this CSS.

Also, the CSS on the TP should have the partition of the reception number

View solution in original post

no worries,

DNA is the dialed number analyser, you put in the number and css and it should tell you the path the call travels. its under tools in serviceability (you have to enable the service if it doesn't appear)

Yes the CTI routepoint should only be hit if your translation pattern doesn't snap it up, im thinking that the number is incorrect before this so setting up a route point with the full PSTN number will tell us if  the called number is still intact. This will actually meet your goal but we would rather get to the bottom of the translation issue than hack a fix in.

can you list the settings for inbound calls on the MGCP gateway endpoint, im interested mostly in the significant digits field.

I am presuming that the CSS for the MGCP gateway is still and the tp partition is also ?

View solution in original post

15 Replies 15

phooghen
Cisco Employee
Cisco Employee

You can probably check the MGCP GW Calling Search Space.

Does this CSS include the partition of the Translation Pattern number ?

Pierre.

^ +1

also, just to make sure I havn't missed something you are talking about, and only about transformation patterns? not translation patterns?

... its confusing the cr@p out of me reading the two being used interchangeably

dont be confused!  im using a translation pattern, to transform the called number from the actual pstn number i see on the debug q931 (when making an incoming call) TO the receptionist extension, say 1000.

i guess the two terms may be used interchangeably, but anyway im using Call Routing --> Translation pattern, not transformation

can you check the inbound CSS on the MGCP endpoint? (also check the number of digits to match)

the partition of the TP should be in this CSS.

Also, the CSS on the TP should have the partition of the reception number

no worries,

DNA is the dialed number analyser, you put in the number and css and it should tell you the path the call travels. its under tools in serviceability (you have to enable the service if it doesn't appear)

Yes the CTI routepoint should only be hit if your translation pattern doesn't snap it up, im thinking that the number is incorrect before this so setting up a route point with the full PSTN number will tell us if  the called number is still intact. This will actually meet your goal but we would rather get to the bottom of the translation issue than hack a fix in.

can you list the settings for inbound calls on the MGCP gateway endpoint, im interested mostly in the significant digits field.

I am presuming that the CSS for the MGCP gateway is still and the tp partition is also ?

The call flow and CSS Parition will be like this

PSTN -----> PRI ---- >MGCP GW (CSS:P1) -----> TP[Partition:P1](Full DID) ---> Translate Called Number to Receptionist on TP [CSS:Receptionist]----> Receptionist[PT:Receptionist]

CSS: Calling Rights

PT: Paritions , A person trying to call an Entity in a PT should have that PT in his CSS(Calling Rights)

Hope that makes sense

PS: Rate Useful posts

Tobin

im not using any partitions for endpoints (phones or GWs) or translation patterns at the moment. for now im only using partitions for route patterns to control phones privileges.

significant digits is on the default setting, i guess (All). did not change that feild.

I did not get a chance to test DNA today, ill do it tomorrow. and let you know.

Thank you very much

Glen

Thank you very much tobin. it turned out significant digits were mistakenly set to 0, put it back to All, worked just fine!

thanks for pointing it out, and other stuff were also useful ... DNA is cool ! lol

im wondering though if theres a way to tracing/logging to see where mgcp gets stuck. i mean instead of guessing and checking all configurations from scratch!

thanks everyone you rock, this forum is the best

Regards,

Glen

Hi,

debug isdn q931 is your friend for MGCP PRI

Regards,

Divin

eicc30000
Level 1
Level 1

my GW is on the none css, so is my translation pattern partition.

im wondering if it has anything to do with BRI and MGCP, i hear they dont work well together!

ahh,

If I am hearing you correctly you are trying to use a 'translation pattern' for inbound calls from the gateway. I presume you have run the dialed number analyser to check if its all ship shape?

As already pointed by Tobin, if you use MGCP, you have to configure a translation pattern on the Callmanager.

If you use H.323, you have to configure a translation-profile on the dial-peer.

sorry I think I am with you now, can you

a)check the tranlation pattern again and make sure its being hit using the DNA

b)test it by creating a cti route point with the full number and forward all to the number you want the call to end up at (if this works then your right its not hitting the tp at all)

Tobin

exactly! this is what im afraid of, I think my translation pattern is not even being hit. it would be great if i could start some traces to see if its being hit or not, could you please elaborate :

"a)check the tranlation pattern again and make sure its being hit using the DNA"

What is DNA?

"

b)test it by creating a cti route point with the full number and forward all to the number you want the call to end up at (if this works then your right its not hitting the tp at all)

"

so i give my CTI DN the actual full called number? and forward to the receptionist extension? ... now if this works you say my tp is not working, does this mean tp is executed before RP's? woudlnt this create a conflict in my Dial plan?

sorry i know too many questions.

appreciate your response, i think this is the best way to troubleshoot this... ill try what you suggested tomorrow and see what happens!

thanks

Glen