Greetings,
I recently downloaded the latest version of the gui, revision # of about
5154 or so. Previously I had been working with something dating around
5104 or so (ancient, I know).
I was looking at the new queue login/out logic using AddQueueMember etc
to get around the disappearance of AgentCallBackLogin post *1.4
My question is whether this is intended to work with * 1.4. I've had a
lot of trouble even getting off the ground with this with *1.4
For instance, I had to change
"Goto(queue-member-manager,handle_member,1)" to
"Goto(queue-member-manager,s,1)", with the corresponding changes in
queue-member-manager. *1.4 choked on the use of handle_member as the
extension.
also. ${CHANNEL(peername)} is not returning anything useful, as in:
-- Goto (queue-member-manager,s,1)
-- Executing [s@queue-member-manager:1]
Verbose("SIP/9166-00000096", "2| Looping through queues to log in or out
queue members") in new stack
== Looping through queues to log in or out queue members
-- Executing [s@queue-member-manager:2] NoOp("SIP/9166-00000096",
"Channel peername is ") in new stack
-- Executing [s@queue-member-manager:3] Set("SIP/9166-00000096",
"thisActiveMember=SIP/") in new stack
-- Executing [s@queue-member-manager:4] Set("SIP/9166-00000096",
"queue_field=1") in new stack
-- Executing [s@queue-member-manager:5] Set("SIP/9166-00000096",
"thisQueueXtn=") in new stack
-- Executing [s@queue-member-manager:6] While("SIP/9166-00000096",
"0") in new stack
-- Jumping to priority 10
== Auto fallthrough, channel 'SIP/9166-00000096' status is 'UNKNOWN'
changing ${CHANNEL(peername)} to SIPCHANINFO(peername)} works better,
but that obviously defeats the purpose of being channel agnostic.
And, I don't get any further in any event:
-- Goto (queue-member-manager,s,1)
-- Executing [s@queue-member-manager:1]
Verbose("SIP/9166-00000097", "2| Looping through queues to log in or out
queue members") in new stack
== Looping through queues to log in or out queue members
-- Executing [s@queue-member-manager:2] NoOp("SIP/9166-00000097",
"Channel peername is 9166") in new stack
-- Executing [s@queue-member-manager:3] Set("SIP/9166-00000097",
"thisActiveMember=SIP/9166") in new stack
-- Executing [s@queue-member-manager:4] Set("SIP/9166-00000097",
"queue_field=1") in new stack
-- Executing [s@queue-member-manager:5] Set("SIP/9166-00000097",
"thisQueueXtn=") in new stack
-- Executing [s@queue-member-manager:6] While("SIP/9166-00000097",
"0") in new stack
-- Jumping to priority 10
== Auto fallthrough, channel 'SIP/9166-00000097' status is 'UNKNOWN'
I haven't check the rev level of *1.4 recently, we are running 264334
currently. I wouldn't have expected functional differences in revision
levels in any event.
(FYI, 9166 is configured as agents on 2 different queues)
Any thoughts on this would be most appreciated. If the answer is "go to
1.8" I'm good with that... eventually.
Ron
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-gui mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-gui
