Ticket #5274 (closed Bugs: invalid)

Opened 2 years ago

Last modified 1 year ago

Queues Sip & Local Channel Bugs

Reported by: Mr-School Assigned to:
Priority: major Milestone: 2.10
Component: Queues Version: 2.9-branch
Keywords: channel sip missed calls Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

Taken from this thread: http://www.freepbx.org/forum/freepbx/users/queues-sip-local-channel-bugs

I am encountering the same behavior as discribed there. I am using PIAF 1.7.5.5 with Asterisk 1.8.5.0 and FreePBX 2.9.0.7.

Noticed quite a few peculiarities when using either SIP or Local Channels in Queues.

I am using Elastix 2.03 with Asterisk 1.6.2.13 and Freepbx 2.7.0.10

Local Channels: If I use Local Channels in Queues setup through FreePBX, the phones aren't send SIP Cancel Reason so they all log a missed call when a call is answered on another phone. If I use SIP channels (S200 in freepbx) this works OK. Queue calls are only logged as a missed call when unanswered or time out. If answered elesewhere this doesn't get log on the phone, Also with Local channels if a device is turned off, it remains in the queue as available to take calls (Not in use). When using SIP channels a switched off device is marked unavailable which is better behaviour.

SIP channel issues: WIth Sip channels, call forwards are totally ignored in queues even if agent restrictions are set to Call as Dialled. This works OK with local channels, Alert-Info for distinctive ring is not passed with SIP Channels and phones just use their default ring. This works fine with Local Channels.

So It looks like both SIP and Local channels have their own issues! Are there any fixes for any of the above issues?

Regards

Change History

02/18/12 22:57:38 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to invalid.

Closing this ticket as these issues are reported against 2.7 which is not supported, nor is 2.7 supported on Asterisk 1.8. Some of these issues probably remain in 2.9 and 2.10 while others do not. The State information is addressed in 2.9 and 2.10 and some earlier releases with specific advanced settings enabled. The SIP Channel Agents are a very advanced and "use at your own risk" capability with know limitations.

As far as the reason code assuming you are referring to the 'c' Dial Option, if you want to file a specific bug about that using FreePBX 2.10 and some very specific scenarios we would be happy to look into it. There seems to be a lot of limitations with the 'c' Dial Option in general which is why it has not been really integrated into FreePBX yet, but we are open to have a closer look and where it makes sense to try to get it working we can review.

Closing as invalid given the versions this was tested and reported on.