[PATCH 2/4] Fix: No need to put active call on hold

[Denis Kenzior]

Hi Zhenhua,

> First, call->status should be 1 stead of 2 in the loop. Second,
> it's incorrect to set status to hold because later callheld=1
> will swap call status back. So active->hold->active again is
> not correct.

Unfortunately we do need to put the calls on hold otherwise the core might 
pick the wrong call as the 'dialed' call.  Instead we now ignore the 
callheld=1 indicator in this situation.  Let me know if this still doesn't fix 
this issue.

Regards,
-Denis