![]() |
|
|
#1 (permalink) |
|
PBXtech SILVER 25+ posts
![]() Join Date: May 2004
Posts: 33
![]() |
BSR:TSC TRK membr not admins event
We have set up TSC's, trunk groups, switches, and DCS in a multi location dial plan. We continue to get an event type 288, BSR: TSC trunk member not administered.
Does anyone know where I can look to try and correct this. \ S8700 CM4 out to multiple locations, G3R CM2, S8700 CM3, CMC CM3, SI CM2. DSC appears to be functioning fine, name and number appearing, calls appear to be completing fine. NO centralized VM involved, strictly call center transfers. Customer using H.323 trunks on MPLS between sites, recently installed and removed ISDN-PRI T1 DCS links. Status TSC on trunk groups shows active with no congestion. |
|
|
|
|
|
#2 (permalink) |
|
Moderator
![]() Join Date: Dec 2005
Posts: 1,360
![]() ![]() |
Re: BSR:TSC TRK membr not admins event
BSR stands for Best Service Routing and is a call center feature. I am home now with no documentation at hand but I suggest you start looking at your call center routing.
BSR is used if you have call centers located in more than one location. If all your calls come in to Atlanta, for example, and after the caller has made their selection in the vectors; the PBX looks at all your administered call centers to decide which one to route the call to depending on skills and wait time. If it finds that the call is better handled in Orlando, the call is routed there. The PBX is telling you that one of your BSR routes is not set up correctly. Look them over closely and follow the logic.
__________________
Marty Retired Avaya DSIC tech |
|
|
|
|
Advertisement
|
Sponsored links
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|