Q931 Calling Party Number

[mike_riggall]

Could someone please sanity check my working here as I am having trouble getting a CME router to present the correct calling number using ISDN-2e trunks in the UK.

In order to present the number 123456 as the calling number on an outbound call I have a dial-peer configured as follows:

dial-peer voice 60000 pots

answer-address 5532

clid network-number 123456

I have to use a dial-peer rather than configure the voice-port so that I can present different numbers depending on the extension in use.

If I debug isdn q931 I see the following output:

000852: Feb 22 11:58:49.542: ISDN BR0/1/1 Q931: TX -> SETUP pd = 8 callref = 0x46

Bearer Capability i = 0x8090A3

Standard = CCITT

Transer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0x81

Progress Ind i = 0x8183 - Origination address is non-ISDN

Calling Party Number i = 0x0080, '123456'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '01234556677'

Plan:Unknown, Type:Unknown

The calling party number is set to the number I need but the number presented at the remote phone is still the telco-provided number for the line. I have subscribed to Customer Provided CLI.

On the incoming side however something is happening as I can see following debug information:

005971: Mar 7 11:48:36.707: ISDN BR0/1/1 Q931: extract_redirect_orig_called_ie: IE type redirecting num 1234123456 reason 0 cnt 1 plan 2 type 1 pres 0

The number that I had hoped to present on an outbound call (123456) is being referenced on an inbound call.

I feel that I have asked the telco for the wrong service however I am not sure what I should have asked for. Please can anyone clarify this for me?

Many thanks for any knowledge greater than my own.

Mike

[s.jankowski]

Make sure that numbering plan and type are set in accordance with the way the device is connected to the gateway. Try this URL for checking the ISDN connectivity issues.

http://www.cisco.com/en/US/products/ps6350/products_command_reference_chapter09186a0080436a9e.html

[swaro2000]

IMO you have requested the correct circuit features from your provider. It seems your provider has dropped the ball & has not provisioned the circuit correctly as per your request. They are overriding your CLID. What is odd is that your CLID is appearing on the remote end as redirecting number which is not correct. It is should be the calling party field. They seem to be populating the wrong fields with your CLID. If they are assuming the '1234' was the orignal number that was then changed/redirected to '123456' then try using the following command

clid network-number 123456 second-number strip