ncphoneman
MIS
We have discovered that calls to analog sets display the wrong caller I.D. number. Here are the particulars:
Definity G3R, 9.5 software.
Two analog sets, extensions 3001 and 3002, set type of "callrid" with call coverage from 3001 to 3002 if 3001 is busy or active.
If two calls are presented within seconds of each other, for example 111-111-1111 then 222-222-2222, the caller I.D. of 111-111-1111 is presented to BOTH sets.
AVAYA help desk says that this feature is working "as designed"; however I can't for the life of me see how anybody would not want the correct caller I.D. for the call that they are being presented.
Has anyone else had this problem and discovered a work-around? I could make a hunt group, but then I loose the coverage capabilities.
ANY help or ideas would be greatly appreciated!!!!
Definity G3R, 9.5 software.
Two analog sets, extensions 3001 and 3002, set type of "callrid" with call coverage from 3001 to 3002 if 3001 is busy or active.
If two calls are presented within seconds of each other, for example 111-111-1111 then 222-222-2222, the caller I.D. of 111-111-1111 is presented to BOTH sets.
AVAYA help desk says that this feature is working "as designed"; however I can't for the life of me see how anybody would not want the correct caller I.D. for the call that they are being presented.
Has anyone else had this problem and discovered a work-around? I could make a hunt group, but then I loose the coverage capabilities.
ANY help or ideas would be greatly appreciated!!!!