GFI Forums: Kerio Operator » Avaya 1603SW-I. Cant connect.

Home » GFI User Forums » Kerio Operator » Avaya 1603SW-I. Cant connect.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Avaya 1603SW-I. Cant connect. [message #124668]

Thu, 01 October 2015 15:00

TheMouse
Messages: 5
Registered: November 2007

Hi,

I've got large (200+) amount of avaya 1603SW-I phones which actually connected to avaya definiy.
My company are ready to move to kerio operator, we currently testing trial and everything is just greate, except we cant connect this **** phones to it

So, we got :
1. Kerio Operator Trial 2.4.3(4805), running on Hyper-V with single net card.
2. 2 X-Lite softphones (works fine)
3. 2 HW SIP phones (works fine)
4. 200+ Avaya 1603SWI

Avaya phones was upgraded to SIP firmware.
On phones we set ip manually.
It starts, updates, asks for extension, then "Contacting server..." thats all. On pick up we hear default signal but no buttons works at all.

On kerio side i've see no messages ( on logs or anywhere else ) except one in 'warnings'

[01/Oct/2015 15:18:41] asterisk[17519]: WARNING[24708]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:19:42] asterisk[17519]: WARNING[24930]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:20:43] asterisk[17519]: WARNING[25154]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:21:44] asterisk[17519]: WARNING[25373]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:22:45] asterisk[17519]: WARNING[25580]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:23:47] asterisk[17519]: WARNING[25813]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:24:48] asterisk[17519]: WARNING[26022]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:25:50] asterisk[17519]: WARNING[26256]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:26:51] asterisk[17519]: WARNING[26467]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:27:53] asterisk[17519]: WARNING[26703]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:28:24] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:28:27] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:28:53] asterisk[17519]: WARNING[26936]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:29:54] asterisk[17519]: WARNING[27076]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:30:16] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:30:32] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:30:35] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:30:55] asterisk[17519]: WARNING[27423]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:31:57] asterisk[17519]: WARNING[27562]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:32:58] asterisk[17519]: WARNING[27710]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:33:59] asterisk[17519]: WARNING[27865]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:35:01] asterisk[17519]: WARNING[28022]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:36:02] asterisk[17519]: WARNING[28230]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:37:03] asterisk[17519]: WARNING[28378]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:38:04] asterisk[17519]: WARNING[28517]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:39:05] asterisk[17519]: WARNING[28681]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:40:07] asterisk[17519]: WARNING[28990]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:40:12] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:40:52] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:40:55] NetworkManager: Failed to open /sys/class/net/eth0/device/vendor
[01/Oct/2015 15:41:08] asterisk[17519]: WARNING[29264]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:42:09] asterisk[17519]: WARNING[29403]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:43:10] asterisk[17519]: WARNING[29555]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:44:11] asterisk[17519]: WARNING[29701]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:45:12] asterisk[17519]: WARNING[29873]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:46:13] asterisk[17519]: WARNING[30042]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:47:14] asterisk[17519]: WARNING[30277]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:48:15] asterisk[17519]: WARNING[30487]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:49:16] asterisk[17519]: WARNING[30717]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!
[01/Oct/2015 15:50:17] asterisk[17519]: WARNING[30956]: tcptls.c:273 in handle_tcptls_connection: FILE * open failed!

And yes, its because of phone. If phone is not trying to connect - no warnings appear at all.

Any ideas? Rolling Eyes

Sniffed packets in attachment.

Attachment: Untitled.jpg
(Size: 122.71KB, Downloaded 829 times)

[Updated on: Thu, 01 October 2015 15:26]

Report message to a moderator

Re: Avaya 1603SW-I. Cant connect. [message #124669 is a reply to message #124668]

Thu, 01 October 2015 15:27

Filip Jenicek (Kerio) is currently offline

Filip Jenicek (Kerio)
Messages: 968
Registered: September 2010
Location: Sydney

Hi,

it looks as if the phone was connecting using sip-tls. Try to configure it using UDP first.

The phone must be configured with sip username, sip password, ip address of Operator and most likely also with some dialplan (what numbers are allowed to be dialed).

I have no experience with Avaya phones, sorry.

Filip

Report message to a moderator

Re: Avaya 1603SW-I. Cant connect. [message #124672 is a reply to message #124669]

Thu, 01 October 2015 15:56

TheMouse
Messages: 5
Registered: November 2007

Thanks Filip,

I'll try to reconfigure it .. but not sure how, avaya lives in their own life in their own crazy world

Also, have You seen the packet :
TLSv1 Record Layer: Alert (Level: Fatal, Description: Unknown CA)
sip-tls is reason for this one?

Report message to a moderator

Re: Avaya 1603SW-I. Cant connect. [message #124676 is a reply to message #124672]

Thu, 01 October 2015 17:37

TheMouse
Messages: 5
Registered: November 2007

Oh! I made it

Ok, i have wasted a lot of time for that and seems no one knows how to actually do it so :
1. Only 1603SW-I can be used
2. Logoff, reset phone to factory (mute73738#)
3. Download configuration file from ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/46xxsettings/083 02015/46xxsettings.txt
4. Edit it :
SET ENABLE_AVAYA_ENVIRONMENT 0
SET SIPSIGNAL 0
SET CONFIG_SERVER_SECURE_MODE 0
SET SIP_CONTROLLER_LIST <your server ip>:5060;transport=udp
SET SIPDOMAIN <your server FQDN>
SET DNSSRVR <your dns server IP>
5. Download SIP firmware
https://support.avaya.com/downloads/download-details.action? contentId=C2010882049141200_6&productId=P0468
6. Copy config file to firmware files
7. Update firmware by HTTP ( i've used IIS, just paste all firmware contents to www root and enable anon read access )

This also should work with any SIP-based PBX.

Thats all

Works like a charm

))

[Updated on: Thu, 01 October 2015 17:40]

Report message to a moderator

Re: Avaya 1603SW-I. Cant connect. [message #124694 is a reply to message #124676]

Fri, 02 October 2015 08:03

Filip Jenicek (Kerio)
Messages: 968
Registered: September 2010
Location: Sydney

Congratulations!

Just in case you didn't know. Any files that you store to /var/tftp in Operator are accessible using http, ftp, and tftp protocols.

[Updated on: Fri, 02 October 2015 08:03]

Report message to a moderator

Re: Avaya 1603SW-I. Cant connect. [message #149226 is a reply to message #124694]

Tue, 29 December 2020 07:20

maudialfarish
Messages: 1
Registered: December 2020

hi, i know this thread is old. but I need help connecting my 1603SW-i to asterisk based server. i edited the 46xxxsettings file like you suggested, but still stuck at contacting server. could you upload your whole 46xxxsetting parameter? thank you

Report message to a moderator

Re: Avaya 1603SW-I. Cant connect. [message #150278 is a reply to message #124676]

Wed, 22 September 2021 20:28

kate_sm2
Messages: 1
Registered: August 2021

TheMouse wrote on Thu, 01 October 2015 17:37

Oh! I made it
Ok, i have wasted a lot of time for that and seems no one knows how to actually do it so :
1. Only 1603SW-I can be used
2. Logoff, reset phone to factory (mute73738#)
3. Download configuration file from ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/46xxsettings/083 02015/46xxsettings.txt https://swcpoker.club/chinese-poker/progressive-pineapple-of c Elly
4. Edit it :
SET ENABLE_AVAYA_ENVIRONMENT 0
SET SIPSIGNAL 0
SET CONFIG_SERVER_SECURE_MODE 0
SET SIP_CONTROLLER_LIST <your server ip>:5060;transport=udp
SET SIPDOMAIN <your server FQDN>
SET DNSSRVR <your dns server IP>
5. Download SIP firmware
https://support.avaya.com/downloads/download-details.action? contentId=C2010882049141200_6&productId=P0468
6. Copy config file to firmware files
7. Update firmware by HTTP ( i've used IIS, just paste all firmware contents to www root and enable anon read access )

This also should work with any SIP-based PBX.

Thats all
Works like a charm ))

Thank you, I just made a cisco text because of you

[Updated on: Fri, 24 September 2021 14:21]

Report message to a moderator

Previous Topic:	Custom port for Outbound Call Routing SIP Interfaces
Next Topic:	warning log message

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Jun 08 01:58:05 CEST 2023

Total time taken to generate the page: 0.02352 seconds