Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BSR Between 2 G3's not working

Status
Not open for further replies.

mikej97204

IS-IT--Management
Jul 12, 2005
203
US

I am trying to set up BSR between two locations. The local site has a G3r v9.05 and the remote site has a G3si v9.05. Both have LAI and BSR turned on.

I have set this up according to the Avaya Call Center
Release 3.1 Call Vectoring and Expert Agent Selection
(EAS) Guide, following the examples it has.

It seems to almost work. When a call comes into the local PBX the BSR Vector does do a poll to the remote site and the remote site does show that there is agents available (based on list trace vector on the remote polling VDN), but that information is not sent back to the local PBX. What comes back is this:

05:56:12 0 0 ENTERING TRACE cid 6590
05:56:12 101 1 vdn e5300 bsr appl 1 strategy EAD-MIA override n
05:56:12 101 1 wait-time
05:56:14 101 2 consider
05:56:14 101 2 consider skill 23 pri m ewt INFINITE adjusted ewt INFINITE
05:56:14 101 3 consider
05:56:15 101 4 consider location 1 NO DATA RETURNED FROM POLL
05:56:15 101 4 queue-to
05:56:15 101 4 NO BEST DATA DEFINED

This is what the remote shows:
07:58:35 0 0 ENTERING TRACE cid 395
07:58:35 202 1 vdn e7224 bsr appl 0 strategy EAD-MIA override n
07:58:35 202 1
07:58:35 202 2 consider
07:58:35 202 2 consider skill 23 pri m idle time 14 skill level 1
07:58:35 202 3 reply-best
07:58:35 202 3 reply-best ewt 0 adjustment 0 idle time 14
07:58:35 202 3 occupancy 75% skill level 1
07:58:35 202 3 LEAVING VECTOR PROCESSING cid 395
07:58:35 202 3 TRACE COMPLETE cid 395

If there are no agents available on the remote side I get back this:

06:10:15 0 0 ENTERING TRACE cid 6900
06:10:15 101 1 vdn e5300 bsr appl 1 strategy EAD-MIA override n
06:10:15 101 1 wait-time
06:10:17 101 2 consider
06:10:17 101 2 consider skill 23 pri m ewt INFINITE adjusted ewt INFINITE
06:10:17 101 3 consider
06:10:17 101 3 consider location 1 polling suppressed
06:10:17 101 4 queue-to
06:10:17 101 4 NO BEST DATA DEFINED

I assume the "polling suppressed" means that there were no agents available at the remote end since that is the only time I get that trace return. When I'm running these tests, I have no agents available on the local side since I want the call to go to the remote site.

I've been reading and searching for information and two things have been mentioned. One is that Q-Sig might be needed for this to work (we do not have Q-Sig turned on on either PBX) and that it won't work on a ISDN trunk. The tie line between the two sites is set up as a ISDN trunk set up this way:

Group Number: 20 Group Type: isdn CDR Reports: y
Group Name: Tie Line COR: 1 TN: 1 TAC: 801
Direction: two-way Outgoing Display? n
Dial Access? n Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc


I'm stumped as to why it won't work. I don't know if I'm missing something or if the problem is not having Q-Sig turned on or if using a ISDN trunk is the problem. I'm sending other calls over the tie line or I would change the trunk group type and try it, so I don't want to do that unless I have to.

So my question is, do I need Q-Sig to get BSR to work and does the type of tie line trunk group matter?

Thanks

Mike
 

I have finally got this to work between our two locations. After reading the Avaya Call Center Call Vectoring and EAS Guide, BSR section a bunction of times, I saw a small section that talked about UUI. I found what I have been missing was changing the UUI IE Treatment option on the 2nd page of the trunk group configuration. Default for all of our trunks has been:

UUI IE Treatment: service-provider

But for BSR to work (at least in my situation, I don't know if it's always necessary), I needed to change it to:

UUI IE Treatment: shared

This also brought up some other BSR parameters that I left at default. Once I did this, my polls started returning best choice and the calls started flowing to the appropriate location. Now I just need to tweak the vectors a little to make sure a call doesn't get stuck in one queue or the other and I'll be ready to do some live testing with it. Hopefully I won't run into any more surprises.

Mike
 
Thanks for taking time to post your resolution Mike. It may help others when they run into this same situation.

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top