@sgseidel wrote:
I’m running FreePBX 14.0.13.24 with Current Asterisk Version:13.29.2 . A number of Cisco phones have successfully registered, including some 7911s, a 7961, a 7945, a 7975 as well as a Sangoma S500 and an Aastra 6753i.
Today I attempted to register a Cisco CP-8961 following carefully the clear step-by-step instructions at the link below:
https://www.falconitservices.com/support/KB/Lists/Posts/Post.aspx?ID=290
As the instructions explain, there are five steps:
Although not officially supported, Cisco CP 8961 and 9971 phones can be easily configured for use on FreePBX, Elastix and most Asterisk PBX systems. This step by step guide will provide the provisioning configuration details. The steps are:
- Configuring Asterisk to allow TCP protocol for use on specific IP phones.
- Setting up a DHCP server with TFTP option 150.
- Setting up a TFTP server.
- Configuring extensions in Asterisk.
- Creating XML configuration files for the IP phones.
The first step requires configuring Asterisk to allow TCP in transport for the 8961 extension in the FreePBX GUI as well as the addition of a few parameters in two Asterisk configuration files:
[stewart@freepbx asterisk]$ ls -l sip_general_custom.conf sip_notify_custom.conf
-rw-rw-r-- 1 asterisk asterisk 34 Feb 17 16:11 sip_general_custom.conf
-rw-rw-r–. 1 asterisk asterisk 70 Feb 17 16:18 sip_notify_custom.conf
[stewart@freepbx asterisk]$ cat sip_general_custom.conf
tcpenable=yes
tcpbindaddr=0.0.0.0
[stewart@freepbx asterisk]$ cat sip_notify_custom.conf
udpbindaddr=0.0.0.0
tcpenable=yes
tcpbindaddr=0.0.0.0
callcounter=yes
[stewart@freepbx asterisk]$The last step requires modifying a configuration xml file SEP[MAC].cnf.xml (i.e., standard fare for Cisco phones), which I show below as follows (authPassword has been changed):
[stewart@freepbx tftpboot]$ egrep -e processNodeName -e featureLabel -e phoneLabel -e name -e contact -e displayName -e authName -e authPassword -e loadInformation SEPB07D47C124C6.cnf.xml
pool.ntp.org
172.16.0.175
Company
8961
8961
Stewart
8961
XXXXXXXXXXX
8961
sip8961.9-3-2-10
The 8961 refuses to register, with the following error in the Asterisk log file:
[2020-02-17 17:27:47] ERROR[5850] chan_sip.c: ‘TCP’ is not a valid transport for ‘8961’. we only use ‘UDP’! ending call.
[2020-02-17 17:27:47] NOTICE[5850] chan_sip.c: Registration from ‘sip:8961@172.16.0.175’ failed for ‘172.16.0.92:49537’ - Device not configured to use this transport type
[2020-02-17 17:30:23] ERROR[12663] chan_sip.c: ‘TCP’ is not a valid transport for ‘8961’. we only use ‘UDP’! ending call.
[2020-02-17 17:30:23] NOTICE[12663] chan_sip.c: Registration from ‘sip:8961@172.16.0.175’ failed for ‘172.16.0.92:49199’ - Device not configured to use this transport type
[2020-02-17 17:34:27] ERROR[23508] chan_sip.c: ‘TCP’ is not a valid transport for ‘8961’. we only use ‘UDP’! ending call.
[2020-02-17 17:34:27] NOTICE[23508] chan_sip.c: Registration from ‘sip:8961@172.16.0.175’ failed for ‘172.16.0.92:53205’ - Device not configured to use this transport type
[2020-02-17 17:34:29] ERROR[23560] chan_sip.c: ‘TCP’ is not a valid transport for ‘8961’. we only use ‘UDP’! ending call.If I read this correctly, it t appears using TCP as transport in FreePBX is not supported.
I’m stumped, and would appreciate anyone who can shed some light on this.
Posts: 5
Participants: 2