SPA5XX with SIP: Creation of Phone Config Files (spa$PSN.cfg and spa$MA.xml)

[shaugupt]

Hi,

Can someone tell me the basic steps needed to get SPA5xx phones registered and working with CME as SIP.

From what I know, CME is capable of registering the SPA phones as SIP, but is incapable of creating "spa$PSN.cfg" and "spa$MA.xml" files needed by the phones.

I am looking for something similar to what happens for IP Phones, where CME generates the required "SEP<mac>.cnf.xml".

Presently, I used to generate the "spa$MA.xml" template from the SPC Compiler and manually edit the xml tags according to requirements for each particular phone.

Is there an "industry standard way" or "New CME Feature" or some other "Script/Program" to get this done for multiple SPA Phones.

Thanks,

Shaurya

[Patrick Born]

Hi Shaurya,

I suggest you post your question on a CME forum and ask for help adding a 3rd-party SIP device.

Do not provide the SPA phones with any SEP* files. These files cause the phone to switch to SPCP-mode and will not operate in SIP-mode again until you factory reset them.

Take a look at this document for an example of how to build configuration files for a SPA phone. This document is written for Asterisk, but is still applicable. https://supportforums.cisco.com/docs/DOC-9954

This You Tube tutorial describes the phone's boot process: http://www.youtube.com/watch?v=76IMzvfpsx8 Note at the 3 minute 13 second mark at step 5 that the phone will switch out of SIP mode if it receives any SEP* files.

Regards,

Patrick

----------

Use this reference document to locate SPA phone resources

[shaugupt]

Hi Patrick,

Thanks for the reply. A lot of good information there.

Actually, I have been following the same steps, and have got successful provisioning for SPA phones as SIP on CME.

In the document https://supportforums.cisco.com/docs/DOC-9954 "Section - 3- Building the spa$MAC.xml Files" where the admin has to manually modify the file for each phone.

I was looking for some tool/script/etc which would help in bulk-modification of spa$MAC.xml for many phones.

You can think of it as a "Bulk ZTD of SPA(as SIP) with CME" usecase.

Regards,

Shaurya

[shaugupt]

Hi Patrick,

In one of your documents regarding the spa$MAC.xml, you mentioned that "less is more",

i.e., we need to supply only those fields from the compiler generated file, that we actually require to change on the phone.

Thus there is no need to send the whole file, but just the required xml fields.

Please correct me if I am wrong here.

Regards,

Shaurya