Okay, I registered my 100 with obitalk and tried calling the valcom PA with obiapp. I was picked up by the attendant, so I pressed one to be put through to the phone. I got dead air with nothing on the speaker. Testing it with a normal phone in the ph port passes the call through just fine.
So below, I included the call history. You can see that when I call with obitalk that the AA answers, and I am then connected to the phone1 port. Not even a second after I'm transferred, the device hangs up.
The result is the same from extension 310 (call 5). Looking at asterisk logs, the obi sends a 486 "Busy Here" back to the server when the "UseForPagingOnly" option is set. If it is unset, the loudspeaker rings obnoxiously, but obviously never picks up.
-----------------------------------------------
Here is the call history for reference:
Call 1 09/05/2013 15:33:32
Terminal ID AA1 PHONE1
Peer Name
Peer Number 0
Direction Outbound Inbound
15:33:32 New Call
15:33:33 New Peer: OBiTALK1(290******) Transfer Target, Continue At Ref:8382
Call 2 09/05/2013 15:33:23
Terminal ID OBiTALK1 AA1
Peer Name
Peer Number 290******
Direction Inbound Inbound
15:33:23 Ringing
15:33:27 Call Connected
15:33:33 Call Transferred Transfer to PHONE1, State=ringing, Ref=8382
15:33:33 End Call
Call 3 09/05/2013 15:32:45
Terminal ID AA1 PHONE1
Peer Name
Peer Number 0
Direction Outbound Inbound
15:32:45 New Call
15:32:46 New Peer: OBiTALK1(290******) Transfer Target, Continue At Ref:12826
Call 4 09/05/2013 15:32:23
Terminal ID OBiTALK1 AA1
Peer Name
Peer Number 290******
Direction Inbound Inbound
15:32:23 Ringing
15:32:27 Call Connected
15:32:46 Call Transferred Transfer to PHONE1, State=ringing, Ref=12826
15:32:46 End Call
Call 5 09/05/2013 15:27:09
Terminal ID SP1 PHONE1
Peer Name Shipping & Receiving
Peer Number 310
Direction Inbound Inbound
15:27:09 Ringing
15:27:10 End Call