[djb_rh]

This seems like it must be the holy grail. I've got several 942's, 2002's, 2102's, and 3102's. I've managed to beat the snot out of the big sample 841 XML file that's floating around out there and use it as my starting point for configuring ALL of the above devices. I have a TFTP server setup and everything works great.

What would really be nice, though, is if I could get an actual COMPLETE XML file *out* of a device with ALL the configuration options it has and nothing more. I've been muddling by adding options by hand that the original file didn't have. Problem is I've now hit on a couple for the 3102 that I can't figure out. If I could query the device for all the XML tags it would expect, that would be wonderful. I expect if that was possible, though, someone would have posted how. But I can't find anything like that for the life of me.

The options in question are the eight different "Dial Plans" under the PSTN Line tab in the advanced configuration page. Those do not correspond to 'Dial_Plan_1_' and so on as that tag is already reserved for the "Dial Plan" option for Line 1, I believe. Obviously if anyone can tell me what XML tag I should use for those eight lines, I'd appreciate it, but I'd rather have a bigger picture way to extract all the XML tags for myself.


--Donnie

[djb_rh]

Alright, after a little futzing I figured out the answer to the riddle of the config option I couldn't figure out. The Dial Plans under "PSTN Line" are configured with XML tags starting at "Dial_Plan_1_2_" and moving to "Dial_Plan_8_2_" for the last of them.

I still want to know now to extract all the tags, dagnabbit.


--Donnie

[Yoshi325]

http://<phone -or- device ip address>/admin/spacfg.xml

That string should do it for some devices, with certain firmware. Unfortunately I cannot confirm that it works for a broad variety of devices, I just know that it works for 922/942/962 devices on firmware ver 4.1.18 or above.

[djb_rh]

Originally Posted by Yoshi325

http://<phone -or- device ip address>/admin/spacfg.xml

That string should do it for some devices, with certain firmware. Unfortunately I cannot confirm that it works for a broad variety of devices, I just know that it works for 922/942/962 devices on firmware ver 4.1.18 or above.

Worked great on my SPA942 with latest firmware, but doesn't work at all on a SPA3102 (latest) or a SPA2002 (latest). Dang. I had pretty good hope on that one. I tried a few other obvious variations on the URL but just got 404 on everything. It's nice at least getting it from the 942, though, so thanks for that one!

I updated the SPA941 - voip-info.org wiki with this info.

--Donnie

[eric]

Good tip, I've made it sticky.

[amitsalunkhe21]

hi
yoshi
i read your trick for xml file collect from spa but it is any help to extract xml file of PAP2 orPAP2T device if yes tell me i use same url that u gave in that message but it not work
plz giove me the solution
amit

[eric]

This trick only works with the SPA phones.

[amitsalunkhe21]

hi
but any way to work with linksys PAP2?
if yes tell me

amit

[albersag]

Originally Posted by eric

This trick only works with the SPA phones.

It also works on spa9000

[xixi168]

First I want to thank Donnie (djb_rh) for initiating this thread and posting some findings. I am new to this device and am struggling big time with the dial_plan_1/2... xml tag. What you said fixed that.

I do have one immediate followup question. I am trying to update a dial plan to (xx.<:@gw0> by using this <Dial_Plan_3_2_>(xx.<:@gw0></Dial_Plan_3_2_>, but the system log server always returns corrupt file error. After playing with different charater combinations, I think "<" and ">" are the guity parties. Every other characters, such as ":", "@" , work fine. My theory is that the "<>" inside of the dial plan is confused with the "<>" in the xml tag, but I am not sure how to work around this.

Any suggestions?