EMP & Lightning Home Surge Protection
EMP - Click Here!
Phone.com 300x250
300x250 Your Business Phone Service in the Cloud
Global Test Supply
defencebyte.com
Antiransomware
Linked Banner to your Product or Website
Meticore Weight Loss Voted #1.
Daily Excellence
Previous Thread
Next Thread
Print Thread
Rate Thread
#573430 06/19/14 10:40 PM
Joined: Feb 2008
Posts: 124
Member
OP Offline
Member
Joined: Feb 2008
Posts: 124
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:
[email protected]#xxx#=xxx,*,*:[email protected]
I modified it to:
[email protected]#xxx#=xxx,*:[email protected]

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: [[email protected]##] [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: [[email protected]#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

Last edited by compu_85; 06/19/14 10:51 PM.

Jason Perkins
Network Engineer
Global Test Supply 728x90
Joined: Jun 2004
Posts: 4,548
Moderator-Comdial, ESI, Voicemail, Cisco
Offline
Moderator-Comdial, ESI, Voicemail, Cisco
Joined: Jun 2004
Posts: 4,548
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 [email protected], [email protected], and [email protected], and oftentimes also X=Y (X and Y being the custom digits and translation).

Justin

Joined: Feb 2008
Posts: 124
Member
OP Offline
Member
Joined: Feb 2008
Posts: 124
I've noticed this happen more when the call is DID'd to a routing box.


Jason Perkins
Network Engineer
Joined: Jun 2004
Posts: 4,548
Moderator-Comdial, ESI, Voicemail, Cisco
Offline
Moderator-Comdial, ESI, Voicemail, Cisco
Joined: Jun 2004
Posts: 4,548
There's an explanation in the I&M manual for what each one (A, B, C) is.

Justin

Joined: Jun 2004
Posts: 4,548
Moderator-Comdial, ESI, Voicemail, Cisco
Offline
Moderator-Comdial, ESI, Voicemail, Cisco
Joined: Jun 2004
Posts: 4,548
That would make more sense. You should build a set of custom translations for those. Routing boxes have * defined differently than mailboxes.

Justin

Joined: Feb 2008
Posts: 124
Member
OP Offline
Member
Joined: Feb 2008
Posts: 124
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
[email protected]#xxxx#=xxxx,*,*:[email protected]
[email protected]#xxxx#=xxxx,*,*:[email protected]
[email protected]#xxxx#=xxxx,*,*:[email protected]

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

[email protected]#5700#=1004,*,*:[email protected]
[email protected]#5700#=1004,*,*:[email protected]
[email protected]#5700#=1004,*,*:[email protected]

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,


Jason Perkins
Network Engineer
Joined: Jun 2004
Posts: 4,548
Moderator-Comdial, ESI, Voicemail, Cisco
Offline
Moderator-Comdial, ESI, Voicemail, Cisco
Joined: Jun 2004
Posts: 4,548
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


Link Copied to Clipboard
Advertising Sponsor
Popular Topics (Views)
Forum Statistics
Forums94
Topics94,457
Posts640,016
Members49,481
Most Online5,661
May 23rd, 2018
Today's Birthdays
docjim, eddycurrent, FC de Argentina, matts520, NetworkKing, Randy from RACE, Zyeith
Newest Members
Goracing57, Michael Duffy, Jim22, hummerdave, Rusenga D
49,481 Registered Users
Get Tech Support Now! Click the banner below
Get Tech Support Now!
Top Posters (30 Days)
dexman 33
Ruben 9
OBT 5
NordVPN
Advertising Sponsor Spot 2
EMP Shield for Commercial - Home & Vehicle
Use Coupon code SAVE - Click Here!
Who's Online Now
16 members (EV607797, justbill, Carl Navarro, metelcom, sundance, BrianS, mbhydro, hitechcomm, OBT, Silversam, pvj, Professor Shadow, hbiss, Keyset6, JBean3329, 1 invisible), 154 guests, and 139 robots.
Key: Admin, Global Mod, Mod
Contact Us | Telephone System Tech Support | Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers.
©Copyright Sundance Communications 1998-2021
Trusted Partners
landing page builder Antiransomware 300x250 Your Business Phone Service in the Cloud