r792 Honeycomb 3.0.1 (Xoom) Cannot Access Dialpad

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Install r792
2.Dial a number and allow it to connect
3.After a very short (10 seconds roughly) time the ability to select the 
dialpad is gone

What is the expected output? What do you see instead?
Csip is going into a weird locking mode on my tablet where I cannot access the 
dialpad.  I didn't realize this until today when I called my credit card 
company.

What version of the product are you using? On what operating system?
r792 on Android 3.0.1

Please provide any additional information below.
When I cannot access the dialpad the phone will still allow me to hang up by 
dragging the icon.  Also strangely the answer icon is there and movable also.  
I think this has to be a software bug since the phone is already in a call. 

Separate Issue:

In previous releases (and this one) when I can get to the dialpad it didn't 
seem to want to create the inband DTMF.  I also tried SIP Info and that didn't 
work also.  I'm thinking there could be multiple issues here.  If you need me 
too I'll open a separate ticket for this issue however I think (guessing) that 
they are connected. 

Original issue reported on code.google.com by austin.t...@gmail.com on 13 Apr 2011 at 11:49

[GoogleCodeExporter]

I guess that there is no proximity sensor on the xoom.

In fact, if you have a close look to the "answer" icon, it's not the answer 
icon !! It's an unlock icon ! It allow to unlock this lock screen.

This lock screen is useful on phones without proximity sensors to avoid you to 
do unwanted actions. So if you simply slide to unlock the right handle, you'll 
be able to do actions on the call screen again :) (timeout is about 5 s the 
first time and then after unlocking or pressing a dtmf button 10 sec)

As for the dtmf problem, did you try auto mode or inband mode? 
SIP info is supported by few sip provider -
The auto mode tries RTP first and if server does not like that fallback to 
inband generation. Most of the time when there is a problem it is cause the sip 
server claims to support RTP but actually do not. In this case pjsip does not 
fallback to inband generation and your dtmf code (sent using RTP) is never 
transmitted by your sip server. So usually in this case, forcing the "In band 
generation" mode helps.
Or could be duplicate of issue 863. 

Original comment by r3gis...@gmail.com on 13 Apr 2011 at 12:17

• Changed state: Invalid

[GoogleCodeExporter]

I have tried forcing in band (also rtp/sip) and it doesn't seem to work. On my 
old phone I was able to hear the dtmf as I dialed and when I tested with this I 
wasn't able to hear the tones.  This is after connecting the call.  When 
dialing in the dialer (before call connection) it does dtmf.

I am using callcentric for all of my testing.

You were 100% correct on the unlock.  My old phone had the proximity sensor.  I 
just didn't look close enough.  It works as expected once I unlocked it ;-) 

Original comment by austin.t...@gmail.com on 13 Apr 2011 at 3:15