Help on the SIP configuration for a standalone 8028

Cinnamon0957 · Post by **Cinnamon0957** » 29 Sep 2023 20:32

Hello, everyone. I inherited an Alcatel-Lucent 8028 Premium DeskPhone from a closed business and am trying to make it work. I am new to IP telephony, and this seemed like a great way to learn. I have SIP services through my internet provider and hoped to get the phone working with their servers.

I have been working on this for several weeks and grasping most concepts. Here is where I am now in the learning curve:

Known working:
- POE and network connectivity
- DHCP server providing static address
- TFTP server providing requested files over UDP

Not working or missing:
- lanpbx.cfg for SIP configuration
- noesip8028N-header
- noesip8028N
- datsip8028N-header
- datsip8028N

Unknown correctness:
- sipconfig.txt
- sipconfig-xxxxxxxxxxxx.txt

Searching through the internet and referencing the SIP phone installation guide for the 4008/4018 , the instructions say,"‘lanpbx.cfg’ file template: use a text editor to create a very simple file with this contents:"

Code: Select all

APPLICATION_TYPE=APPL_SIP

Various searches on the internet confirmed that this was a valid file for the 4038 also. If I place this file on the TFTP server, it is downloaded, and then the phone screen reports, "1/5 network start, 2/5 network setup, 3/5 config download, bad file content." So, I assume this is not the format the 8028 uses for its SIP configuration.

If I use a format similar to the one referenced here, the phone gets further into the boot process but is in NOE mode, judging from the requests for startnoe* files from the TFTP server.

I can get into the configuration menu on the phone by sequentially pressing the (i) and # keys on startup. If I manually configure the mode for SIP through the Soft Infos menu, the TFTP network traffic hints to header files and binaries that I don't have. Specifically noesip8028N-header, noesip8028N, datsip8028N-header, datsip8028N. These files seem very similar to the ones referenced here, but those are clearly for the 4028 and not the 8028. On the off-chance that the files are compatible, I downloaded and renamed them noesip8028N-header, noesip8028N. Unsurprisingly, after downloading these binaries, the phone reboots and returns to NOE run mode. Here is the output from tcpdump with the phone manually placed into SIP mode.

Code: Select all

06:41:27.909475 IP 172.16.132.1.bootps > 172.16.132.50.bootpc: BOOTP/DHCP, Reply, length 300
06:41:27.910521 ARP, Probe 172.16.132.50, length 46
06:41:28.415044 ARP, Announcement 172.16.132.50, length 46
06:41:29.422755 ARP, Request who-has 172.16.132.1 tell 172.16.132.50, length 46
06:41:29.422852 ARP, Reply 172.16.132.1 is-at 00:30:48:be:6a:81 (oui Unknown), length 46
06:41:29.423021 IP 172.16.132.50.1024 > 172.16.132.1.tftp: TFTP, length 50, RRQ "lanpbx.cfg" octet timeout 5 blksize 1428 tsize 0
06:41:29.423631 IP 172.16.132.1.20538 > 172.16.132.50.1024: UDP, length 34
06:41:29.424600 IP 172.16.132.50.1024 > 172.16.132.1.20538: UDP, length 4
06:41:29.424601 IP 172.16.132.1.20538 > 172.16.132.50.1024: UDP, length 30
06:41:29.425377 IP 172.16.132.50.1024 > 172.16.132.1.20538: UDP, length 4
06:42:44.619567 IP 172.16.132.50.blackjack > 172.16.132.1.tftp: TFTP, length 58, RRQ "noesip8028N-header" octet timeout 5 blksize 1428 tsize 0
06:42:44.620134 IP 172.16.132.1.23224 > 172.16.132.50.blackjack: UDP, length 19
06:42:44.621138 IP 172.16.132.50.cap > 172.16.132.1.tftp: TFTP, length 51, RRQ "noesip8028N" octet timeout 5 blksize 1428 tsize 0
06:42:44.621483 IP 172.16.132.1.23295 > 172.16.132.50.cap: UDP, length 19
06:42:44.622854 IP 172.16.132.50.exosee > 172.16.132.1.tftp: TFTP, length 58, RRQ "datsip8028N-header" octet timeout 5 blksize 1428 tsize 0
06:42:44.623212 IP 172.16.132.1.28290 > 172.16.132.50.exosee: UDP, length 19
06:42:44.624111 IP 172.16.132.50.1028 > 172.16.132.1.tftp: TFTP, length 51, RRQ "datsip8028N" octet timeout 5 blksize 1428 tsize 0
06:42:44.624650 IP 172.16.132.1.65091 > 172.16.132.50.1028: UDP, length 19
06:42:47.205831 IP 172.16.132.50.solid-mux > 172.16.132.1.tftp: TFTP, length 58, RRQ "noesip8028N-header" octet timeout 5 blksize 1428 tsize 0
06:42:47.206363 IP 172.16.132.1.62934 > 172.16.132.50.solid-mux: UDP, length 19
06:42:47.207741 IP 172.16.132.50.iad1 > 172.16.132.1.tftp: TFTP, length 51, RRQ "noesip8028N" octet timeout 5 blksize 1428 tsize 0
06:42:47.208033 IP 172.16.132.1.55075 > 172.16.132.50.iad1: UDP, length 19
06:42:47.209471 IP 172.16.132.50.iad2 > 172.16.132.1.tftp: TFTP, length 58, RRQ "datsip8028N-header" octet timeout 5 blksize 1428 tsize 0
06:42:47.209768 IP 172.16.132.1.50193 > 172.16.132.50.iad2: UDP, length 19
06:42:47.210916 IP 172.16.132.50.iad3 > 172.16.132.1.tftp: TFTP, length 51, RRQ "datsip8028N" octet timeout 5 blksize 1428 tsize 0
06:42:47.211353 IP 172.16.132.1.pconnectmgr > 172.16.132.50.iad3: UDP, length 19

After many hours of internet searches and running the combinatorics, I seem to be running out of leads.

Does anyone have documentation on
- the file specification or example of a lanpbx.cfg for the 8028N or similar model?
- the binary files noesip8028N-header, noesip8028N, datsip8028N-header, and datsip8028N

The phone reports Version NOE 4.52.20. If there is any other version information that is useful to this discussion, please let me know.

If someone has an 8xxx phone running in SIP mode and can do a packet capture, I am happy to pull apart the capture to assemble these parts for my configuration.

Thank you ahead of time. I am pleasantly frustrated and excited to see if I can get this working instead of the phone going to the landfill.