Installed FOP2 2.11 on Trixbox v 2.8.0.5 and am getting no recognition of incoming calls in FOP2. I've used the visual phonebook database as a lookup source for Trixbox and that's picking the correct record to display on the phone. No SQL query originated by FOP2 though. Extension simply shows inactive on both lines.

Tried to compare this to a working setup using Trixbox 2.6 and can't see any difference in my configuration. Any ideas on what's going wrong or how I can investigate further?

Thanks

Carlos.

Hi,

Yes. Received "Connection to manager OK!"

Carlos

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

Sorry, forgot to say that netstat -nta gives:

0.0.0.0:4444 0.0.0.0:* LISTEN
0.0.0.0:4445 0.0.0.0:* LISTEN

as I changed FOP1 to port 4444

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 inactive

501 Mobile
Line1 501
Line 2 inactive

when 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.

Hi Nicolas,

Thanks for the offer, but I won't put you to trouble just yet ;-)

Do you mean a difference in the extensions.conf file?

Carlos.

Hi Nicolas,

Done a "diff" on the freepbx core modules, extensions.conf, sip.conf, iax.conf, and features.conf, between the Trixbox 2.8 (not working) and the Trixbox 2.6 (working) versions. Both exactly the same!

Any other thoughts?
Carlos.

Hi Nicolas,

I'll try and get a report from fop2_server -X 15 for you if this will help guide you to the issue.

Carlos

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

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.