Cisco 7960

jamrod

New Member
Joined
May 4, 2008
Messages
12
Reaction score
0
I was really hoping to ditch trixbox and move to PIAF as I really do long for the A@H days again. I have gathered that there seems to be a bit of negativity to everything Cisco projected here. I can see the reasons why not to promote them but I have an estate of Cisco 7960 IP phones and whether I like them or not need to make them work with PIAF if I want to change and move my clients to this new exciting project. Is there an easy way to make them work with PIAF as they work perfectly well with SIP firmware and trixbox? Any help would be appreciated.
 

TheShniz

Guru
Joined
Nov 15, 2007
Messages
560
Reaction score
2
I have to disagree, there's *much* love for Cisco phones here on these forums... don't let it get you down that everyone doesn't deem them as 'the best phone ever' (I don't btw, I feel you have different phones for different applications, I have no single favorite)

Anywho...

No reconfiguration required... simply move the PiaF's IP Address to what your TB's was.

If you're using SCCP aka Skinny, then check out the Treasure Cove (or whatever) thread... everything you need to know for installing SCCP-b is there.

P.S.
It would be good measure for you to copy over the /tftpboot/ onto the PiaF.

P.P.S.
I've had good results w/ their latest P0S3-08-9-00 firmware on 7940/60.
 

jamrod

New Member
Joined
May 4, 2008
Messages
12
Reaction score
0
Thanks for the quick reply. DO you have any advice on whether I should use SCCP or just keep the phones on SIP?
 

TheShniz

Guru
Joined
Nov 15, 2007
Messages
560
Reaction score
2
Well... It can be argued either way I suppose. There are some key differences between SIP & SCCP w/ Cisco phones, and you should check out the Treasure Cove for that listing (for fear I forget something).

My *preference* is to always use Cisco phones w/ SIP firmware whenever possible... reason being, administration of said extensions is VERY easy in FreePBX. Granted adding 'Custom Extensions' isn't all that difficult either, but I'd just assume keep everything the same and avoid any confusion w/ the users.
 

The Deacon

Guru
Joined
Jan 29, 2008
Messages
296
Reaction score
14
I have to agree. I have a plethora of Cisco 7940 * 7960 phones and they work GREAT with PiaF.

I'm a big fan of SIP on the phones as well...

FWIT.

-Rick
 
Joined
May 16, 2008
Messages
87
Reaction score
0
I am a Cisco voice guy and also a newbie with piaf and found the Cisco easy enough to configure and get working with SIP. Logs of info around for figuring it out.

For me, I learned.

Enable additional logging in /etc/xinetd.d/t*f*t*p by adding -vv at the option line and look in the /var/log/message file when the phone is booting. It will tell you everything the Cisco phone is looking for. Configure those files and your set.
 

TheShniz

Guru
Joined
Nov 15, 2007
Messages
560
Reaction score
2
I wish I knew more about how to integrate with the Call Manager... not because I want to necessarily work with them, but rather help migrate someone off them. As it is right now, I just up & rip the whole CM out & plunk down a new system w/ the same phones... would definately make life easier w/ larger sites.

Any advice on learning to integrate w/ the Call Manager? (as in CM-side)
 
Joined
May 16, 2008
Messages
87
Reaction score
0
The Cisco voip wiki on this is pretty good. I use CM4.1 so it is sip aware.

http://www.voip-info.org/wiki-Asterisk+Cisco+CallManager+Integration

A few things I needed to figure out.

1. Be sure the MTP on CM4 is running and enabled. Also be sure the default media group has the MTP in it.

2. When you create the trunk in CM, be sure the incoming CSS and/or partition is reachable by the phones. There is a setting on the trunk for incoming calls on this.

3. When creating the trunk in PIAF, be sure the context is a trunk. You need to include the statement. Its not shown on the wiki.

4. In CM, turn on SIP traces and look at the CM logs if you need to troubleshoot it.

5. In PIAF look at the Asterisk logs to troubleshoot it.

6. On PIAF you need an outbound route to point to CM. Hopefully you can do a block of numbers.

7. On CM you need a route pattern to point to the PIAF.

Took me around 30-40 minutes to figure it out. But I know CM fairly well and was using a development box we have and could do anything with it. Your mileage may vary.

The Cisco press call manager book is pretty good. It explains partitions, CSS, route patterns and the basics which you would need to move around CM.

Hope this helps. T.
 

ksDevGuy

Guru
Joined
Oct 18, 2007
Messages
102
Reaction score
11
Ditto. Run Cisco 7960's & 7971's everywhere primarily -- under PBIAF & some leftover TB installs. Once you've dialed in the config initially, from there out on any distro really it's a matter of simply moving your tftpboot folder & doing a current version FreePBX backup/restore ... that's it!

Looking to tinker with the color 7965/75's soon (if I can get BLF support working under SIP someday, or SCCP I've been testing not to crash under Asterisk v1.4 via Group Call Pickup when hints are present! Ugh).

ksDevGuy
 

TomS

Guru
Joined
Oct 18, 2007
Messages
240
Reaction score
6
Still cannot get 7940G's to work

:banghead:
I have a few Cisco 7940G phones.
I have installed SIP 8.9 from Cisco but cannot get the phones to complete the load.
Does anyone have an A-Z install for these phones if they are so easy.
I do not have a TB tftpboot area to retieve and move to PiaF.
I cannot find the .xml example files to make the phones work.
It says that OS79XX.TXT is not used after SIP release 5 but I configured it anyway with: POS3-08-9-00
All permissions are currently 777 in /tftpboot directory.
In /tftpboot directory I have:
POS3-08-9-00.loads
POS3-08-9-00.sb2
SIP<MAC>.cnf (Not an .xml file)
SIPDefault.cnf (Not an .xml file)
from another document I created: XMLDefault.cnf.xml
------ SORRY INDENTS ARE LOST UPON SAVING THE ENTRY!
<Default>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<ports>
<ethernetPhonePort>2000</ethernetPhonePort>
</ports>
<processNodeName></processNodeName>
</callManager>
</member>
</members>
</callManagerGroup>
<loadInformation8 model="IP Phone 7940">P0S3-08-9-00
</loadInformation8>
</Default>
---
What is Ether Phone Port 2000? should this be 5060 for SIP?
While displaying that it is configing IP, it comes out with
a looking for file: SEP<MAC>.cnf.xml
I cannot find an example of this file anywhere.
In the logging of the tftpd in messages (see above and thanks):
Looks for filename CTLSEP<MAC>.tlv not found
Looks for filename SEP<MAC>.cnf.xml not found
Looks for filename SIP<MAC>.cnf and loads it
Looks for filename POS3-08-9-00.loads and loads it
Looks for filename P003-08-9-00.sbn and fails
Looks for filename CTLSEP again and fails
Looks for ilename SEP...cnf.xml and fails again
Looks for XMLDefault.cnf.xml and loads it
Then it goes back to CTLSEP and fails
Then SEP...cnf.xml and fail
Then SIP...cnf again and loads it
Then POS3 again and loads it
Then POO3 again and fails
.... Over and over again
I have access to cisco.com so if someone can tell me the
files needed in /tftpboot, permissions required, and configuration of the .xml files to get these phones to run, it would be greatly appreciated.
Thanks TomS
 

TheShniz

Guru
Joined
Nov 15, 2007
Messages
560
Reaction score
2
The 7940/60 with SIP firmware does NOT use the .xml files, but rather older .cnf files...

Here's an example of a SIP<MAC>.cnf:

Code:
# Cisco SIP Configuration
phone_label: "Name"
line1_name: "123"
line1_shortname: "123"
line1_displayname: "123"
line1_password: "XXXX"
line2_name: "UNPROVISIONED"
line2_shortname: "UNPROVISIONED"
line2_displayname: "UNPROVISIONED"
line2_password: "UNPROVISIONED"
line3_name: "UNPROVISIONED"
line3_shortname: "UNPROVISIONED"
line3_displayname: "UNPROVISIONED"
line3_password: "UNPROVISIONED"
line4_name: "UNPROVISIONED"
line4_shortname: "UNPROVISIONED"
line4_displayname: "UNPROVISIONED"
line4_password: "UNPROVISIONED"
line5_name: "UNPROVISIONED"
line5_shortname: "UNPROVISIONED"
line5_displayname: "UNPROVISIONED"
line5_password: "UNPROVISIONED"
line6_name: "UNPROVISIONED"
line6_shortname: "UNPROVISIONED"
line6_displayname: "UNPROVISIONED"
line6_password: "UNPROVISIONED"
line1_authname: "123"
line2_authname: "UNPROVISIONED"
line3_authname: "UNPROVISIONED"
line4_authname: "UNPROVISIONED"
line5_authname: "UNPROVISIONED"
line6_authname: "UNPROVISIONED"

Don't forget, you'll still need SIPDefault.cnf... of which there are plenty of examples. I'll say that 50% of the problems I have with Cisco phones are due to typing errors (the other 50% is due to them being a royal PIA).
 

TomS

Guru
Joined
Oct 18, 2007
Messages
240
Reaction score
6
Why does it still request .xml

Why does it still requrest the .xml files in the /tftpboot directory?
I started with the .cnf only files but no luck.
I will try it again with your input.

This is the current SIP<MAC>.cnf file:
# SIP Configuration File
# 7940 w/2 lines From: ADI's World 'Using Cisco IP Phones with Asterisk'
# Line 1 Parameters
line1_name: 540
line1_authname: "540"
line1_displayname: "540"
line1_password: "1234"

# Line 2 Parameters
line2_name: 541
line2_authname: "541"
line2_displayname: "541"
line2_password: "1234"

# Phone Label (Text desired to be displayed in upper right corner)
# Has no effect on SIP messaging
phone_label: ""

# Remote Access Parameters for console or telnet login
phone_prompt: "SIP Phone"
phone_password: "secretpassword"
user_info: none

The OS79XX.TXT file is:
POS3-08-9-00

Files in the /tftpboot directory are:
POS3-08-9-00.loads
POS3-08-9-00.sb2
SIPDefault.cnf

Are other files required here?
Here is the SIPDefault.cnf file:
# Image Version
image_version: "P0S3-08-9-00"
# Proxy Server
proxy1_address: "IP"

# Proxy Server Port (default - 5060)
proxy1_port:"5060"
# Emergency Proxy info
proxy_emergency: "IP"
proxy_emergency_port: "5060"
# Backup Proxy info
proxy_backup: "IP"
proxy_backup_port: "5060"

# Outbound Proxy info
outbound_proxy: ""
outbound_proxy_port: "5060"

# NAT/Firewall Traversal
nat_enable: "0"
nat_address: ""
voip_control_port: "5061"
start_media_port: "16384"
end_media_port: "32766"
nat_received_processing: "0"
# Proxy Registration (0-disable (default), 1-enable)
proxy_register: "1"

# Phone Registration Expiration [1-3932100 sec] (Default - 3600)
timer_register_expires: "3600"

# Codec for media stream (g711ulaw (default), g711alaw, g729)
preferred_codec: "none"

# TOS bits in media stream [0-5] (Default - 5)
tos_media: "5"
# Enable VAD (0-disable (default), 1-enable)
enable_vad: "0"

# Allow for the bridge on a 3way call to join remaining parties upon hangup
cnf_join_enable: "1" ; 0-Disabled, 1-Enabled (default)

# Allow Transfer to be completed while target phone is still ringing
semi_attended_transfer: "0" ; 0-Disabled, 1-Enabled (default)

# Telnet Level (enable or disable the ability to telnet into this phone
telnet_level: "2" ; 0-Disabled (default), 1-Enabled, 2-Privileged
# Inband DTMF Settings (0-disable, 1-enable (default))
dtmf_inband: "1"

# Out of band DTMF Settings (none-disable, avt-avt enable (default), avt_always - always avt )
dtmf_outofband: "avt"

# DTMF dB Level Settings (1-6dB down, 2-3db down, 3-nominal (default), 4-3db up, 5-6dB up)
dtmf_db_level: "3"

# SIP Timers
timer_t1: "500" ; Default 500 msec
timer_t2: "4000" ; Default 4 sec
sip_retx: "10" ; Default 11
sip_invite_retx: "6" ; Default 7
timer_invite_expires: "180" ; Default 180 sec

# Setting for Message speeddial to UOne box
messages_uri: "*97"
# t*f*t*p Phone Specific Configuration File Directory
tftp_cfg_dir: "./"

# Time Server
sntp_mode: "unicast"
sntp_server: "NTP-IP"
time_zone: "MST"
dst_offset: "1"
dst_start_month: "Mar"
dst_start_day: ""
dst_start_day_of_week: "Sun"
dst_start_week_of_month: "2"
dst_start_time: "02"
dst_stop_month: "Nov"
dst_stop_day: ""
dst_stop_day_of_week: "Sunday"
dst_stop_week_of_month: "1"
dst_stop_time: "2"
dst_auto_adjust: "1"

# Do Not Disturb Control (0-off, 1-on, 2-off with no user control, 3-on with no user control)
dnd_control: "0" ; Default 0 (Do Not Disturb feature is off)

# Caller ID Blocking (0-disabled, 1-enabled, 2-disabled no user control, 3-enabled no user control)
callerid_blocking: "0" ; Default 0 (Disable sending all calls as anonymous)

# Anonymous Call Blocking (0-disbaled, 1-enabled, 2-disabled no user control, 3-enabled no user control)
anonymous_call_block: "0" ; Default 0 (Disable blocking of anonymous calls)

# Call Waiting (0-disabled, 1-enabled, 2-disabled with no user control, 3-enabled with no user control)
call_waiting: "1" ; Default 1 (Call Waiting enabled)
# DTMF AVT Payload (Dynamic payload range for AVT tones - 96-127)
dtmf_avt_payload: "101" ; Default 100

# XML file that specifies the dialplan desired
dial_template: "dialplan"
# Network Media Type (auto, full100, full10, half100, half10)
network_media_type: "auto"
#Autocompletion During Dial (0-off, 1-on [default])
autocomplete: "1"
#Time Format (0-12hr, 1-24hr [default])
time_format_24hr: "0"
# URL for external Phone Services
services_url: "http://IP/xmlservices/index.php"
# URL for external Directory location
directory_url: "http://IP/xmlservices/PhoneDirectory.php"
# URL for branding logo
logo_url: "http://IP/cisco/bmp/trixbox.bmp"
# Remote Party ID
remote_party_id: 1 ; 0-Disabled (default), 1-Enabled

IP means actual IP address goes there.
Thanks
TomS
 

TomS

Guru
Joined
Oct 18, 2007
Messages
240
Reaction score
6
Reboot phone

After reboot of phone, it still is looking for SEP<MAC>... file.
It continues to loop through and never continues.
Thanks
TomS
 

TheShniz

Guru
Joined
Nov 15, 2007
Messages
560
Reaction score
2
Well, I'm going to assume that you have the SIP firmware loaded already, so all you should need is...

OS79XX.TXT
P0S3-08-9-00.loads
P0S3-08-9-00.sb2
P003-08-9-00.bin
P003-08-9-00.sbn
SIP<MAC>.cnf
SIPDefault.cnf

...I still must remind that most problems are typographical either with filenames, mac addy's, or the configuration files themselves (syntax, etc). Cisco phones are not forgiving when it comes to programming.

Is this a problem with a particular Cisco phone, or multiple phones?
 

slickrock22

Member
Joined
May 15, 2008
Messages
46
Reaction score
0
I know someone just posted a new thread on config for TB 1.2.3 tool to use the gui to config cisco phones, but does PBIAF have the tool that was in TB 1.2.3? If not is there a way to add it back in? It makes cisco admin a snap!
 

merlyn

New Member
Joined
Nov 10, 2007
Messages
127
Reaction score
0
:banghead:
I have a few Cisco 7940G phones.
I have installed SIP 8.9 from Cisco but cannot get the phones to complete the load.
Thanks TomS

Ok Tom I am a little confused. You said you loaded SIP 8.9 on the phone but it doesnt fully load so is it actually using 8.9 currently or is it defaulting back to the old firmware and then rebooting.
You cannot "jump" from too old a version to a new version
Goto settings --> status ----> firmware version to see what it has loaded currently. You should be able to check this on the phone if you keep hitting the settings button at some point during the loading process (probably). Or do you know what firmware version it last worked on was?

merlyn
 

merlyn

New Member
Joined
Nov 10, 2007
Messages
127
Reaction score
0
Nevermind TomS
I noticed your OS79XX.TXT is wrong that would do it. It should read.
P003-08-9-00. I am not using 8.9 so I am not positive that cisco did not change there format yet again but this is the correct format for 8.6 and 8.8 (I am currently running 8.8). If in doubt use the OS79XX.TXT file that came in the zip file from cisco.
And yes it should read P0S3-08-9-00 in the SIPDefault.cnf which you have correct. Don't ask me why cisco does this but that is the way they want it with the S changed to a 0 (zero) in the OS79XX.TXT file only.

as for the SIP<MAC>.cnf file mine is currently blank and i can register fine. My SIPDefault.cnf is default that was created when i set it up except for changing my server ip # and firmware version #. I will be adding in info as i continue to setup my system though of course but in the mean time it is working fine.
I would go completly default for now then add the extra info in later after you get them registered and on the correct firmware.

That should get you working.

Merlyn
 

TheShniz

Guru
Joined
Nov 15, 2007
Messages
560
Reaction score
2
That's correct... and it should be noted that Cisco themselves has been known to publish firmware updates w/ typos that make them unusable unless corrected. I seem to remember programming some 7971's and having to rename the .jar file cuz Cisco released it incorrectly.
 

baldbrad

New Member
Joined
Jun 1, 2008
Messages
12
Reaction score
0
I have one, and have no problems with it under PIAF. Just make sure the t*f*t*p server is installed and enabled in PIAF, copy the configuration files from your trixbox server to the PIAF server, and change the addresses in the phone to match the new server (if you're changing IP's). Should work just fine.
 

Members online

No members online now.

Forum statistics

Threads
25,779
Messages
167,505
Members
19,199
Latest member
leocipriano
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Top