Cisco 7970 Software Manual Intervention To

The SPA-3101 seems to have the right featureset, including internal dialplans to shift calls from the analog phones to Asterisk first, then the connected POTS line should the Asterisk server be unavailable.

To recap, the actual Asterisk server is a Trixbox 1.2.3 build running on a VMware virtual server, linking to a SIP trunk from BroadVoice.

Internal phones have now been expanded to include a few Cisco 7960 sets as well as the 7970.

Following my earlier posting about getting the 7970 to function with Ast.

Following my earlier posting about getting the 7970 to function with Asterisk, TrixBox founder Andrew Gillis sent me a note about the Endpoint Manager feature in TrixBox, which will create Cisco phone configuration files on the fly.

In TrixBox 1.2.3, theres support for the XML configuration file format that drives the 7970s SIP firmware, as well as older phones such as the 7940 and 7960.

Id seen this in my initial perusal of TrixBox, but didnt immediately see that the configuration files were available anywhere, so I built my own.

Well, if Id looked there to begin with, I wouldnt know half of what I now know about the configuration of these phones.

Cisco 7970 Software Manual Intervention To

The configuration files generated by TrixBox for the 7970 will work (and seem to have cleared up the continuous ring problem, though Im not sure exactly why yet), but still need manual intervention to configure some extended functions of the phone, such as multiple line and speed dial settings.

It appears that with the parameter set to 1, the phones internal Web server and client are disabled.

Setting this to 0 seems to have enabled both functions, and the phonebook and services menus are now populated on the phone.

In addition, theres a debug statement present in varwwwhtmlciscoservicesPhoneDirectory.php that will cause XML parsing errors.

Comment out the echo Query statement near the bottom of that script to fix that problem.

Specifically, it begins the firmware upgrade process, and looks for a file named Jar70sip.8-2-0-55.sbn, but that file doesnt exist in the firmware zip file.

Presumably, its looking for the file jar70sip.8-2-0-55.sbn, which is present.

I began to rename the file to permit the firmware upgrade to continue, but then thought better of it.

As far as the 7960s go, theyre a whole different beast than the 7970.

The configuration file syntax is arguably easier, and they dont have the 7970s habit of going into a reboot death spiral when there are XML parsing problems on the configuration file.

So at the moment I have five extensions on my Asterisk box with a single SIP gateway.

Im going to be dropping in a Linksys SPA-3102 to act as both an FXS and FXO analog adapter for a regular POTS line, and run through the dialplans on both that and the Asterisk box to bring at least one POTS line into the mix, along with an analog phone.

If that goes well, the other lines will get the same treatment.