Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Main outgoing number presentation

When i program my uc500 via the CCA 1.9(1) with an outgoing number for presentation it seems like it's not sending this one via the E1 port.The Bri ports are not used at this site. Is there anyone who has some experiance with this one?

is there a CLI command to present the main number to the outside world on a E1?

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

Re: Main outgoing number presentation

Yes, it is pretty evident that your PSTN provider doesn't like that four digit calling number:

Cause i = 0x82E46C - Invalid information element contents

Also, the "cptone" command doesn't really apply here. It is used for other localization purposes.

As Steven suggested, CCA 1.9.1 can be used to select calling number for outbound calls.

Marcos

6 REPLIES

Re: Main outgoing number presentation

I don't have a T1 available to test with at the moment.  Can you post screen shots of CCA for the translation rules page?  Can you also tell me what the main number for the site is?

In cca, I believe you have the option to have the main number be the site number you have configured.  It works in my SIP implementation.

Community Member

Re: Main outgoing number presentation

Ronald,

You need to make sure that you are sending the caller id in a format that your PSTN provider understands. Typically, if they see something that they don't like (or an invalid calling number that should not be coming from that trunk) they will ignore it and overwrite it. This is done to prevent calling number spoofing and toll fraud.

Capture a "debug isdn q931" and look for the calling number in the outgoing SETUP message. That will tell you what the UC500 is sending.

Thanks,

Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

Community Member

Re: Main outgoing number presentation

This is what the debug is telling us:

UC520#
Apr  1 13:36:39.507: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 00230
Apr  1 13:36:39.507: ISDN Se0/3/0:15 Q931: Sending SETUP  callref = 0x013A callID = 0x80BB switch = primary-net5 interface = User
Apr  1 13:36:39.511: ISDN Se0/3/0:15 Q931: TX -> SETUP pd = 8  callref = 0x013A
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Progress Ind i = 0x8183 - Origination address is non-ISDN
        Calling Party Number i = 0x0180, '00230'
                Plan:ISDN, Type:Unknown
        Called Party Number i = 0x81, '0610832758'
                Plan:ISDN, Type:Unknown
Apr  1 13:36:39.675: ISDN Se0/3/0:15 Q931: RX <- STATUS pd = 8  callref = 0x813A
        Cause i = 0x82E46C - Invalid information element contents
        Call State i = 0x01
Apr  1 13:36:39.679: ISDN Se0/3/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0x813A
        Channel ID i = 0xA98381
                Exclusive, Channel 1
Apr  1 13:36:41.551: ISDN Se0/3/0:15 Q931: RX <- PROGRESS pd = 8  callref = 0x813A
        Progress Ind i = 0x8282 - Destination address is non-ISDN
Apr  1 13:36:47.787: ISDN Se0/3/0:15 Q931: RX <- PROGRESS pd = 8  callref = 0x813A
        Progress Ind i = 0x8284 - Call has returned to the ISDN
Apr  1 13:36:47.827: ISDN Se0/3/0:15 Q931: RX <- ALERTING pd = 8  callref = 0x813A
        Progress Ind i = 0x8288 - In-band info or appropriate now available
Apr  1 13:36:52.239: ISDN Se0/3/0:15 Q931: RX <- CONNECT pd = 8  callref = 0x813A
        Date/Time i = 0x0904010F2617
                Date (yr-mm-dd)   = 09-04-01
                Time (hr:mnt:sec) = 15:38:23
        Connected Number i = '!', 0x83, '638532229'
Apr  1 13:36:52.243: %ISDN-6-CONNECT: Interface Serial0/3/0:0 is now connected to 0610832758 N/A
Apr  1 13:36:52.243: %ISDN-6-CONNECT: Interface Serial0/3/0:0 is now connected to 0610832758 N/A
Apr  1 13:36:52.243: %ISDN-6-CONNECT: Interface Serial0/3/0:0 is now connected to 0610832758 N/A
Apr  1 13:36:52.243: ISDN Se0/3/0:15 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x013A
Apr  1 13:36:58.243: %ISDN-6-CONNECT: Interface Serial0/3/0:0 is now connected to 0610832758 N/A
Apr  1 13:36:59.987: %ISDN-6-DISCONNECT: Interface Serial0/3/0:0  disconnected from 0610832758 , call lasted 7 seconds
Apr  1 13:36:59.991: ISDN Se0/3/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0x013A
        Cause i = 0x8090 - Normal call clearing
Apr  1 13:37:00.127: ISDN Se0/3/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x813A
Apr  1 13:37:00.127: ISDN Se0/3/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x013A

the sending number should be 0183631323

any idea?

i've already inserted;

voice-port 0/3/0:15
cptone NL
shutdown
no shutdown

Community Member

Re: Main outgoing number presentation

Yes, it is pretty evident that your PSTN provider doesn't like that four digit calling number:

Cause i = 0x82E46C - Invalid information element contents

Also, the "cptone" command doesn't really apply here. It is used for other localization purposes.

As Steven suggested, CCA 1.9.1 can be used to select calling number for outbound calls.

Marcos

Community Member

Re: Main outgoing number presentation

Marcos,

the main number is selected via de CCA 1.9.1. and gives this result. with or whitout 0 in the beginning doesn't make a difference.

Is there some other field i'm missing in here?

Community Member

Re: Main outgoing number presentation

A Rule id was dubbled via CCA 1.9.1. Via cli we found thad 2 rules got mixed up.

5256
Views
0
Helpful
6
Replies
CreatePlease to create content