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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Incoming call issue"Invalid number format (incomplete number)"

Dear Cisco Team

I am facing problem with one of my site where we are running UCCE 8.5 , CVP 8.5

I have two voice gateways for incoming and outgoing.

i am facing problem with incoming calls before it was configured with 142 number and recently the customer had changed the number from 142 to 164

i had made changes in the gateway but when i am testing incomiong calls it giving me below error message.

*May  2 11:44:46.749: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x1F45

        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839B
                Exclusive, Channel 27
        Calling Party Number i = 0x0083, '55491715'
                Plan:Unknown, Type:Unknown
*May  2 11:44:46.749: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x9F45 cal
lID = 0x36F7 switch = primary-net5 interface = User
*May  2 11:44:46.753: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x
9F45
        Channel ID i = 0xA9839B
                Exclusive, Channel 27
*May  2 11:44:46.753: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8  callref = 0
x9F45
        Cause i = 0x809C - Invalid number format (incomplete number)
*May  2 11:44:46.817: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8  callref = 0x1F
45
*May  2 11:44:46.817: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8  callref =
0x9F45

I checked with the provider and he told me that you have problem at your end.

i have also attached the gateway config.Kindly have a look on it and advise please.

Thanks

Regards

Everyone's tags (4)
2 REPLIES
Green

Incoming call issue"Invalid number format (incomplete number)"

I don't understand the problem or know the answer, but I had a quick look at the config file and noticed a couple of issues.

1. In the voice service voip - sip section you bind the SIP control messages to your loopback interface but there is no setting to bind the media mesages to the same interface. These usually go in pairs:

sip

  bind control source-interface Loopback0

  bind media source-interface Loopback0

  rel1xx disable

  min-se 360

  header-passing

2. The dial peer for cvp error is not correct. Ringtone is OK. You have incoming called-number 9292, but unless you have changed it on the CVP side, the number is 92929292.

3. You don't have your pots dial peer under the control of the cvp-survivability service, even though you have defined it.

Regards,

Geoff

Incoming call issue"Invalid number format (incomplete number)"

Tell your telco that they seem to be doing something wrong.

*May  2 11:44:46.749: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x1F45

        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839B
                Exclusive, Channel 27
        Calling Party Number i = 0x0083, '55491715'
                Plan:Unknown, Type:Unknown

There is no Called Party Number (should be 164 from your description) included in the SETUP they send and the 'Sending Complete' bit is set to True so the gateway will attempt to route this called as soon as the SETUP is received, yet it has no destination number (164 which with your config will be expanded to 80000 and routed out dial-peers

80000/800010).

So ask your telco why there is no Called Party Number included in the SETUPs they send.

Cheers,

Kris

1890
Views
0
Helpful
2
Replies