ecas

[alfalfa]

I have a cust with ipo 500 4.1.9 that is running ecas and using cdr to get info to ecas, on the reports in ecas they are showing under ext field 99999, ----------, and *
Does anone know what the 99999 actually is have seen mention of it in other threads but never -------, nor *

 

[piethief]

voicemail, according to veramark

 

[puregold]

Extension: Range = 2 to 9 digits.
Any number up to 9 digits. In general all extensions should have the same number of digits. This setting can be left blank for users used just for dial in data connections.

Users for Delta Server, CBC and CCC should only use up to 4 digit extension numbers.

Users associated with IP phones or who may log in as such devices should not be given extension numbers greater than 7 digits.

Extension numbers in the range 8897 to 9999 are reserved for use by the IP Office Delta Server.


ACE - Avaya Certified Expert
ACI - Avaya Certified Instructor

 

[CarGoSki]

Veramark uses 9999 to mask a voicemail call. If you need to see the true destination then assign an auth code to the user then add an auth code field to the report.

-------- with a duration of zero is a hangup.

* = ??

 

[jslewis]

Ipo 406 ver 3.2.x
I am lucky to find a fresh ecas thread. I am trying to track incoming calls from a DID that go to a huntgroup.
ext # are 1xx and 2xx
Hunt group # is 526 with one user and an overflow group.
The extension summary report always shows 0 calls for 526, but the 9999 numbers mentioned in previous posts show lots of calls.

Is ecas capable of tracking this type of call routing?

 

[piethief]

What version?

 

[jslewis]

My cleints ecas version is 3.1.071.04c

 

[piethief]

https://support.veramark.com/customer/logon.asp

use your serial number to access this site. I belive there is a known issue with CDR. I never use it, I use Delta Server and collect SMDR. Then you have an intermediate layer that you can look at and see what data ecas is getting.

There also is a setting in ecas to ignore voicemail calls, part of the switch wizard.

I've never specifically chased down this issue, and there may not be a fix.
Good luck though.

 

[CarGoSki]

Have you tryed assigning an auth code to the hg user then adding auth code to the report?