DISCONNECT message not sent to PSTN

[rwawrig]

Hi,

The call flow is like this: the call is going from a sip phone, through an AS5350 outside to the carrier.

The signaling information is always going through the SIP server. The RTP packets are sent directly to Cisco. When the call is disconnected, the sip server is sending a BYE message to Cisco, and call info to radius server. In the same time Cisco is disconnecting and sending accounting info to radius, and the call is billed.

The problem is that few calls (1 call from 30) are not billed correctly. The information from cisco is coming too late.

In radius log file I have the info from Cisco and sip server. I have seen in the log that (for this calls) the "h323-setup-time" and "h323-connect-time" sent by sip and Cisco is the same, but the "h323-disconnect-time" differ with more or less one minute for all this unbilled calls. Cisco "h323-disconnect-time" is with one minute after the sip "h323-disconnect-time".

In the CCSIP debug i can see that (for this unbilled calls) Cisco is receiving a BYE message from SIP server at the right time, and is sending a bye message back.

Now, what the cisco is not doing - is that is not sending a disconnect message to the PSTN side, but is keeping the channel open until a timer is disconnecting the call on PSTN side and is sending a DISCONNECT message to cisco. In this moment cisco is sending a RELEASE, is receiving a RELEASE_COMPlete and is sending the accounting packets to radius (one minute later when the radius is saying there is no call leg and cannot bill the call).

So, what i see until now is that (for this unbilled calls) cisco is receiving the BYE message from SIP, but is not disconnecting the call on ISDN side, until is not receiving the DISCONNECT message from the switch (one minute later).

Anyone have any idea about ?

[#2]

Check if you are running into the known issue CSCed22112

[rwawrig]

Thank you for your feedback.

It seems that the CSCed22112 bug is a little different from what i have. They are saying that

"The SIP Cancel message sent by the PGW does not get mapped to an ISDN disconnect message on the gateway. This causes the called party phone continuously rining even though the calling party has already hung up." It was interesting, but this is involving a PGW gateway and the problem was resolved by upgrading the software on the PGW.

In my case i'm not using a PGW. The calls are coming from SIP phones to a sip server , and from there through cisco to PSTN.

There is the other idea - that the BYE message is not mapped to an ISDN disconnect message. But why is this happening for 1 call from 30 ?

What i think is that there is a cisco IOS 12.3 bug (or feature).

I was using until now 12.3-10 IOS version.

When i tryed last T version (12.3-11 T) I got another problem. All the calls were not billed.

It seems the cisco was sending in accounting:

Sep 29 05:54:33 UTC: RADIUS: NAS-Port-Id [87] 15 "ISDN 3/1:D:30"

and Radius was saying: Unknown-Attr-87 = 'ISDN 3/1:D:30'

Now, the last solution - a downgrade to 12.2 T version (only available).

I did the downgrade from 2 hours already and no problems yet. The accounting is sent like this:

Sep 29 06:12:25 UTC: RADIUS: cisco-nas-port [2] 15 "ISDN 3/1:D:31"

(one question - how can i change this attribute [87] to [2] for the 12.3 IOS version that the radius understand ?).

I will see during the day is unbilled calls are still coming.

[rwawrig]

the situation is the same