Call Manager Express & Outgoing Calliing Line ID Per Set

[Mike Shoop]

Objective:

I need to be able to send out unique calling line ID's per telephone vs. a single CLID mask which is currently being sent by the carrier.

I know that I can have the carrier pass on whatever we send as CLID - that part is not the problem.

And I know that in our very large CUCM we can set the 'External Mask' on the DN definition of the 'Device/Phone' to be what we want it to be - this is what I'd like to be able to do on the Call Manager Express.

But I don't know how to specify the outgoing CLID for each individual set in a Call Manager "Express". 

If the solution to this is a Dial Peer I'd sure like to see an example.

Background:

I have a Call Manager Express (CME) with a single PRI circuit and approximately 40 DID numbers which supports two medical practices, Cardiac and Neuro specialists.

Currently a single CLID is sent out (by the carrier) for all outbound calls on the single PRI.  This causes confusion as patients receiving the calls from the Neuro practice return calls to the CLID they received which happens to be the main number of the Cardiac practice.

Requirement:

I need the Neuro practice to be able to send out their own DID number as their CLID, and the Cardiac practice to be able to send out their own DID number as their CLID. (Approximately 6 phones would have outgoing CLID 'A', and 6 phones would have outgoing CLID 'B')

Very grateful for any assistance you could provide, and wishing a Great New Year to you All!!

[Ryan Huff · Accepted solution]

If your PSTN DIDs are in a range (and you are using 4 digit ephone-dn extensions), which is fairly typical for CCME; voice translations are the first thing that come to mind.

Here is an example:

DID Range: 470-200-1500 thru 470-200-1599

voice translation-rule 100
  rule 1 /^15/ /47020015/

!
voice translation-profile senddid
 translate calling 100

!
dial-peer voice 100 pots
  description IN-LATA
  destination-pattern 9470[2-9]......
  translation-profile outgoing senddid
  port 1/0/1:23
  forward-digits 10

!

If you are using TDM technology (PRI) most carriers will pass your CLID, so long as the CLID is native to the PRI. Carrier's can pass non-native CLID but often times will replace non-native CLID with the billing number of the PRI (often times the phone number given to the carrier, by the customer, during trunk provisioning) for PSAP (911) routing purposes.

SIP provider's on the other hand, will generally pass anything you want as they typically do not provide PSAP routing service (911).

If your DIDs are not in a range (or are in several ranges), voice translation rules may prove a little more difficult to use; you can have up to 15 rule items per rule inline with IOS (excludes newer router platforms that have the ability to host voice translations in text files in flash).

If you can give me the range of your DIDs, specify the ephone-dn extension length used and the router platform/code level; I might be able to come up with something a little more tailored to your needs.

If you'd like to know more about voice translation rules please visit: http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml

Also a good resource: https://supportforums.cisco.com/document/31816/custom-made-guide-translation-rulesprofiles-and-some-common-uses

Thanks,

Ryan

(: ... Please rate helpful posts ... :)

[Mike Shoop]

Thank you Ryan, this is an excellent and extremely clear response! I would definitely like to send you a couple of examples.

1. CLID  6158556232 should be sent for the following ephones

6232 Front Desk

6234 Tracy (Nurse)

6235 Dr. Valentino

CLID 6158515551 should be sent for the following ephones

3470 Front Desk

3475 Tina (Nurse)

3476 Jessica (Nurse)

3474 Dr Wines

Very grateful for the quick and knowledgeable response!

Mike Shoop

[Ryan Huff · Accepted solution]

Hello Mike,

Are you looking to translate the calling party of each of these seven DIDs to their individual 10 digit format or do you want 6158556232 as the CLID for the first three extensions and 6158515551 as the CLID for the last four extensions?

If I'm reading you right you'll want the latter, so it would look like:

voice translation-rule 5555
    rule 1 /623[245]/ /6158556232/
    rule 2 /347[0456]/ /6158515551/
!

voice translation-profile senddid
    translate calling 5555
!

You would invoke this on the outbound dial-peer(s) using, translation-profile outgoing senddid.

Thanks,

Ryan

(: ... Please rate helpful posts ... :)

[Mike Shoop]

OK, many thanks, I get it, just want to confirm that on each of the outbound dial peers I need to add the line: translation-profile outgoing senddid.

This is extremely helpful. thanks again, it will be later this afternoon and I'll let you know if this works.

[Ryan Huff]

Mike,

You would do this on whichever outbound dial-peers (carrier facing) that you wish the calling party mask to be changed on (the dial-peer is where transformations like these are made) and that these extensions are using.

You can verify the transform is working (or at least being sent to the carrier correctly) by reviewing the q931 messages after the outgoing translation-profile has been applied.

Thanks,

Ryan

[Mike Shoop]

OK Ryan, back now from the New Year's break - I am pasting in below the actual translation rules which were already in place.

See Rule 3 and voice translation-profile caller-id. There were already in place.

Then see the two Dial Peers dial-peer voice 2 pots and dial-peer voice 3 pots: I added the statement to invoke the translation rule #3 in each of the dial peers.

There was no statement in the dial peers re translation rules so I think that is what the problem is/was. I'll let you know tomorrow if this works. very grateful for  your help.

[Ryan Huff]

Mike,

While I don't see the text you are referencing, it sounds like you may have it sorted out. I appreciate your willingness to complete the lifecycle of this thread; that helps this community continue to be a valuable resource!

I am excited to hear if it works! Please let me know if I can be of any assistance in the future!

Thanks,

Ryan

[Mike Shoop]

Sorry I left out the txt. Here's what it looks like right now: I think the dial-peer statement is a little different that what you suggested but it's the only way I could get it to work.

Disregard Voice-Translation Rules 1 & 2.

Notice Translation-Rule 3, Rule 1 - this looks to me like it sending out 6158515551 for any 4 digit extension ("^..../")

I added Rule 3 thru 11, and instead of the current Rule 1 I need it to send out 6158515551 for any 34XX extension. So I think that rule needs to be edited. Right???

voice translation-rule 1
 rule 1 /^\(615855\)\(....\)/ /\2/
 rule 2 /^\(6158515551\)/ /3470/
 rule 3 /^\(615543\)\(....\)/ /\2/
!
voice translation-rule 2
 rule 1 /^\(9\)\(.......\)/ /8\2/
 rule 2 /^\(91\)\(..........\)/ /81\2/
!
voice translation-rule 3
 rule 1 /^..../ /6158515551/
 rule 2 /^6222/ /6158556222/
 rule 3 /^6233/ /6158556233/
 rule 4 /^6232/ /6158556232/
 rule 5 /^6234/ /6158556232/
 rule 6 /^6220/ /6158515551/
 rule 7 /^6225/ /6158515551/
 rule 8 /^6235/ /6158556232/
 rule 9 /^6230/ /6158515551/
 rule 10 /^6223/ /6158515551/
 rule 11 /^6221/ /6158515551/
!

voice translation-profile DID
 translate called 1
!
voice translation-profile TNS
 translate called 2
!
voice translation-profile caller-id
 translate calling 3
!

dial-peer voice 2 pots
 corlist outgoing local
 description Local Dial Peer
 destination-pattern 9615.......$
 translation-profile outgoing caller-id
 port 0/0/0:23
 forward-digits 10
!
dial-peer voice 3 pots
 corlist outgoing LD
 description LD Dial Peer
 destination-pattern 91[2-9]..[2-9]......$
 translation-profile outgoing caller-id
 port 0/0/0:23
 forward-digits 11

You're right - the Support Community is an incredibly valuable resource.  Very grateful for the help!

[Ryan Huff]

Hello Mike,

In your example, voice-translation 3 is in essence, doing the same thing as the example I provided. My example was in 'short-hand' whereas this example would be in what I'd call, 'expanded-form'. In addition, your example is performing transforms for 4 digit numbers my example is not.

If you recall earlier in the thread, we talked about voice translations like these having a limit of 15 items per rule; usually you would try to pack as much capability into one rule item as possible.

Applied; in your example, each rule item in voice translation 3 is performing a 1:1 match whereas in my example, each rule item could match more than one possibility. For example, /623[245]/ would match 6232, 6234 and 6235. In other words, one rule item to match 3 different numbers versus three rule items to match 3 different numbers.

EXAMPLE: /^623[245]/ or /623[245]/ (depends on how your ephone-dns look) could take the place of rule items 4, 5 & 8 in your example.

Ultimately both methods work just fine, one just uses advanced regular expressions to help conserve precious space in the voice translation rule. If you don't need more than 15 translations and don't need to plan for growth then no sense bothering with it, I would leave it as is.

Glad to hear it is working! Good job!

Thanks,

Ryan

[Mike Shoop]

Ryan - I've tried to back out every change I have made ,  Ultimately it did not work as far as the CLID on the outgoing calls (note that voice port 0/0/0:23 is used for the outgoing - I wondered if maybe the translation profile needs to be assigned to it.??

Mainly though, this is a Medical (Cardiac) Practice and now the main number 615 851 5551 no longer rings to the front desk x3470. This number 615 851 5551 is an incoming DID number on the 0/0/0 PRI. Can you please take a look at the info below and see if you see anything I may have accidentally 'broken' lilke maybe a translation rule for the incoming, etc. I can send the entire config if that will help. Right now they're not getting any inbound 615 851 5551 calls to extension 3470.

The other inbound calls seem to be working properly and outbound is also working properly.

Once I get the front desk ringing again, I'll then go back to the outgoing clid issue.

thanks, Mike Shoop

voice translation-rule 1

rule 1 /^\(615855\)\(....\)/ /\2/

rule 2 /^\(6158515551\)/ /3470/

rule 3 /^\(615543\)\(....\)/ /\2/

!

voice translation-rule 2

rule 1 /^\(9\)\(.......\)/ /8\2/

rule 2 /^\(91\)\(..........\)/ /81\2/

!

voice translation-rule 3

rule 1 /^..../ /6158515551/

rule 2 /^6222/ /6158556222/

rule 3 /^6233/ /6158556233/

!

!

voice translation-profile DID

translate called 1

!

voice translation-profile TNS

translate called 2

!

voice translation-profile caller-id

translate calling 3

!

dial-peer voice 2 pots

corlist outgoing local

description Local Dial Peer

destination-pattern 9615.......$

port 0/0/0:23

forward-digits 10

!

dial-peer voice 3 pots

corlist outgoing LD

description LD Dial Peer

destination-pattern 91[2-9]..[2-9]......$

port 0/0/0:23

forward-digits 11

dial-peer voice 9962322 pots

corlist outgoing local

destination-pattern 8615.......$

port 0/1/1

forward-digits 10

!

dial-peer voice 9962323 pots

corlist outgoing LD

destination-pattern 81(2-9).........$

port 0/1/1

forward-digits 11

!

dial-peer voice 9962324 pots

corlist outgoing local

destination-pattern 8615.......$

port 0/1/0

forward-digits 10

!

dial-peer voice 9962325 pots

corlist outgoing LD

destination-pattern 81(2-9).........$

port 0/1/0

forward-digits 11

!

dial-peer voice 9962326 pots

corlist outgoing local

destination-pattern 8615.......$

port 0/3/0

forward-digits 10

!

dial-peer voice 9962327 pots

corlist outgoing LD

destination-pattern 81(2-9).........$

port 0/3/0

forward-digits 11

!

dial-peer voice 9962328 pots

corlist outgoing local

destination-pattern 8615.......$

port 0/3/0

forward-digits 10

!

MAIN NUMBER – 615 851 5551 SHOULD BE RINGING TO THIS DN

ephone-dn 1 octo-line

number 3470 secondary 0

pickup-group 1

label Front Desk 3470

description Front Desk 3470

name Front Desk 3470

call-forward night-service 918004076753

corlist incoming Gville-1

night-service bell

!

www.ascension.org

Mike Shoop Regional Telecommunications Engineer Ascension Information Services and National Telecommunications Service Line Ofc 615-494-3095 mike.shoop@ascensionhealth.org

[Ryan Huff]

Regarding the main number (615-851-5551) not ringing to extension 3470, I'd need to see the q931 and the dial-peer debugs. Based on the config section you provided, it does look like you would need "translation-profile incoming DID" on the inbound dial peers.

Although in your example, there are no inbound dial-peers shown, which in and of itself, could be your issue but I'll assume you have inbound dial-peers and just didn't paste them?

Regarding the outgoing caller-id; yes you would need "translation-profile outgoing caller-id" on whatever dial-peers the calls are going out of. So, if these extensions are going out of the dial-peers that point to 0/0/0:23, then that dial-peer would need "translation-profile outgoing caller-id".

[Mike Shoop]

Thanks Ryan, I'm attaching the config, and I'll be debugging the PRI to see what's up. Much appreciate your support.

[Mike Shoop]

here's the debug output on my call to 6158515551 from my desk 6154943095

WAN-GOODLETTSVILLE-RTR#
Jan  5 12:07:56: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref = 0x1F2D
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Facility i = 0x9F8B0100A117020118020100800F53542054484F4D4153205255544845
                Protocol Profile =  Networking Extensions
                0xA117020118020100800F53542054484F4D4153205255544845
                Component = Invoke component
                        Invoke Id = 24
                        Operation = CallingName
                                Name Presentation Allowed Extended
                                Name = ST THOMAS RUTHE
        Display i = 'ST THOMAS RUTHE'
        Calling Party Number i = 0x2180, '6154943095'
                Plan:ISDN, Type:National
        Called Party Number i = 0xA1, '6158515551'
                Plan:ISDN, Type:National
Jan  5 12:07:56: ISDN Se0/0/0:23 Q931: Received SETUP  callref = 0x9F2D callID = 0x1EAE switch = primary-ni interface = User
Jan  5 12:07:57: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x9F2D
        Channel ID i = 0xA98381
                Exclusive, Channel 1
Jan  5 12:07:57: ISDN Se0/0/0:23 Q931: TX -> ALERTING pd = 8  callref = 0x9F2D
        Progress Ind i = 0x8188 - In-band info or appropriate now available
WAN-GOODLETTSVILLE-RTR#
WAN-GOODLETTSVILLE-RTR#

[Ryan Huff]

Can you also show the output of "debug voip ccapi inout" for a test call?

Thanks,

Ryan