atcomsystems.ca/forum
Posted By: compu_85 trans.txt questions - 06/19/14 10:40 PM
My FXII / interchange has several mailboxes configured for announcements. I have a PRI with a block of numbers, and use the DID translation table to send them to a virtual extension with the box number.

Frequently the box will play the "I'm sorry that's not a valid entry" message. I did some looking with the trace feature and found that one of the entries was adding a * to the end of the string.

Here's the original rule:
B@#xxx#=xxx,*,*:caller=@
I modified it to:
B@#xxx#=xxx,*:caller=@

I guess I'm trying to understand the way the system passes numbers to the VM. When I call the main number (DID translates to 200) I see this in the trace (where nnnn are the last 4 of my phone number):
TRANSLATION try: [A@##] [a703898nnnn##] (OK)

If I call one of the other numbers (in this case one where the DID translates to 186), I see this:
TRANSLATION try: [B@#xxx#] [b703898nnnn#186#] (OK)

It looks like the first character is a reason code? Am I wrong in modifying the line in trans.txt to not append a "*"?

Thanks,

-Jason
Posted By: 5years&counting Re: trans.txt questions - 06/20/14 05:50 AM
It depends on the mailbox, if I remember correctly. The *,* is for two things. The first * bypasses the transfer ("Please hold while I transfer your call to..."). The second * squelches the "You may transfer the call now" prompt. If the mailbox is set to No Transfer, I'm guessing you are running into the second * being extraneous.

Anytime I wrote custom translations in the trans.txt, I would always do so for A@, B@, and C@, and oftentimes also X=Y (X and Y being the custom digits and translation).

Justin
Posted By: compu_85 Re: trans.txt questions - 06/20/14 01:16 PM
I've noticed this happen more when the call is DID'd to a routing box.
Posted By: 5years&counting Re: trans.txt questions - 06/20/14 02:31 PM
There's an explanation in the I&M manual for what each one (A, B, C) is.

Justin
Posted By: 5years&counting Re: trans.txt questions - 06/20/14 02:33 PM
That would make more sense. You should build a set of custom translations for those. Routing boxes have * defined differently than mailboxes.

Justin
Posted By: compu_85 Re: trans.txt questions - 02/26/16 06:51 PM
Originally Posted by 5years&counting
There's an explanation in the I&M manual for what each one (A, B, C) is.

Justin

So I'm trying to find this in the I&M manual. I'm looking at one from 4/00, and I don't seew what A B and C are for the reason codes. I'm presuming these are generated by the PBX? I don't see them in the Voicemail Integration Digits setup.

Specifically, I'm trying to understand this section:

;Caller-id info
A@#xxxx#=xxxx,*,*:caller=@
B@#xxxx#=xxxx,*,*:caller=@
C@#xxxx#=xxxx,*,*:caller=@

A previous installer set up a rule to send calls from hunt group 5700 to extension 1004's mailbox:

A@#5700#=1004,*,*:caller=@
B@#5700#=1004,*,*:caller=@
C@#5700#=1004,*,*:caller=@

In a few months I'll need to modify this due to staffing changes. My initial throught was to get rid of that translation and use the voicemail's recording routing to do it instead. But I'd like to understand that translation before I remove it.

Thanks,
Posted By: 5years&counting Re: trans.txt questions - 03/22/16 06:23 AM
I always wrote translations for the basic and the A,B,C translation rules. If I remember correctly, they are specific to the type of call (internal, external, etc.) It's in the documentation somewhere, or in a tech bulletin.

Justin
© Sundance Business VOIP Telephone Help