SIP Connector V2.50.2.3 sent to the updater

[stipus]

I just sent version V2.50.2.3 of the SIP Connector plugin to the updater. It should be available shortly.

Change log:

- The dll Stipus.Sipxtapi.Core.dll doesn't need the Visual C++ 2005 SP1 Runtime anymore.

- You can now select active codecs from the Configuration interface.

Default codecs are: PCMU / PCMA
Optional codecs are: GSM, iLBC, SPEEX, SPEEX5, SPEEX15, SPEEX24

Best regards,

[sigbjorn]

I have tried the new update, and HomeSeer reports: Cannot find the file C:\Program Files\HomeSeer HS2\interop.dll when starting.

[stipus]

I don't understand what could be the cause of this problem, as the plugin doesn't use nor modify this file.

The plugin comes with a file named interop.speechlib.dll that should be in the HS2 directory.

Does HomeSeer start if you rename this file to something else ?

[sigbjorn]

Could maybe have something to do with the Media Player plugin. I installed the update for this at the same time I did the update of SIP connector. Anyway, I found a backup of this file and now everything is up and running again.

[kennesaw10]

Problem with HS2 Beta 2.3.0.112

I upgraded HS to 2.3.0.112 and was still on the Sip Connector version 2.40.2.2 with out issue. I then went to the updater and saw that version 2.50.2.3 was available and downloaded it.

I am now unable to get the Sip Connector to run. I get an error as follows:

7/21/2009 1:46:17 PM  - SIP Connector - SIP Connector 2.50.2.3 Standard Edition Copyright 2006-2009 stipus@stipus.com
7/21/2009 1:46:17 PM  - Plug-In - Initializing Plug-in: SIP Connector
7/21/2009 1:46:18 PM  - SIP Connector - Initializing SipxTapi. Primary identity= TcpPort=5060 UdpPort=5060 TlsPort=5061 RtpPortStart=9000 BindAddress=0.0.0.0 UseSequentialPorts=False
7/21/2009 1:46:18 PM  - SIP Connector - ContactId=1 Type=Local TransportType=udp Interface={70F83463-2968-45BF-B4E4-66E4ABAAD097} Ip=192.168.1.103 Port=5060
7/21/2009 1:46:18 PM  - SIP Connector - ContactId=2 Type=Local TransportType=tcp Interface={70F83463-2968-45BF-B4E4-66E4ABAAD097} Ip=192.168.1.103 Port=5060
7/21/2009 1:46:18 PM  - SIP Connector - ContactId=3 Type=NatMapped TransportType=udp Interface={70F83463-2968-45BF-B4E4-66E4ABAAD097} Ip=76.17.97.174 Port=5060
7/21/2009 1:46:18 PM  - SIP#Joes - Registering HomeSeer1 <sip:2029@>. LocalContactId=0
7/21/2009 1:46:18 PM  - SIP#Joes - Error: RegisterFailed Cause: RegisterFailedNotAuthorized
7/21/2009 1:46:21 PM  - SIP#Joes - Error: Timeout Registering line !
7/21/2009 1:46:21 PM  - Error - Error loading line list from config file !Exception of type 'Stipus.SipXtapi.SipxException' was thrown.
7/21/2009 1:46:21 PM  - Error - Initializing interface: SIP Connector->1
7/21/2009 1:46:21 PM  - Plug-In - Finished initializing plug-in SIP Connector

Not sure where to go from here. The 2 extensions are not registering with my PBX now.

In addition, when I click on "config" from the interfaces page, I get no screen. There is also no plug-in for Sip-Connector that shows anywhere other than on the interfaces screen.

[stipus]

The best way to debug such a problem is to install wireshark on the HomeSeer PC and capture port 5060 while HomeSeer starts, or use tcpdump on the Asterisk PC and capture the same port.

Send the capture file to stipus at stipus dot com, and I'll have a look.

Best regards,

[stipus]

I can see the following in the email:
Registering HomeSeer1 sip:2029@.

Did you edit/remove the ip address yourself when you sent the message ?

[kennesaw10]

I can see the following in the email:
Registering HomeSeer1 sip:2029@.

Did you edit/remove the ip address yourself when you sent the message ?

No I did not. I have precise security on my firewall and Asterisk server.

[stipus]

ok but in the real homeseer log, do you see registering 209@ or is there the ip address of your asterisk server after the @

[kennesaw10]

ok but in the real homeseer log, do you see registering 209@ or is there the ip address of your asterisk server after the @

I've restored to the previous version of HomeSeer and SipConnector. As I recall, it simply said "registering 2029." I actually register 2 extensions and had no problems prior to this release of both Homeseer and SipConnector.

[stipus]

Could you install wireshark on your HomeSeer PC and capture port 5060 while HomeSeer is registering the line ?

[stipus]

I just restarted my HomeSeer, and when registering the line I got the message

25/07/2009 11:28:26 - SIP Debug - SIP#B3G: Registering stipus [siphone_number@domain_realm]. LocalContactId=0

Please check that the DomainRealm parameter is set for your line. It should be set to the IP address of your asterisk server.