CLI on incoming calls on 4 alog lines is being presented as follows 07xxx-xxxxxx or 0113-xxxxxx, is this a BT issue or is the IPO at fault, S/W ver 2.1.27
Many thanks.
BT, and a few other providers in the UK send CLI with the "-" between the SDT code (area code) & the main part of the number.
This will cause alpha taging to fail but it was fixed by Avaya in V2.1(31)
This fix has so-far not made it into V3.0 dispite repeated requests during field trials.
I thought this one had gone away, but I have just had an email from the customer with the following Monitor log.
It now seems (since the upgrade to 2.1.31) the "-" has been replaced with a space in the CallingNum field.
cjinsocal581, earlier you asked about Incoming Call Route set-up, could this have a bearing on this problem?
342927mS PRN: 56 bytes @ffe901c4 were allocated by ffe11a70 00000000 at 541270299 mS
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.