Queue MemberName behavior

mkeuter

Hi Nicolas,

at one of my customer sites with FOP2 2.2.7 I see a very strange behavior when I use the "queuechannel" setting:

[SIP/12]
type=extension
extension=12
context=default
label=Secretary
queuechannel=SIP/12|Penalty=0|MemberName=12

When I use the above setting and I login 12 into a Queue, the member in the Queue appears with "12", which is fine. But also the label of the extension button for "12" switches from "Secretary" to "12".

On my own installation and another customers FOP2 2.2.7 installation, this does not happen.
I compared all related setting, but didn't find anything helpful.
Any idea what could cause this?

Michael

nicolas

Hi,

The extension buttons are renamed if a queue member is of the type Local/12@from-queue and the extension and queuecontext in the fop2 button configuration matches 12 and from-queue respectively. (look at the output from asterisk -rx "queue show" and see if the device is Local/xx instead of SIP).

Best regards,

mkeuter

Hi Nicolas,

in this case the Member is a SIP channel not a Local channel:

91 has 0 calls (max 1) in 'ringall' strategy (13s holdtime, 12s talktime), W:0, C:7, A:0, SL:85.7% within 30s
Members:
12 (SIP/12 from SIP/12) (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet
No Callers

Update: it also happens if I change the context from "default" to it real context "ip-phones".

nicolas

In case of device members, label renaming is also standard. Whenever there is a queuemember event where the location differs from the name, the matching extension button will be renamed with the queue member name. There is no way to stop that behaviour currently.

Best regards,

mkeuter

Hi Nicolas,

I don't know what's happening internally, but on my own system and another customers one, this does not happen. See screenshot (extension 24 has the MemberName 24@local-agents and the button is still named "Yealink Büro"
http://mksolutions.info/galerie/q-membername.png

[SIP/24_yeal38g]
type=extension
extension=24
context=internal-phones
label=Yealink Büro
group=UG
server=1
customastdb=CF/24
queuechannel=SIP/24_yeal38g|Penalty=0|MemberName=24@local-agents

Update: it seems when the SIP peername is not SIP/12 but e.g. SIP/12_xxx then it works.

nicolas

What happens internally is what I said. If the queue member does not match the button in fop2, or the extension/context if its a local channel, then it won't be renamed. In the other hand, if the queue member has a name defined, and the channel/device matches the fop2 button definition, or the extension@queuecontext of a local queue member, then it will be renamed.

Best regards,