CISCO 7920 works with Trixbox and SCCP, but only dials first digit
I finally got my CISCO 7920 working with Trixbox and SCCP. I can call into it just fine, however when I try to dial from it it only dials the first digit and then goes to a fast busy signal. Has anyone experienced this before? I am guessing that it is a phone configuration issue, as someone else stated that changing the firmware fixed this problem. However I tried 2 other firmwares with the same problem. I also looked into the dialplan.xml, but it is never loaded from the TFTP directory.
Paul
I'm experiencing the same problem with a Cisco 7910.
With chan_sccp I can dial the handset, it rings and I can pickup and talk. When I try to dial from the handset the first digit causes the handset busy tone.
The log shows "Taken Offhook with a call (9) in progress. Skip it!
This is with Asterisk 1.2.13 svn rev 47264
chan-sccp-20060408_1.2.8-1
The 7910 has
Application Load ID PO400403010400
Boot Load ID PC040300
Version 3.1(4.0)
With chan_skinny I can dial out from the handset but when you dial it's extension the handset doesn't ring.
I'm at a loss to resolve this myself, so any suggestions would be welcome.
I picked up bits from the SCCP-HOWTO2 on www.voip-info.org
http://www.voip-info.org/wiki/index.php?page=Asterisk+SCCP+channe...
The word document from here is very useful and I used his example config files
http://www.robbyyasko.net/trixbox/Files/tabid/161/Default.aspx
Starting here
http://www.voip-info.org/wiki/view/SCCP
1. Download the rpm
http://yum.trixbox.org/centos/4/RPMS/chan_sccp-20060408_1.2.8-1.i...
2. secure ftp copy the file onto your trixbox as root into /root
3. Secure shell onto the trixbox (you can use the web interface System SSH Terminal if you have it installed)
Install the file
rpm -i chan_sccp-20060408_1.2.8-1.i386.rpm
To see were the files are do
rpm -ql chan_sccp-20060408_1.2.8-1.i386
/etc/asterisk-1.2.8_samples/sccp.conf
/usr/lib/asterisk/modules/chan_sccp.so
/usr/share/doc/chan_sccp-20060408_1.2.8
/usr/share/doc/chan_sccp-20060408_1.2.8/7960-tones.xml
/usr/share/doc/chan_sccp-20060408_1.2.8/XMLDefault.cnf.xml
/usr/share/doc/chan_sccp-20060408_1.2.8/sccp.conf
/usr/share/doc/chan_sccp-20060408_1.2.8/set_sep_cnf
/usr/share/doc/chan_sccp-20060408_1.2.8/skinny-proxy-v1.2.pl
/usr/share/doc/chan_sccp-20060408_1.2.8/skinny-proxy-v1.4.pl
4.
copy the sccp.conf file to /etc/asterisk
cp -i /usr/share/doc/chan_sccp-20060408_1.2.8/sccp.conf /etc/asterisk/sccp.conf
Edit this fle and replace bindaddr = 0.0.0.0 with the ip address of your Trixbox
copy the XMLDefault.cnf.xml file to /tftboot
cp -i /usr/share/doc/chan_sccp-20060408_1.2.8/XMLDefault.cnf.xml /tftpboot
Edit this file and put the Trixbox ip address inside the ProcessNodeName brackets
5.
edit the Asterisk /etc/asterisk/modules.conf
disable the automatic loading of chan_skinny
If the module has autoload=yes you don't need to add an entry for chan_sccp otherwise add a load for it
autoload=yes
noload => chan_skinny.so
load => chan_sccp.so
6. Restart Asterisk
amportal restart
Additional setup
DHCP set the IP address of the Trixbox as the tftp boot server
Creat a SEPXXXXXXXXXXXX.cnf.xml in /tftpboot
the XXX part is the hexadecimal MAC address of the phone
Edit the sccp.conf file for your extensions and ids
I used the word document listed above to fill in the details from
http://www.robbyyasko.net/trixbox/
Hope that helps
I'm using my 7920 with trixbox 1.2.3. The one problem i've run into recently is that I can call the 7920 but the 7920 hangs up when I dial a sip extension. I can dial through my zap and vonage softphone trunks just fine. Also I have had a terrible time trying to get my 7920 to update to the latest firmware over tftp. If anyone has ideas....
Has anyone been able to figure out this problem yet? I still have not been able to get it to work. As far as configuring Trixbox with SCCP I basically followed the same guidelines as ddeasy, but I am not sure the exact steps that I took because most of it was trial and error. Mostly I just looked over the sample config files on the internet and tried different things and looked at the logs until it worked.
Paul
Haven't had a chance to try this yet, but I think that it may be the fix.
http://www.trixbox.org/forums/trixbox-forums/trixbox-endpoints/fi...
Paul


Member Since:
2007-02-21