Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mnail

Pages: [1]
1
It is correct though - if the format for recording the Q is WAV (large files though) it works out of the box.

Just costly real estate when doing lots of calls with agents.

Tested in Firefox 2.x and IE 6.0.2900.x.x

I'm at a loss for the GSM file type failure - besides I noticed the file type GSM is associated with Quicktime plug-in 7.1.6 mot Quick time Player - will check on Firefox to see if it can be manipulated.

Thanks again for checking up on this.

2
Hey guys this needs to be checked into - with the JAR files re-coding is not a choice.

The link in the window (pop-up) is only downloading a file name "qm_popup_streamAudio.do"

While yes, if you save this to the desktop and then right click and then rename to "qm_popup_streamAudio.gsm" file it will open and you'll hear the recording - - in reverse while all GSM files play (as we are  recording that format constantly via ARI)  the file type is shown to be a ".do" within QM and the system (browsers) do not know what to do with the file type - - I made the selection of Quicktime but it kicks back with "not a movie file" then stops.

Hopefully this is clear -

How do we re-write the link location to remove the "qm_popup_streamAudio.do"  and have it identify itself as a GSM file? ((((It is not trying to DL'd the GSM extension as it is re-written to the " .do"))))

Line in question is:
out.println( " - <a href=\"" + oC.getS( "POPUP_files" ) + "\" target=\"audio\">" + oC.getS( "POPUP_files_desc" ) + "</a>" );


Thanks for checking into this.

We need the GSM to work as we record over 700 calls daily.

3
Running QueueMetrics / Re: Large environment(s)
« on: March 31, 2007, 20:44:40 »
Just wanted to note for those who are checking out Qmetrics (first and foremost, I have no commercial interest in this product and receive no money if you purchase it – just wanted to be clear)

Anyways, as all management calls happen on a daily basis – I’m pleased with the ability of Qmeterics but have been pulled to roll a couple of sites before re-visiting this.

I noticed something initially I thought the java app was leaking ram – this was not the case though it was a leak in another application on our end. So even though I was granted the “go for it time” it has been taken back (always see a manager 100 miles away) see I even got to fix my own stuff!

They’re good people but you know how it is. (can ya do it in your spare time – sure if I had any :-)

Anyways just wanted to firm up where we are with this on a large environment and timetables have to shift since I primarily do the programming and backbone for our company. I can’t complain as I’m paid well but was digging the results I was obtaining from the Qmetrics product line.

I see as well 1.3.4 with user adjustable hours is coming so this just sparks more interest on my end. Thanks for keeping up the project and we’ll get back to ya and reclaim the time allotted.

4
Running QueueMetrics / Re: Unk Agent - Realtime monitor
« on: March 17, 2007, 18:06:13 »
I had done exactly that (as described via the FAQ) Selected the Agents name and still showed as unknown - its most likely something I have on this end, I'll keep knocking around should not be that major to figure out.

With each version (LS shows there to be Versions 1.x - 1.3.3) If configured can I test each version? (Of course as long as the Conf are configured in each Version folder) Never mind as I finished my thought this would conflict with the DB's layout. Not enough coffee in me yet.

5
Running QueueMetrics / Re: Large environment(s)
« on: March 17, 2007, 18:01:03 »
Good deal if it is a hardware thing - the I/O bottlenecks have been cleared up for us (cost but worth it) Ram Disk - all recording(s) happen within ram  - this started just as a means to not have early drive failure but proved worth its weight in gold.

I'll know as the next couple of weeks roll forward - Management always looks at the bottom line etc.. so we have to prove everything (Why/Why not).

It comes as an after thought to some (logging and monitoring that is) but thats what they pay us for - to think and then prove Why.

The ability to see reasoning (call disconnect, time etc to me is critical) staffing (we currently over staff) obviously not cost effective for any company, not to mention who was where when (aka - such n such was being paid but answer one call in the morning) that might work for small places with less hustle but we see it all the time "Gone fishing" just trying to keep it balanced.

We have some monitoring tools that happens now but they are trivial in comparison.

The CRD built into Asterisk is not correct - just meaning one cannot state Agent answered @ what time, wait time since the CDR handles (Start, answer, End, duration, billing times - but again The Q (switch) answered, not the agent.

Hard to get some to understand, surprisingly. Your app looks good to me and if we do not obtain it it will not be from lack of trying - just bad management call.

Still any work arounds I happen to find I'll post so others can have a shot at it should it help.

6
Running QueueMetrics / Unk Agent - Realtime monitor
« on: March 16, 2007, 19:14:28 »
"Agents currently logged in" Appears correct with username and extension.

When inbound call starts everything appears as it should.

Once call is in progress - it shows agent name and wait time/talk time - in the upper realtime monitor the it shows Unk - - even though all other info appears correct along with Agent full name and the extension?

Something I missed?

Since we have custom loads on the production servers I'm doing this on a lab system clean load no real tweaks - Freepbx front end, QMetrics ver. 1.3.3.

Only tweak I am doing is the Agent login from the previous post ( I tried it the way the FAQ suggest but still shows Agent Unk instead of busy.

Call does show to be inprogress etc.. just that field seems to not populate correctly. TIA

7
Running QueueMetrics / Large environment(s)
« on: March 16, 2007, 18:28:29 »
Hey, could anyone let me know of Agent limitation?

We have 700+ on a cluster - Reading docs state 2-200 Agents, is this s limitation of the software (i.e. heapsizes) or limited by hardware?

If this is a software limitation - can the systems be chained together as a cluster - showing Q's from another Queuemetrics system?

We have 400 Agents within 1 Q - 180 in 2nd Q etc..

Asterisk is handling this setup but custom loaded and highly tunned for our use.


Thanks

8
Edited original post to reflect the rewrite statement - Thx for the catch

Another note, I noticed the "default.rewriteLocalWithQueue=true" did not work well - or I did not do it correctly during initial test) maybe I misunderstood what it did but was used in conjunction with the original work around for Freepbx installation(s) due to the way it handles the dial plan (aka, no AgentLogin() ) anyways this app has some serious potential within orgs just hard to have time (unless multiple people test and post back) works arounds etc.. Again I have time to play and if I can get it to work for our org I have no problem posting work arounds that are efficient and hopefully get feedback (constructive :-) but none the less wider platform usage.

9
When users have the Freepbx front end (aka amp) and you make a Q, no longer is there the Agentlogin() to hear music all the time - it remedies a couple of things - if agents are logged in and listening to music, the Moh will take bandwidth from the local network and the Moh will also create an additional load on the asterisk server - - with that in mind the Q's are made (within Freepbx) to have static or dynamic agents - but when they call the switch it will not keep them on the line and will hang up until a inbound call comes in.

Now the problem created by this is the Agents will not show up in the Queuemetrics realtime monitor or the wall panel monitor (without hacking the dial plan and then having agents do a dual logging) No good we say.

(We rely on scripts from Andrews old dial plan off AAH/Trixbox, so this reflects partial dial plan from there as well.)

First things first Edit: the "rewriteLocalChannels=true" is a must - for those that may wonder where it is (version 1.3.3 configuration.properties located (rpm based install) /usr/local/queuematrics/webapps/queumatrics-1.3.3/WEB-INF (linux installation of course) (line 109).


Easy fix for this - Works on Freepbx Version(s) 2.x.x (currently from 2.0 to 2.2.1 - latest)

In the dial plan

Edit Extensions.Conf

[macro-agent-add]
exten => s,1,Wait(1)
exten => s,2,Macro(user-callerid,SKIPTTL)
exten => s,3,Read(CALLBACKNUM,agent-user)     ; get callback number from user
exten => s,4,GotoIf($["${CALLBACKNUM}" = ""]?5:7)   ; if user just pressed # or timed out, use cidnum
exten => s,5,Set(CALLBACKNUM=${CALLERID(number)})
exten => s,6,GotoIf($["${CALLBACKNUM}" = ""]?2)   ; if still no number, start over
exten => s,7,GotoIf($["${ARG2}" = ""]?9:8)   ; arg2 is queue password
exten => s,8,Authenticate(${ARG2})
exten => s,9,AddQueueMember(${ARG1}|Local/${CALLBACKNUM}@from-internal/n)   ; using chan_local allows us to have agents over trunks
exten => s,10,UserEvent(Agentlogin|Agent: ${CALLBACKNUM})
exten => s,11,System( echo "${EPOCH}|${UNIQUEID}|NONE|Agent/${CALLBACKNUM}|AGENTLOGIN|-" >> /var/log/asterisk/queue_log )
exten => s,12,Wait(1)
exten => s,13,Playback(agent-loginok)
exten => s,14,Hangup()

_________________Modified/added line in bold above____________________

To remove the agent(s) upon logout here is the change for that as well.

Edit Extensions.Conf

[macro-agent-del]
exten => s,1,Wait(1)
exten => s,2,Macro(user-callerid,SKIPTTL)
exten => s,3,Read(CALLBACKNUM,agent-user)     ; get callback number from user
exten => s,4,GotoIf($["${CALLBACKNUM}" = ""]?5:7)   ; if user just pressed # or timed out, use cidnum
exten => s,5,Set(CALLBACKNUM=${CALLERID(number)})
exten => s,6,GotoIf($["${CALLBACKNUM}" = ""]?2)   ; if still no number, start over
exten => s,7,RemoveQueueMember(${ARG1}|Local/${CALLBACKNUM}@from-internal/n)
exten => s,8,System( echo "${EPOCH}|${UNIQUEID}|NONE|Agent/${CALLBACKNUM}|AGENTLOGOFF|-|${RV}" >> /var/log/asterisk/queue_log )
exten => s,9,UserEvent(RefreshQueue)
exten => s,10,Wait(1)
exten => s,11,Playback(agent-loggedoff)
exten => s,12,Hangup()

______________________________Modified/Added line in bold_______________________________


Now when Agents login and Out they are correctly moved from the Database and no additional work arounds for the Agents.

After the change above - make a Q give it what ever # you want (with out with out PIN#) (lets say 123)
Agent snow call the switch and dial "123*" (without quotes) and they are asked to login with their agent # - they enter their extension and the system shows immediately with Qmetrics that they did and managers are happy, Agents are happy and we take the rest of the day off to do something else! Not really to much stuff to get into :-)

Admins must still add agents to the front end of QueueMetrics (i.e. Agent/7200 with the persons name) The script change above will add the Agent/ (and dynamically grab the extension based on callerID) injecting it into the queue_log for asterisk.

Just now tinkering with the Qmetrics stuff but looks promising and as we go will post solutions as we use multiple systems and dial plans and it will prevent dual agent logins or funky dial plan hacks.

Enjoy!

Pages: [1]