Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Call Logging problem- Strange conditon code.

Status
Not open for further replies.

djudjuman

Technical User
Mar 24, 2003
59
NL
A call logging was programmed on Ericsson BC10 and the format used was a user defined form. It was noticed that it generated some condition
code NC,and B which are not listed in Alex.
It still generated condition codes that can be interpreted in alex. On trying to view the form programmed, using command CLFOP; it gave the message 'NOT ACCEPTED,NOT ALLOWED'. So the question is how to interpret the condition code and why the error message when one enter the command CLFOP.
 
That combination likely means that the dialled extension was diverted, the diversion point was busy and the caller hung up.

(N) Dialled party not equal to answering party
(C) Abandoned calls
(B) Calls to a busy party

It doesn't have so much to do with the output file format, but I bet "yes" was entered for the LOGABN parameter when the CLOHI command was initiated.

C-ya,

Dave Strang

 
Thanks Dave for the Help. Where can i get the interpretation of the letters B and C ?.In Alex i can see NC though as a double character condition code but not C separately and B.
Cheers
 
Call information logging, CL & ED,
Description of the extra facility,
EXTRA FACILITY DESCRIPTION
1/1551-APD 101 02 Uen K4
Condition codes for call data
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top