Topic: More auto provisioning questions

[gippsweb]

Got the aastra's sorted and provisioning brilliantly thx Jeff.

Have a couple of spa941's I thought I'd have a play with, seem to have it partly working apart from the config file being created in uppercase and the phone is looking for a file in lowercase?

I am using the default extension setup as follows;

Code: [Select]

["spa941.cfg"
<flat-profile>
<Profile_Rule> /spa$MA.cfg
</Profile_Rule>
<Resync_Periodic> 2
</Resync_Periodic>
</flat-profile>
]
["spa$MAC.cfg"
<flat-profile>
<Proxy_1_> gippsweb.com
</Proxy_1_>
<Outbound_Proxy_1_> gippsweb.com
</Outbound_Proxy_1_>
<User_ID_1_> 5001
</User_ID_1_>
<Password_1_> password
</Password_1_>
<Display_Name_1_> SPA941
</Display_Name_1_>
<Dial_Plan_1_> (*x.|*xx*x.|x.)
</Dial_Plan_1_>
<Time_Zone>
</Time_Zone>
<Resync_Periodic> 3600
</Resync_Periodic>
</flat-profile>
]

[SARK devs]

I'm assuming you are showing me the decriptor (spa941.cfg) and the phone config (spa{mac-address}.cfg).  If these two streams are in the same file then it is incorrect.... However....

The <Profile_Rule> in the spa941.cfg file dictates the case of the spa{mac-address}.cfg name.  (spa$MA or spa$MAC, if I remember correctly, but you should look it up in the sipura provisioning guide)
 
However, you can also change the name which SAIL generates...

If you code  ["spa$MAC.cfg"...   then SAIL will generate a lower case name;  however if you change it to ["spa$MAU.cfg" then SAIL will generate an uppercase name.

Playing around with these two settings should get you to where you want to be.

Best

S

[gippsweb]

Yes it's from the provisioning box from the extension..

I've tried changing the descriptor
["spa$MAC.cfg"
<flat-profile>

tried changing it from MAU to MAC in spa.cfg but it gets overwritten on a commit. (This appears to be the item I need to change).

Adding the descriptors to the aastra seemed to do the job, but the spa doesn't want to play for some damn reason. (the nut punching buttons on the keyboard probably, but don't tell anyone)

The SPA admin guide I've got here shows the config file with the mac address in lowercase.
I haven't been able to find my LVS provisioning guide, it probably has a bit more detail...

[SARK devs]

Yes it's from the provisioning box from the extension..

Hmmmm  - that looks pretty old.  We changed that a long time ago.

Go to devices...   You should have 2 files...  SPA-941 (which is the regular cfg file) and spa941.cfg (which is the decriptor for spa941.cfg).

They should look like this...

SPA-941 (provision window) should contain...

Code: [Select]

["spa$MAC.cfg"
<flat-profile>
<Proxy_1_> $localip
</Proxy_1_>
<Outbound_Proxy_1_> $localip
</Outbound_Proxy_1_>
<User_ID_1_> $ext
</User_ID_1_>
<Password_1_> $password
</Password_1_>
<Display_Name_1_> $desc
</Display_Name_1_>
<Dial_Plan_1_> (*x.|*xx*x.|x.)
</Dial_Plan_1_>
<Time_Zone> GMT
</Time_Zone>
<Resync_Periodic> 3600
</Resync_Periodic>
</flat-profile>
]
spa-941.cfg should contain...

Code: [Select]

<flat-profile>
<Resync_On_Reset> Yes
 </Resync_On_Reset>
<Resync_Periodic> 7200
 </Resync_Periodic>
<Profile_Rule> /spa$MAU.cfg
 </Profile_Rule>
</flat-profile>
Once you've set this up correctly, you'll need to delete and redefine your 942 extension in order to inherit the correct template.


Hope this helps

S

[gippsweb]

Just rebuilt the extension, only issue I've got is the MAU in the spa.cfg file, I tried to overwrite it but it changes back with a commit.

Yep, that SPA extension was originally created the week that the SPA 941's were listed as an IP device. So it probably hasn't changed since then.....

[SARK devs]

Not sure I understand...

You mean you can't update it in devices?

Best

S

[gippsweb]

I need a holiday.....
If I was to scroll far enough down the page I would have seen the .cfg files listed below the devices, wouldn't I 

How silly of me..(turns out the light and heads to the bedroom)...

[SARK devs]

sleep tight...  and don't let the bedbugs bite!

Best

S

[gippsweb]

OK, changed the spa941.cfg descriptor from MAU to MAC, this has changed the file the phone is looking for from

spa00aa00aa00aa.cfg

to

spa00:aa:00:aa:00:aa.cfg 

SAIL is creating the filename as follows spa00AA00AA00AA.cfg

After trying all ways of writing it I've just figured it out.

I have spa$MAU in the descriptor file, then in the extension changed spa$MAC to spa$mac
Now it finally creates the correct file for me......

[SARK devs]

Yes,

You really need to look in the sipura provisioning guide.  I'm pretty sure you can find it on-line these days.  There are quite a few different ways you can set up spa-941.cfg to direct the phone to look for different filename formats in the tftpserver ($MA, $MAC, $MAU plus some which generate serial numbers instead of mac addresses).

Anyhow, all's well that ends well.  Glad you got it to work OK.  The 941/2's are not bad phones, the only complaints we get are that they are a little on the quiet side and you can't turn off the missed calls indicater, which is a pain if the phone is in a ring group. 

Best

S 

[gippsweb]

Exact same problem I have with them.
And the fix ended up changing the file name in the provisioning tab on the phone.
Damn, so many things to fiddle with and stuff up, thank god for a master reset to take it all back to factory