CM block CLID per call with mgcp

[alexis.katsavras]

Hi there,

The customer has the requirement of when they dial a number the CLID should be blocked but if they put a * at the front of the number the CLID should not b blocked.

We have created two route patters “9.07XXXXXXX” and “*9. 07XXXXXXX”.

For the “*9.07XXXXXXX” RP it works fine and the CLID is allowed through everything is default.

For the “9.07XXXXXXX” under “Calling Party Transformation” section I have set “Caller Line ID” and “Caller Name Presentation” to Restricted. This still lets the CLID to be presented to the outside world. If I do the same on the MGCP gateway configuration page then all calls are block. So this seems to work at the gateway leve but not at the Route Pattern level.

Have I missed something out?

Thanks in advance for any help
Alexis

[srsivara]

Hi Alexis,

As a workaround until we figure the problem out, you can mask the calling party number to a random number (say, 1234567890) on the RP “9.07XXXXXXX". Even if the calling party is not restricted, the original calling party number will not be revealed, if the RP “9.07XXXXXXX” is picked.

What version of CallManager are you running ? Are calls going out through a PRI gateway ? If so, can you run 'debug isdn q931' on the gateway and check the SETUP message ?

Check if you see something like this :

Outbound PRI SETUP message to 10.110.0.12 at timestamp 10/29/2009
10:41:30.979
SETUP, pd = 8, callref = 0x0004, Message Size = 40 bytes
Sending Complete
Bearer Capability i = 0x8090A3, ITU-T standard, Speech, Circuit mode, 64k,
A-law
Channel ID i = 0xA9839F - PRI interface, Exclusive channel 31
Calling Party Number i = '511111' - Plan: Unknown, Type: Unknown,
Presentation Restricted, User-provided, verified and passed
Called Party Number i = '12351285112' - Plan: Unknown, Type: Unknown

- Sriram

Please rate helpful posts !

[JAMES WEST]

Hi Sriram,

My colleague is out of the office just now, but here are the answer -

• CUCM Version 7.x.x (no access to CUCM just now )
• MGCP gateway with local break out
• Debug ISDN Q931 below -

MBH-ROUTERV1#

Jan 25 16:23:18.456: ISDN Se0/0/0:15  Q931: RX <- ALERTING pd = 8  callref = 0xA0

E7

Jan 25 16:23:18.904: ISDN Se0/0/0:15  Q931: TX -> DISCONNECT pd = 8  callref = 0x

209C

        Cause i = 0x8490 - Normal  call clearing

Jan 25 16:23:19.052: ISDN Se0/0/0:15  Q931: RX <- RELEASE pd = 8  callref = 0xA09

C

Jan 25 16:23:19.104: ISDN Se0/0/0:15  Q931: TX -> RELEASE_COMP pd = 8  callref =

0x209C

Jan 25 16:23:19.336: ISDN Se0/0/0:15  Q931: RX <- ALERTING pd = 8  callref = 0xA0

E8

Jan 25 16:23:19.356: ISDN Se0/0/0:15  Q931: RX <- CONNECT pd = 8  callref = 0xA0E

8

Jan 25 16:23:19.360: ISDN Se0/0/0:15  Q931: TX -> CONNECT_ACK pd = 8  callref = 0

x20E8

Jan 25 16:23:19.816: ISDN Se0/0/0:15  Q931: RX <- CONNECT pd = 8  callref = 0xA0E

7

Jan 25 16:23:19.820: ISDN Se0/0/0:15  Q931: TX -> CONNECT_ACK pd = 8  callref = 0

x20E7

Jan 25 16:23:21.248: ISDN Se0/0/0:15  Q931: TX -> SETUP pd = 8  callref = 0x20E9

        Sending  Complete

        Bearer Capability i =  0x8090A3

                Standard =  CCITT

                Transfer Capability  = Speech

                Transfer Mode =  Circuit

                Transfer Rate = 64  kbit/s

        Channel ID i =  0xA9839C

                Exclusive, Channel  28

        Calling Party Number i =  0x0081, '442078340182'

                Plan:Unknown,  Type:Unknown

        Called Party Number i =  0x80, '07747861718'

                Plan:Unknown,  Type:Unknown

Jan 25 16:23:21.424: ISDN Se0/0/0:15  Q931: RX <- CALL_PROC pd = 8  callref = 0xA

0E9

        Channel ID i =  0xA9839C

                Exclusive, Channel  28

Jan 25 16:23:26.180: ISDN Se0/0/0:15  Q931: RX <- ALERTING pd = 8  callref = 0xA0

E9

        Progress Ind i = 0x8488 - In-band info or appropriate  now available

Jan 25 16:23:28.440: ISDN Se0/0/1:15  Q931: TX -> DISCONNECT pd = 8  callref = 0x

047C

        Cause i = 0x8090 - Normal  call clearing

Jan 25 16:23:28.588: ISDN Se0/0/1:15  Q931: RX <- RELEASE pd = 8  callref = 0x847

C

Jan 25 16:23:28.604: ISDN Se0/0/1:15  Q931: TX -> RELEASE_COMP pd = 8  callref =

0x047C

MBH-ROUTERV1#

Thanks,

James

[alexis.katsavras]

Hi Sriram

Hope all the info provided by James is what you were looking for. If not let me know

Unfortunately changing the calling party number to a nonexistent number doesn’t really help. If the number you present to the outside world is not within your allocated DDI range the TELCO will replace the number with the main ISDN number

On a side note how do you get the SETUP message to display “Presentation Restricted”? When I do it is always in HEX

Thanks

Alexis

[srsivara]

Can you do the following ?

- Set the 'Cisco CallManager' traces to detailed on ALL servers :
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml#calm

1. Set the Calling party settings to 'Restricted' and make a call

2. Set the 'Restricted' setting on the gateway, and make a call

Get me the 'debug isdn q931' information for both calls, along with the 'Cisco CallManager' traces from ALL severs.

Please make a note of the following for both calls :
- Calling party
- Called party
- Time stamp of the call
- Whether calling party info was displayed on the called number, or not

- Sriram

[alexis.katsavras]

Hi there,

just to say that this has been resolved. Reset the RP, RL and RG. If that dosent work the no mgcp and mgcp on the gateway

alexis

[srsivara · Accepted solution]

Hi Alexis,

Good to know that the problem has been resolved ! Can you please mark the question answered, for sake of completeness ?

Thanks,

Sriram