G3si Prompting Buffer Full

[pbxman]

Okay guys...this is going to drive me nuts. I increased our Prompting Buffer about a year ago, and we are again getting "Prompting Buffer Full" events in our switch. I can NOT seem to find where I changed this last time...I keep thinking it's in our announcement boards somewhere - and i need to increase it again.
Could someone refresh my ailing brain? :Thanks!

 

[cclausen]

Need some more informaiton. The switch stores digits in a digit buffer. This normally associated with a collect in a vector. Are you using vectors on your system?

 

[pbxman]

Yes - we are using Vectors, ACD, Hunt Groups, VDN's, ARS, etc...
It's a simple command - I just cant remember what it is..

 

[cclausen]

You might want to try "change system features" and see if there is anything in the various pages for increasing the size.

Chris

 

[pbxman]

Nah - thats not it. If I remember correctly - it was somewhere where you wouldnt expect it to be...and thats probably why I can't find it again!
Thanks for the response, though - any other ideas? I'll know it as soon as i see it!
hehe

 

[VLG711]

PBXMAN,
I think what you are looking for is the number of collected digits in the vector step. The display events command will tell you which vector is having the problem (in the Data 1 column "vec/step&quot. The step should look like Collect XX digits after announcement XXXX. On our V8 I believe you can only collect a max of 24 digits.
I hope this helps.

KGG_DRS

 

[pbxman]

Wow - I forgot this was open-ended still..

I still haven't found it. It has to do with how many lines are available before the collect digits step. There's a place to change the number. Default was 8, and I upped it to 16, now i need more. We haven't got the errors recently, so i forgot about it. I should just call Lucent at this point, because it was so long ago, and I cant remember.

If anyone else knows..let me know!
Thanks for the input guy's..again - it's not something that "makes sense" per se..it's a real weird hidden feature.

Thanks again - if i find it, i'll post it...good stuff to know.

 

[mclellan]

Hello,

We have run into this problem on our G3R V11. Does anyone know how I can fix this?


Thanks!
Barry

 

[jaymzter]

Anything over 24 digits is discarded and the vector event is generated. The 24 digit ceiling is non-negotiable. Do you know what circumstances are triggering this scenario?

 

[bravosfreak]

Did anyone ever find the fix for this problem. We ran into this issue yesterday. I have never seen it before.

 

[orypecos]

http://www.google.com/search?q=cach...ting+Buffer+Full+site:support.avaya.com&hl=en

Does it have something to do with sending the records to Cms?
This article seems to be talking about records coming out of the cms rather than from the pbx to the cms. But I am only guessing.


®
Call
Management System (CMS) feature which allows you to transfer the
CentreVu CMS Release 3 Version 6 (R3V6) call record files (call history
data files) to another computer for processing.
This feature is especially useful for call centers with a high volume of
calls. It allows a much higher volume of call record data to be processed
and stored than can be processed and stored on the CMS computer.
If you are upgrading to CentreVu CMS R3V6, any applications
associated with the ECHI may have to be rewritten because additional
call record database items were added with R3V6 CMS. You need to
make sure that the version field (which identifies the CMS version) is
correct.
Space Allocation
0
You will need to allocate space on CentreVu CMS for call records to be
buffered (in System Setup: Data Storage Allocation, up to 99,999
segments in a buffer).
Call Record File
Size
0
As calls are processed, call records are recorded in a file (one record per
call segment) until the file size reaches 20 MB or the end of an interval is
reached, whichever comes first. When this happens, the file of call record
segments is transferred to another computer via uucp (at speeds of up to
38,400 bps if the computers are close).
A new file (and its first record) is then created as the first segment of the
next call is processed.
Data File Format
0
This document describes the format of the external call history data files
and what you must do to transfer these files to your computer.
You are responsible for the storage of and subsequent formatting,
printing, and so forth, of the data transferred to your computer.
NOTE:
NOTE:
Page 6
Call Record File Format
2 CentreVu CMS R3V6 External Call History Interface
Call Record File Format
0