Old tech, new system : BCMS Login ID's

[Nick44]

Hi Guys,
Cust is running CM6.2 with AACC contact Centre.
As they have AACC, there are no EAS licences on the platform.

There is a need for a simple system with a single DN for the nightly duty manager to login, so the CC has a single number to call if they need to access the Duty Manager.
So,
I set Up a VDN to Vec with Q to split 60
Set up Hunt 60 as ACD/vec.
Added BCMS Login ID's, 2001 to 2012.
added station numbers of Duty Managers to HG.
FAC for agent login is #12
so, figured for agent to login to split the dial train would be #122001
Cannot find any documentation on support.avaya for BCMS Agent Login ID's as it's very old tech now.

( did this 15 years ago but can't remember any more - old age) .

list trace on user station returns:-
“denial event 1381 : Agent login fail D1=0x9ee8 D2=0x1244”
fails at last digit dialled.

Hunt Grp cacpacity is 8000

What's the correct dialstring to get a BCMS login ID to connect?




Speak softly and carry a big switch

 

[AvayaTier3]

need the hunt group on the end (also when you log out of each hunt-group)
#12 2001 0060

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AvayaTier3]

Your station can be a member of several splits. It can login to 3 at the simultaneously. It must login to each, one at a time.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[Nick44]

Mr Hamilton, by golly,
Good evening Sir, many years since we last spoke!
Hope I find you well. Many thanks for the reply.

FAC for agent login is #12
agent dials #12 ( from registered handset in split group 60 )
dial tone returned.
agent dials 2001 ( registered BCMS Login ID )
gets deny tone on last digit, so:-
#12200 (then 1 - then deny)

or could it be just not dialling fast enough and getting time - out on digit dialling.

Also, you suggest 060 for split registration, as hunt group range is 4 digit wouldn't it need to be 0060?

Therefore #1220010060?
When I get it right will prog up an Abb Dial, just testing at the mo.

Cheers,
Nick.





Speak softly and carry a big switch

 

[AvayaTier3]

add hunt help
this will tell you how many digits for the hunt-group number

software versions, system hardware platforms / memory capacity and other considerations
like hospitality reduction turned on can limit system to 10 hunt-groups.
have something to do with max hunt-group.

4 digit HG for hunt-group 1 may be
01
001
0001

60
060
0060

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AvayaTier3]

display system-parameters features                              Page  12 of  20
                        FEATURE-RELATED SYSTEM PARAMETERS

  AGENT AND CALL SELECTION
                         MIA Across Splits or Skills? y
                          ACW Agents Considered Idle? y
                          Call Selection Measurement: current-wait-time
    Service Level Supervisor Call Selection Override? n
                                 Auto Reserve Agents: none


  CALL MANAGEMENT SYSTEM
                           REPORTING ADJUNCT RELEASE
                                      CMS (appl mis): R15/R16
                                      IQ  (appl ccr): 5.0

                               [COLOR=red]BCMS/VuStats LoginIDs? y
[/color]                   BCMS/VuStats Measurement Interval: hour
           BCMS/VuStats Abandon Call Timer (seconds):
                     Validate BCMS/VuStats Login IDs? n
                            Clear VuStats Shift Data: on-login
                 Remove Inactive BCMS/VuStats Agents? n

Above works with any number and BCMS LoginID does not have to be defined (no validation)

display system-parameters features                              Page  12 of  20
                        FEATURE-RELATED SYSTEM PARAMETERS

  AGENT AND CALL SELECTION
                         MIA Across Splits or Skills? y
                          ACW Agents Considered Idle? y
                          Call Selection Measurement: current-wait-time
    Service Level Supervisor Call Selection Override? n
                                 Auto Reserve Agents: none


  CALL MANAGEMENT SYSTEM
                           REPORTING ADJUNCT RELEASE
                                      CMS (appl mis): R15/R16
                                      IQ  (appl ccr): 5.0

                               [COLOR=red]BCMS/VuStats LoginIDs? y[/color]
                   BCMS/VuStats Measurement Interval: hour
           BCMS/VuStats Abandon Call Timer (seconds):
                     [COLOR=#CC0000]Validate BCMS/VuStats Login IDs? y[/color]
                            Clear VuStats Shift Data: on-login
                 Remove Inactive BCMS/VuStats Agents? n

These will only work when BCMS LoginID is defined and mapped to a name
Command: change bcms-vustats loginIDs



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

44 years Bell, AT&T, Lucent, Avaya
Tier 3 for 34 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[Nick44]

Thanks,
Sys para feats all set as you show above

add hunt help returns 1 - 8000

Ch bcms login shows agents 2001 to 2012 registered and named

Ch hunt 60 shows test ext 2278 populated up.



Speak softly and carry a big switch