Answered elsewhere not working on queues - S500

Hi,

We have a queue and have 6 Sangoma S500 phones in the queue. We have the Answered Elsewhere option enabled on the queue. However even if a call is answered elsewhere all the other 5 phones state there’s a missed call.

it is a new install of the FPBX using the ISO and has all the latest updates installed and latest firmware installed on the phones as of the time of this post.

Does anyone have any clues as to why i’m seeing this behaviour?

Kind Regards,

Jimmy.

Sounds like a bug - have you submitted a ticket too?

Hi,

No i haven’t it wanted some confirmation it’s a bug before i go and file one.

is this happening on other peoples systems?

thanks

jimmy

Tested now on FreePBX 13/Asterisk 13 not happening by us.
Queues: 13.0.34.7
Queues Pro 13.0.27

It sounds like a problem a few people were reporting a few months ago, but the fact that the option that’s supposed to tell the phones they didn’t miss a call is not working sounds buggy.

Make sure all of your firmware and modules on the PBX are up to date. You may also want to try the “Edge” track for the queue module, just in case it’s fixed there but not in the main track.

Hi,

Just tried the edge module and the phones ring but the calls get terminated when picked up. I will wait till the next stable module gets released.

I think you need to post some logs. There are a couple of things that could do this, including codec mismatches.

Yes i think so too. It’s a production system so will have to get some downtime booked in.
I’ve been trying a few things to get the Answered elsewhere feature working however nothing seems to work.

Where can I submit tickets for the firmware of the Sangoma phones? FreePBX sends a correct status, but the phone firmware obviously doesn’t pay attention to this. The counter for unanswered calls is increased continuously.

<— Transmitting SIP request (490 bytes) to UDP:999.999.999.86:5060 —>
CANCEL sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 999.999.999.10:5060;rport;branch=z9hG4bKPj17aed2db-b938-4f2f-a17d-94e07d085895
From: “XXXXXXXXXXXXXXXXXXXX” sip:[email protected];tag=fd2b9cc4-94c2-40e6-a164-f7938a2d3225
To: sip:[email protected]
Call-ID: 9d6f41d6-ef9c-423c-888f-a523073617ad
CSeq: 28362 CANCEL
Reason: Q.850;cause=26
Reason: SIP;cause=200;text="Call completed elsewhere"
Max-Forwards: 70
User-Agent: FPBX-14.0.1.36(13.18.5)
Content-Length: 0

<— Received SIP response (504 bytes) from UDP:999.999.999.86:5060 —>
SIP/2.0 487 Request Cancelled
Via: SIP/2.0/UDP 999.999.999.10:5060;rport=5060;branch=z9hG4bKPj17aed2db-b938-4f2f-a17d-94e07d085895
From: “XXXXXXXXXXXXXXXXXXXX” sip:[email protected];tag=fd2b9cc4-94c2-40e6-a164-f7938a2d3225
To: sip:[email protected];tag=526fd46218ebea2
Call-ID: 9d6f41d6-ef9c-423c-888f-a523073617ad
CSeq: 28362 INVITE
User-Agent: Sangoma S500 V2.0.4.43
Allow: INVITE, ACK, UPDATE, INFO, CANCEL, BYE, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, PRACK
Content-Length: 0

<— Received SIP response (489 bytes) from UDP:999.999.999.86:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 999.999.999.10:5060;rport=5060;branch=z9hG4bKPj17aed2db-b938-4f2f-a17d-94e07d085895
From: “XXXXXXXXXXXXXXXXXXXX” sip:[email protected];tag=fd2b9cc4-94c2-40e6-a164-f7938a2d3225
To: sip:[email protected];tag=526fd46218ebea2
Call-ID: 9d6f41d6-ef9c-423c-888f-a523073617ad
CSeq: 28362 CANCEL
User-Agent: Sangoma S500 V2.0.4.43
Allow: INVITE, ACK, UPDATE, INFO, CANCEL, BYE, OPTIONS, REFER, SUBSCRIBE, NOTIFY, MESSAGE, PRACK
Content-Length: 0

<— Transmitting SIP request (425 bytes) to UDP:999.999.999.86:5060 —>
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 999.999.999.10:5060;rport;branch=z9hG4bKPj17aed2db-b938-4f2f-a17d-94e07d085895
From: “XXXXXXXXXXXXXXXXXXXX” sip:[email protected];tag=fd2b9cc4-94c2-40e6-a164-f7938a2d3225
To: sip:[email protected];tag=526fd46218ebea2
Call-ID: 9d6f41d6-ef9c-423c-888f-a523073617ad
CSeq: 28362 ACK
Max-Forwards: 70
User-Agent: FPBX-14.0.1.36(13.18.5)
Content-Length: 0

I have created a support ticket.

Post the solution here please when fixed. Tx

Any news on this, I have 3 deployments doing this now.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.