Undefined index: pin
-
I wasn't aware about this procedure. When I execute debug mode, I still have "unable to initialize libusb: -99" error but it generates logs well.
I have attached the result in this reply for you to get an overview.It's a good news. I will be happy to test this beta together. I'm available all the day so I'll try to contact you as soon as the live help will be online.
What I saw in logs seems correct but may be I'm missing something.
I also corrected the warning.
Thanks very much for all.
ps : I noticed than buttons 'dial' and all the others doesn't works too. Think it's linked with the fact that status isn't modified.
Regards,
-
-
Hi,
Sorry for my late.
I observed it doesn't afefct anything too.
Starting from your point, I carefully observed the configuration of my file and I had not seen some of my buttons do not have the correct syntax. [SIP/XXXX]
After modification, it works as agreed.
I can continue the preparation of the module with queues.
Thank you very much for your help.ps: if it still stands, I am always available to see together for the beta for elastix 3.
-
FOP 2.29 is out in beta, including the fop2manager with support for elastix 3 auto configurations. I have not had the chance to actually try it in production, having only access to elastix db schemas and not much else.
http://download.fop2.com/fop2-2.29-centos-i386.tgz
http://download.fop2.com/fop2-2.29-centos-x86_64.tgz -
I tried this new version. It's a newer implementation, seems all buttons are taken directly from database. But already have some troubles : my users have been erased and even I creat the ame user, I don't find my buttons back in the panel.
For the moment I prefer to stay on the 2.28. I keep this new version for the future.However, I found another problems in the panel when I'm logged with an user.
When I select an extension button and click on Dial button, it calls only my extension and I can't dial another one.
Also, I defined a queue, it works fine, I declare the button as [QUEUE/...] but don't see any call in wait state on the button and I have Agents and Waiting call at 0.Thanks for your help.
-
Hi,
Multi tenant users and buttons are handled differently in the database than single tenant users, that is probably why your users were removed. Multi tenant has another side effect, you must login as that particular tenant to fop2 using the ?context=domain.com directive in order to log in. In my tests, the fop2 manager worked fine in this scenario, but no tenant buttons won't show up. In any case, you can try to catch me on the live help if you can give me access to your system to work on it directly.
As for your problems, when you dial, your phone always rings first, once you pickup, then it will dial the destination number. So, there is no problem there at all. Just answer and the destination number will be dialed.
Regarding queue buttons, the queue name is incorrect if you do not see anything, or it could also be that you did not define an extension=xxx and context=yyy to the [QUEUE/xxx] button definition.
Best regards,
-
I'll try all of this later and come back to you to look at this together. For the moment I've downgraded on 2.28 and focus on it. Thanks.
I try this this morning and it works as you described to me. Didn't think the scenario worked like this. Thanks again.
My case is a little specific, may it cause some conflict. I explain it in more details. I have a standard number SN and a temporary number TN, both are extensions, SN is registered on a phone and not TN. I use this TN from others extensions to put the call in the queue which will call SN. Here are my conf files :
extensions_custom.com :
exten => 5555,1,Answer()
exten => 5555,n,agi(googletts.agi,"Please wait.",en,any)
exten => 5555,n,Queue(hotline,td,,,30)
exten => 5555,n,Voicemail(SIP/5845_myorg.fr)
exten => 5555,n,Hangup()queues.conf :
[hotline]
musiconhold=default
strategy=ringall
timeout = 20
retry = 15
maxlen = 0
wrapuptime= 15
joinempty = no
leavewhenempty = yes
eventwhencalled = yesmember => SIP/5845_myorg.fr
buttoncall.cfg :
[others extensions]
...[QUEUE/5555_myorg.fr]
type=queue
label=Support
extension=5555
context=myorg.fr-from-internal[QUEUE/5845_myorg.fr]
type=queue
label=Support2
extension=5845
context=myorg.fr-from-internalFrom here, the queue works fine, several calls go in queue but my buttons on the panel don't change state.
As you can see, I created 2 queue buttons for both extensions SN adn TN to see which one is effective.
Did I miss something ?Thanks for your help.
-
-
Hi Admin,
I have another question about Queues in fop2 please.
I would like to know when a call is in queue, how to transfer it from the caller to another extension from the button in the interface ?
I tried to select the button then click on blind transfer but it doesn't work well.Thanks for your reply.
-
Not sure what you mean exactly. If you want to move a waiting call out of a queue, you have to drag it out to another extension (enableDragTransfer=true in presence.js). However, if you do that, the call will be marked as ABANDONED for queue reporting applications, so use with care if you need statistics about them.
-
-
There are some issues when your queue members are Local channels where a transfer fails, but that is an asterisk issue as the command that fop2 sends to the manager is correct. Try an attendant transfer instead and see how it performs, you can hangup as soon as you do the attendant transfer and it will behave similar to a blind transfer.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login