Setting up Cisco Phone with Obitalk - Sooo close!

[wdwms]

Greetings all!
I've been following some of azrobert's posts, specifically this one: http://www.obitalk.com/forum/index.php?topic=11592.msg76226#msg76226

I've successfully configured my obi200 to accept SIP connections for calls, specifically a soft phone (MicroSIP) and I can confirm outgoing works ( haven't tackled incoming yet).

I have a Cisco 7965 phone i'd like to get working, i've updated the firmware and setup a tftp server so it can get its config, which seems to work fine. However when placing calls I get:

11-26-2018   12:18:02   Kernel.Debug   192.168.2.124    SIP DLG reject: 486
which results in the fast busy as soon as the first number is pressed on the keypad.

Is this an authorization issue?

Thanks!

[wdwms]

I should add that yes I have converted the Cisco phone to SIP.

[drgeoff]

I should add that yes I have converted the Cisco phone to SIP.

AIUI a SIP phone will not immediately attempt to send a message to the SIP server when the first digit is dialled.  It waits until it thinks the user has dialled the complete number and then sends that as part of a SIP INVITE message.  Thus I think what you report is not caused by an authorisation issue.

[ProfTech]

Wild guess. I seem to remember a field in the 100/110 something about "accept dialog". Does a similar configuration option exist is the 200?

[zapattack]

Is the Dial Plan default?
Something like
(xx.|*xx.)
If there is a Dial Assist, it should probably be off.

[wdwms]

Obi200
X_AcceptDialogSubscription
Not sure what that would do.

Regarding the dial plan, its default, i don't have a dial plan on my tftp server, should i do that?
For Dial assist, you mean in Cisco or Obi?

[wdwms]

Ok i'm getting somewhere, i configured a dialplan.xml and now I can dial out.. however when the person on the other end answers it just hangs up...

no idea where to look next..

[wdwms]

Ok so i'm seeing the following after the call is established via an INVITE and then an ACK (ignore xxxxxx, blanking out the number.)

RTP:Start->c0a80291:24882(80 160);0;0;0:0:0;0(46)

RxFrom:c0a80291:49214

BYE sip:Obi200@192.168.2.124:5063 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.145:5063;branch=z9hG4bKf40a9870
From: "AeroPro" <sip:OBi200@192.168.2.124>;tag=8478ace7aa950002faebdeab-613b948c
To: <sip:xxxxxxxxxxx@192.168.2.124>;tag=SP4f2fb5676db6b085e
Call-ID: 8478ace7-aa950002-da38dcfd-ebcc6432@192.168.2.145
Max-Forwards: 70
Date: Wed, 16 Dec 2009 09:22:58 GMT
CSeq: 102 BYE
User-Agent: Cisco-CP7965G/8.5.3
Content-Length: 0

It looks like to me that the Obi is hanging up.. what would cause a BYE to happen immediately after connecting?

[zapattack]

This is exactly the same behaviour if connecting
from a 110 which connects to the 200 and GV.
I have a  Cisco 525 directly on the 200 and no problems.
Using phone jack on 200, no problem.
Calls originating on 110 drop on answer (but you can hear recordings).