Hi,

Currently experimenting with the use of SMT i series handsets running SCM firmware to connect to alternative VOIP systems (asterisk, etc)

We have a bunch of SMT handsets left over from an outgoing OfficeServ setup that will continue to be used, if possible.

I'm trying to "roll my own" PnP/DHCP/TFTP solution to get these handsets auto-configuring and registering to a new PBX, or whichever VOIP system I configure, so phone-by-phone manual setup can be avoided if possible. The ability to set station keys and AoM buttons would be a bonus.

The SCM firmware handsets run through a bootup sequence that requests a number of XML files over TFTP/HTTP from the SCM system.

Having an example of the files would be super helpful. Does anyone have an SCM system in a lab enviro where they'd be happy to send me a copy of these XML files?

The phones request the following files:

via TFTP:

sec_boot.xml

and via HTTP:

/sec_mac/sec_{mac}.xml
/scm_profile/sec_phone.xml
/scm_profile/sec_user_{id}.xml
/scm_profile/sec_line_{group_line}.xml
/scm_profile/sec_service_{group}.xml

/scm_profile/sec_key_xxxxxxxx.xml

Your help would be very much appreciated. Of course, happy to post results of experimentation back here for everyone to enjoy.

Thanks.

First thing is you'll need to flash the scm firmware to the handsets. This is done automatically when the handsets first connect to a scm system, but can be done manually.

Yep. Have the SCM firmware. Happy to do this manually, but also keen to investigate how to ape the SCM auto-update procedure as well.

What I don't have is an SCM - just a retiring OfficeServ.

An update:

I acquired a copy of SCM firmware for an IPX300B unit. I unpacked it and had a dig around. Found a script in there called: samsung_config_generator.sh which takes a CSV file and puts out the sec_{mac}.xml files I asked about in my original post.

Funnily enough, the file is written by someone at Grandstream Networks, and the file it produces is the same format (matching P values and all) as the XML provisioning done by Grandstream SIP devices.

I've done some XML provisioning of Grandstream devices before, so I'll have a go at sending a file to one of my SMT-i3105 handsets via its PnP process and see what happens.

Will report back with results.

Red Herring, I think.

Interesting that the file is there, but my phone seemed to ignore its contents so I am assuming for now it's not related.

I'll keep looking.

sec_<phonemac>.xml file:



The phone then immediately requests /scm_profile/sec_user_2953.xml from the HTTP server. Filename is of course determined by the login_info text node in the previous file.

Reverse engineering the format of the sec_user_<userid>.xml file is proving difficult.

saved as /scm_profile/sec_user_EXT#.xml gets me as far as "Connecting Server..." on the handset.

If someone could provide an example (sanitised for your security of course) of a sec_user file from an SCM or iBG system we might be able to push this further along an hopefully document the SMT-i series autoprovisioning process.

Without knowing more about the expected internals of this XML file, I will probably leave it there.

Have you tried installing the SCME software on an old PC? Its an ISO you can burn it to a DVD and install the system. Its linux based and might provide what you need?

No, I haven't. The SCM software I managed to get hold of is I think a package for SCMC - yes it's linux, but it's compiled for an ARM processor and won't go on a PC.

Certainly the executable I decompiled to get as far as I have was compiled for ARM anyway, and as far as I can tell it's the only executable or script I found in the system that writes to those files. All others are concerned with reading them, or scripts to delete them.

I'll scrounge around and see if I can obtain an SCME image somewhere.

Thanks for the info.