Cisco SPA112 fiasco continued...
As if it isn't bad enough releasing buggy devices, I can't believe that Cisco have changed the way provisioning works.
My customers are struggling to find PAP2T devices and I'm under pressure to allow the use of the new SPA112 and SPA122 devices with our service.
I can't get hold of the new provisioning guide - assuming one even exists so I'm up the creek without a paddle.
Can anyone provide me with any information whatsoever on the new Cisco provisioning model?
Are you doing anything special with the PAP2/PAP2T provisioning ?
I am using http to provision my SPA/PAP2 devices and for me everything is working with the new ATAs.
If you want me to try something on my ATA I can do it.
Providers: voip.ms, freephoneline, smartcall.ro through asterisk. Hardware: Vonage VDV21, Moto VT2x42, Linksys SPA series, Grandstream HT series, Panasonic KX-TGP5x0
No - nothing too special. I have written my own HTTP provisioning server that creates a temporary xml profile and instructs the ATA to get the profile.
A minimum number of settings are downloaded at stage 1, including $SA and the location of an encypted profile in Profile_Rule.
All Linksys devices provision perfectly, however, my SPA112 fails at the first stage. Using Wireshark I see the SPA requesting the temporary profile, but none of the settings are download.
I'm at the stage where I am using the /admin/resync? command with the SPA112 to test what it can and cannot download. I have found that both of the following work, so it seems to support both forms of syntax:
My old profiles simply use but maybe I need the schema info as follows:
It's good to hear that you have been able to provision the Cisco devices using your Linksys profiles, so I will do a few more tests and update this thread.