No recognition of incoming calls
-
-
-
What is the output from /usr/local/fop2/autoconfig-buttons-freepbx.sh ?
If you do not see button activity, the button definitions are wrong or the manager is not responding to events at all. You can also run fop2_server in debug mode: /usr/local/fop2/fop2_server -X 15
Best regards
-
Output of autoconfig-buttons-freepbx.sh is normal.
However /usr/local/fop2/fop2_server -X 15 generates: Can't listen to port 4445
Tried to search for this on forum, but the search seems to be not working at present. Regards this as too common words.
Thanks,
Carlos
-
-
Just to add a little more!
I realised that I needed to stop the fop2 server and restart with -X 15 . Silly me!
I've also noticed that internal calls show:
500 Carlos
Line1 device
Line2 inactive501 Mobile
Line1 501
Line 2 inactivewhen calling extension 501 from extension 500
What's the "device" mean?
Carlos
-
-
Hi Nicolas,
After some more experimentation, here are my finding:
Trixbox 2.6 + FOP 2.11
Inbound route straight to extension:
FOP2 shows calling number at extension, Calling number and name shown on pop-up.Inbound route to queue:
FOP2 shows calling number on all extensions which are queue agents. Shows calling number and name in queue. Shows calling name and number in pop-up.Trixbox 2.8 + FOP 2.11
Inbound route straight to extension:
FOP2 shows [u:3bfxb89z]called[/u:3bfxb89z] extension number at extension e.g ext 502 shows 502 calling. No pop-up.Inbound route to queue:
FOP2 shows [u:3bfxb89z]called[/u:3bfxb89z] extension number at extension. Shows [u:3bfxb89z]calling[/u:3bfxb89z] number [u:3bfxb89z]and[/u:3bfxb89z] name in queue. No pop-up.
(Each extension shows own number as calling number e.g. ext 511 shows 511 as calling number, 512 shows 512)I can only assume that FOP2 must be being given the calling number as it appears in the queue, but why isn't the extension showing the calling number (only shows own extension number calling) and there's no pop-up?
Thanks
Carlos.
-
Carlos, popups will not show if the callerid matches the extension, as you do not want self popups (as when doing originations). I have other reports of FreePBX using a RINGGROUP number as the called number, and not the callerid of the person calling. That change is in the ringgroup macro for some freepbx version. And it is freepbx that uses that callerid and fop2 just displays it. I do not have reports of this behavior on anything but ringgroups.
If you can provide me access to your trixbox 2.8 I can take a deeper look, but it is a dialplan issue, not a fop2 issue...
Best regards,
-
-
-
-
-
-
Hi Nicolas,
Here's a snip from the screen:
http://www.ripon.org/carlos/screen.jpg
showing the incoming call to the queue, but each extension showing its own calling number.
Carlos
-
Nicolas,
Seem to be getting somewhere at last. If an agent logs into a queue via FOP2, then the CALLING number is shown as ringing the agent's extension and hence the pop-up works.
If an agent logs into a queue via (queue number)* e.g. 803* or the agent is placed permanently into the queue via trixbox static agents, then it's the AGENT number which is shown as ringing the agent's extension, and hence no pop-up.
Any thoughts?
Carlos
-
Not sure how is the agent-add macro doing its thing, you should look at the "queue show" output from the asterisk cli to see how are the agents added, and if they use Local/XXX@YYY, verify that the button configuration use extension=XXX and queuecontext=YYY. You can see that by running autoconfig-buttons-freepbx.sh. There must be a coincidence between extension/queuecontext in both the queue member and the button config so fop2 can match the inbound call as a queue member call.
-
Hi Nicolas,
Just had a further look and Trixbox adds to the queue:
member=Local/500@from-internal/n,0
when adding a static member. If I change this to:
member=SIP/500
then it works as expected. At least until Trixbox is relaoded and overwrites the change.
Tried "queue show" and it gives Local/500@from-internal/n in both v2.6 and 2.8
Also autoconfig-buttons-freepbx.sh gives:[QUEUE/803]
type=queue
extension=803
label=Sales
context=ext-queues
queuecontext=from-internal
extenvoicemail=*again in both v2.6 and 2.8
To add yet more, setting the destination of an inbound route directly to an extension results in the CALLED extension being displayed against the extension in FOP2.
Carlos.
-
Look at the extension configuration in the buttons.cfg file, not the queue configuration, and see if they have the queuecontext set and to what value it is set.. it should be "from-internal", but maybe it is set to "from-queue". If that is the case, you must change the autoconfiguration button script to use the correct queuecontext for your setup.
-
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