[asterisk-bugs] [Asterisk 0012324]: chan_skinny call control problems with 7921

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12324 
====================================================================== 
Reported By:                sbisker
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   12324
Category:                   Channels/chan_skinny
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-03-28 12:33 CDT
Last Modified:              2008-10-06 18:46 CDT
====================================================================== 
Summary:                    chan_skinny call control problems with 7921
Description: 
First Problem: chan_skinny doesn't respect callwaiting=no flag in
chan_skinny.conf

This is for the 7921G phone.  7920 phone works as expected.

Example:  (All phones chan_skinny with 1 line)

phone1 -> phone2
phone2 answers
phone3 -> phone2
phone2 rings
if phone2 answers, then phone2 can hear both phone1 & phone3, but they
can't hear each other.


Second Problem:  If a 7921G skinny device calls itself, the phone
continues to ring until the battery is removed.




====================================================================== 

---------------------------------------------------------------------- 
 (0093262) DEA (reporter) - 2008-10-06 18:46
 http://bugs.digium.com/view.php?id=12324#c93262 
---------------------------------------------------------------------- 
I cannot 100% prove this, but I think part of the issue stems from the
fact
that we always set one of the call instance/reference values to 00.

I found that one of the status packets has the call number set, but we do
not
set it and it is always 00.  A simple increment/decrement will not work
to
track it:
    1st Call- 01
    2nd Call- 02
    3rd Call- 03
Hangup 2 and make another call now we have:
    1st Call- 01
    2nd Call- 02
    3rd Call- 02

An array of call instances seems wasteful, and I have not had time to
look into a bitmasked instance tracker.

We do set call instance and line reference values properly, but I am
starting
to think the phones may also need the correct call number to track the
calls
state.

I will re-run the packet captures to see which response packet needs the
tweak 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-06 18:46 DEA            Note Added: 0093262                          
======================================================================