[Date Prev][Date Next][Thread Prev] [Thread Next][Date Index] [Thread Index]

Thomson ST2030 not working with FOP


  • From: Erik De Decker <erik.dedecker@xxxxxxxxxxxxx>
  • Date: Mon, 01 Oct 2007 08:07:28 +0200
  • Mailing-list: contact operator_panel-help@lists.house.com.ar; run by ezmlm

Hi,

FOP is an excellent application.

I was tying to make FOP work a Thomson ST2030 phone, while I found out that instead of accepting an SIP INVITE from FOP it refuses and sends a SIP 480 (not available messages)

My other phones AT-530 work perfect with FOP. I compaired the ST2030 behavior with a the CTI TAPI Snap application. The difference is that Snap sends a SIP INVITE with a FROM ID (*80@xxx) different from the ST2030 telephone account (SIP:20@xxx).

INVITE sip:20@xxxxxxxxxxxxxxx:5060 <http://www.snapanumber.com/>;user=phone SIP/2.0
From: "20 Phone 1" <sip:20@xxxxxxxxxxxxx>;tag=as79e2b01e


The ST2030 responds with a SIP 480 message = non-available, the phone does not ring and the call remains unanswered ! (the action fails)

Snap sends:

INVITE sip:20@xxxxxxxxxxxxxxx:5060 <http://www.snapanumber.com/>;user=phone SIP/2.0
From: "Erik" <sip:*80@xxxxxxxxxxxxx>;tag=as2946aa3c


(*80 is the number dialed from Snap TAPI)

Here the ST2030 starts ringing and the action succeeds.

I am not used to Perl and the code is quiet massive to do a frontal attack :-) I would like to modify the behavior of FOP to avoid sending From: "20 Collaborateur 1" <sip:20@xxxxxxxxxxxxx>" to SIP/20 ! I guess it would be better to set the action in the From field of the SIP INVITE message.

Is this possible ?

Many thanks in advance,

Erik
Follow-Ups from:
Nicolas

[Date Prev][Date Next][Thread Prev] [Thread Next][Date Index] [Thread Index]