Set Calling Party Name for FXO port?

[apu]

We have a Valcom door phone unit, connected to a 2821 via an FXO port. In turn, this FXO port is registered via MGCP to a CallManager 7.1 system.

Can we set the Calling Party Name somewhere for calls that originate on this FXO port?

Right now, the calls just come in as "Unknown Number" but it would be helpful to identify them as "Front Door," etc.

[acampbell]

Apu,

How does your FXO - door system operate.

Are you using PLAR or do you dial a number ?

Regards,
Alex.
Please rate useful posts.

[Brian Carscadden]

Check the following IOS CLI commands:

station-id name

station-id number

These are set under the FXO voice port.

Good luck,

Brian

[acampbell]

Brian,

The guy says it is MGCP registration so I reckon we only help if

it uses a PLAR translation for incomming calls

Regards,
Alex.
Please rate useful posts.

[apu]

Alex,

They have an MGCP endpoint defined with an Attendant DN.

Brian,

Small world. Hope all is well. Alex is right re: station-id name/number not working. I did try before posting just in case. (P.S. Not the client you & I share, by the way. Helping these folks with a Cisco system some other reseller provided them years ago but they were not happy with the service.)

[acampbell]

Hi,

Note down how it works just now.
Like the Attendant Dn , CSS etc.

Then try making a few changes and test.

Create a new Partion

PT-DOORPHONE

Create a new CSS

CSS-DOORPHONE
Assign the Partitions

PT-DOORPHONE

Create a new Tranlation Pattern

Just put a "." as the actual Translation Pattern
Assign to Partition PT-DOORPHONE
Description DOORPHONE TP
Calling Search Space - Select a CSS that has access
to the partition that Attendant DN resides
Calling Party Transform Mask - Use an Original number like 4444
Called Party Transform Mask - Use the Attendant DN

Go to the gateway endpoint
Remove the Attendant DN
Change the CSS to CSS-DOORPHONE

Test and hopefully you will see the call on
the Attendants phone is from 4444

Sorry I thought you could use a Name too
but there is no setting for that on CUCM7.1 TPs

If this is no use then just put back the correct CSS & Attendant DN
Delete all other stuff  too.

Regards,
Alex.
Please rate useful posts.

[apu]

Thanks, Alex.

I did dig around the translation patterns for a while. I'll have to try your new CSS approach next time I am there.

The two door phones (one per MGCP port) do answer when you call their respective extensions so I guess a call from those extensions would be better than a call from "Unknown Number." Of course, it is obviously easier to see "Front Door" and "Back Door" than to realize that x4444 is one of the two doors, especially if there are different people answering the doors.

[Brian Carscadden]

All is well Apu. Yeah those pesky Cisco partners can be fly by night hacks sometimes.

I may have a solution. Let me get a cup of coffee and log into my 7x cluster, then I'll get back to you.

Brian

Sent from Cisco Technical Support iPad App

[Brian Carscadden]

Apu,

Was going to use a hunt pilot alerting name, but unfortunately that's not supported on 7.x Alex's recommendation seems most feasible for MGCP. Otherwise switching to H323 (co-resident with MGCP) for just the FXO ports is a worthwhile option. Then you can go with the "station-id name" option.

Regards,

Brian

[Brian Carscadden]

Here's a sample snippet of a config I did for a client. Co-resident H323/MGCP. MGCP Controls their PRI, but H323 the FXO ports. Here's the H323 pieces. Two dial-peers for each door; one for each CUCM server for backup purposes.

voice-port 1/0/0

connection plar 801

station-id name FRONT DOOR

station-id number 1111

caller-id enable

!

voice-port 1/0/1

connection plar 802

station-id name BACK DOOR

station-id number 2222

caller-id enable

dial-peer voice 100 voip

destination-pattern 801

progress_ind setup enable 3

session target ipv4:10.1.1.2

codec g711ulaw

!

dial-peer voice 101 voip

destination-pattern 801

progress_ind setup enable 3

session target ipv4:10.1.1.1

codec g711ulaw

dial-peer voice 200 voip

destination-pattern 802

progress_ind setup enable 3

session target ipv4:10.1.1.2

codec g711ulaw

!

dial-peer voice 201 voip

destination-pattern 802

progress_ind setup enable 3

session target ipv4:10.1.1.1

codec g711ulaw

[apu]

Thanks, Brian.  I'll give it a try.

P.S. Definitely not the "P" client we share. This one came about because I was sitting in a public safety meeting hearing complaints about the phone system that apparently were ongoing for a year. Came back the next week and took me an hour to clear up their to-do list.