SMDR and call duration

[nix8]

Why different time between duration from provider and duration from SMDR ???

no. of calls provider - smdr duration
60% 1 sec
10% 2 sec
30% 0 sec

Trunk board is TLU76 R9A / R2 MFC

 

[spamfree]

The time in the SMDR i.e the 3rd field is in increments of 6 seconds by default. It can be changed; look up the appropriate ASPAPARNUM=xx; and modify so that it reports every 1 sec. This should give a more accurate reading.
This problem is more noticable with analogue trunks, the ring duration is counted in the talk time. So calls that ring out and are not answered are seen by the CRD as vaild. Not an issue with ISDN.

 

[nix8]

Thanks for reply,
but this one no result my problem
( I have ASPAP:NUMTYP=122 == 1 not 6 )

 

[TBLuk]

nix8,

You should be doing ASPAPARNUM=122.

If it is 6, change it to 1 by doing ASPACARNUM=122,PARVAL=1;

 

[NIUX]

Hi All,

For your info, for PARNUM=122
If PARVAL=6
Then the 3rd field in SMDR output will be 4 digits:
D1 for no. of hours
D2D3 for number of min.
D4 for tenth of min (each count=6 sec)

If PARVAL=1
Then the 3rd field in SMDR ouput will be 5 digits:
D1D2D3D4 as before
D5 for number of sec (More accurate)

The Billing system should understand the 5th digit.

BR/

 

[PetrNik]

Hello,
I noticed that in BC11 call metering for outgoing public calls starts from dialing number. But in BC9 it started from receiving CONNECT. In BC11 there is additional time (ring time) and there is different between my data and providers' bill. Is there possible to fix this problem?

 

[TBLuk]

Does this only happen when ringing ACD/Hunt groups?

 

[ulhaq]

and also did you check the records eneterd in CLINP.
Meaning that there is possibilty of omitting time in sec.By default it counts for all th sec, but you can set the TIME parameter in CLODI that the calls less this duration are not logged. this is done due to the reasons that usually 01 sec calls are not considered real.... but this depends market to market

 

[PetrNik]

Unfortunately ring time may be different, for example 1 sec or 1 min. It would be better to exclude ring time generally.
But how can I do it?

 

[ulhaq]

ring time means the time before the B-party picks up the phone. yes it varies offcourse. Normally the charging starts when the B-answer is received,
the TIME parameter defined in CLODIis the one which is effective after B-answer or the call has been answered by B-party, and the duration is less then the one for which one feels it not to be real call

 

[PetrNik]

But I see that charging starts from ringing not from B-answer. May be there is any parameter in ASPAC or patch that changes it.

 

[nix8]

hi all,

Q:ASPAC ...
A: I have set ASPACARNUM=122,PARVAL=1;

Q: Does this only happen when ringing ACD/Hunt groups?
A: No, for all calls.

Q: and also did you check the records eneterd in CLINP. ...
A: TIME have set to ALL -> I have registred all calls.
I have only a few calls with length up to 3 secs ->
I have problem with "all calls"
(
no. of calls provider - smdr duration
60% 1 sec
10% 2 sec
30% 0 sec
)

Have You other solution ???

 

[GioBs]

to PetrNik

Well, I don't know BC11 (not yet), but in BC10 the digit D18 of parameter ADC in command RODDI permits to generate an internal answer signal for free charge services without CONNECT. This configuration parameter, I think , is the implementation of a BC9 patch.

I've noted that in BC9, when this function is activated (it should be used with LCR, and not for all calls) the call duration on ISDN trunks is calculated starting from dialling time-out or from CALL_PROC signal, and not from CONNECT, also if the CONNECT signal arrives (that is to say from the internal answer signal).

Perhaps you shoul check if there is something of similar in BC11

As usual sorry for my english

//GioBs