Call is disconnected but exceed the credit time of our billing system

Unanswered Question
Jun 7th, 2010

1. According to our Billing system ABC account have 180 seconds left.

2. Billing system passed to Cisco GW the following attributes in the authorization response:
-----------------------------------------------
h323-ivr-in = DURATION:180
h323-return-code = 0
h323-currency = SGD
h323-credit-time = 180
-----------------------------------------------

3. Based on this information Cisco GW should disconnect the call (please note that in this case Cisco managed the call disconnection).
4. After the call ended Billing received the following attributes in the Stop Accounting request from Cisco GW:
-----------------------------------------------
NAS-IP-Address = 'x.x.x.x'
User-Name = '5555657466'
Called-Station-Id = '60379806579'
Calling-Station-Id = '65601865'
Acct-Status-Type = 'Stop'
h323-call-origin = 'originate'
h323-setup-time = '10:44:29.469 cct Wed Mar 10 2010'
h323-connect-time = '10:44:40.511 cct Wed Mar 10 2010' 
h323-disconnect-time = '10:47:40.522 cct Wed Mar 10 2010'
h323-disconnect-cause = '10'
Acct-Session-Time = '180'
-----------------------------------------------

Acct-Session-Time = h323-disconnect-time -  h323-connect-time

Acct-Session-Time = 10:44:40.511 - 10:47:40.522

Acct-Session-Time = 180.011 seconds

From the Cisco GW side the call was considered as 180 seconds, but our billing system computed call duration as (h323-disconnect-time - h323-connect-time) and received value rounded to 181 seconds.

Is there a way that Cisco GW will disconnect the call at exactly 180 seconds or less?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion

Related Content