Hi
I face a problem with the timer of call logging, it is sometimes hungs and gave me duration time 9:59:59. this happens randomly with random extensions.
md110 bc10_cna:135
9.59.59 is max time for one call record .
If the actual call is longer a call record with 9.59.59
is pushed out , and a new at the same extension takes over for the rest of the calls duration .
thanks Syar
acually the calls less than 30 minutes but the timer hungs, I stoped the call logging and resart all the programme unets "SFCEI", BUT ACUALLY DID NOT HELP.
Do you have headsets connected with the digital extensions??? & Analog 2W trunks??
Sometimes users with headsets doesn't clears the call on the phone & leaves the headsets aside when they don't get line/register signals & there is no disconnection from the called end...
I have seen this situation so may be that could be the case!!!!!
Hi
To Mr.singhbrindisi thanks for your replay. There are no headsets connected with the digital extensions or Analog 2W trunks.
**********************************************************
To Mr.daJAYman Thanks also for your replay. I stopped the call logging by command "CLTGE;" And I restart the following pu:CLOPS1&CLOPS2&CLPS1&CLPS2&CLPS3&CLHH&CLOM&EDH&FAM2&SIP
and then "CLTGI;"
Unfortunately the above procedure did not solve the problem
I used: SIU card
************************************************************
To fcpli thanks also for your replay. and here you are the print out
PCLOP:UNIT=CLPS1;
PATCH LOG DATA
UNIT: CLPS1 LIM: 1
CI TYPE STATUS SIZE IA/SIGNO/ADDR CORRSTART
S76458A PROGRAM CONF 66 0000205C 00004172
S76522A PROGRAM CONF 54 00001B6E 000041B4
S76522A PROGRAM CONF 54 0000392A 000041EA
S77984A PROGRAM CONF 56 000005E8 00004220
S77984A PROGRAM CONF 72 00001740 00004258
S78748A PROGRAM CONF 140 0000177A 000042A0
S86804A PROGRAM CONF 106 00001F44 0000432C
S86804A PROGRAM CONF 46 00001FAE 00004396
S86804A PROGRAM CONF 192 00001FBC 000043C4
S88847A PROGRAM CONF 82 0000186A 00004484
S88909A PROGRAM CONF 286 00000D80 000044D6
S88909A PROGRAM CONF 54 000034AE 000045F4
S89020A PROGRAM CONF 76 00002368 0000462A
END
************************************************************
Thanks alot for your help.
Hi md110user!
Insert the following patch, it should help. If not, it does not harm anything (or anybody). Updating the SP doesn't help in this case. If the problem continues, more "research" is needed. Good luck!
fcpli
Hi md110user I had a similar problem, and it was as sayar2003 said, calls were 10 hours or longer we used TABS as our call accounting and a call type of "J" was put out from the MD110 BC 10 and was not recognized. We put a patch in TABS & now all is ok what type of call accounting do you use and what type of call does it see?
Cheers Brian
I had a similar problem, the peoblem was that even though the Ext. will hang up and terminate the call, the route equipment will still be busy with the external line, try checking ur route parameters for disconecation signalling.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.