Issues with disconnect cause code 28

[wilsonsant]

Hi Guys,

I am having problem in site where not is possible complete the call to number format 1xx. I see that the call not arrived in the gateway. Verifying the debug I see the disconnect cause code 28. I am attaching the logs. Could You help me, please

For test I was trying call to number 156 (I need first put 0 to take line)

Thanks,

Regards,

Wilson

[Daniele Giordano · Accepted solution]

Hi, your gateway receive an INVITE:

Received:
INVITE sip:0156@10.96.19.5:5060

and it sends a new invite without 0:

Sent:
INVITE sip:156@10.24.0.102:5060 SIP/2.0

but the remote gateway reply with "address incomplete":

Received:
SIP/2.0 484 Address Incomplete
Via: SIP/2.0/UDP 10.24.4.14:5060;branch=z9hG4bK3AF51524;received=10.24.4.14
From: "WILSON IPComm" <sip:4710@10.24.4.14>;tag=85BA44D0-80F
To: <sip:156@10.24.0.102>;tag=as656eb743
Call-ID: CE6DCE0C-B69211E8-AEB49A5F-99C2B8C1@10.24.4.14
CSeq: 101 INVITE
Server: Dialdata-VRS-v2.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0

So, you must check on this "Dialdata-VRS-v2.0" if it can handle 3 digits dialed numbers.

Regards.

[wilsonsant]

Hi Daniele,

Thanks a lot for Your contact. I talked with the Carrier and him told me that call not is arriving. I don´t identified problem with configuration (maybe that there are any error, but,...)

Thanks,

Regards,

Wilson

[Daniele Giordano]

Hi, the "Dialdata-VRS-v2.0" is a device of your carrier?
If yes, the device replies to your Cisco with a 484 address incomplete so, it's impossible that a call is not arrived.
If the Dialdata is not a device of a carrier, who manage this equipment?

Regards.

[wilsonsant]

Hi Daniele,

Yes, the equipment is of Carrier, but, They are to affirming with the call is not arriving.

in my side, in try to monitoring with the command: show call active voice compact and I too don´t see the call in the gateway.

Thanks,

Regards,

Wilson

[Daniele Giordano · Accepted solution]

My suggestion is to send the debug to the carrier.
In this way also the carrier can see the trace.
To go deep in the issue you can ask to the carrier a debug or a trace on its device.

In this case they can see the call and investigate about the reject.

Regards.

[wilsonsant]

Hi Daniele,

There are the caracteristic specifc that need to configure in the gateway (I don´t know this information). Now We will to configure and believe that will solve the problem (the Carrier pass this information). Thanks a lot for Your help.

Regards,

Wilson