Profile Rule - Problems

Unanswered Question
Oct 26th, 2009
User Badges:


I am having big problem due to the following two Bugs in Profile Rule evaluation in Sipura, LinkSys and Cisco IP Phone Devices.

1) If I give the URL of a web server like on a Windows IIS Server. It usually redirect to a default document by sending a redirection 301/XXX message to user agent. All SIP Devices are not supporting redirection message from web server at all. They are not able to pull configuration file.

2) General Purpose Variables: When used in Profile Rule like$C and if the GPP_C has the value "THIS IS TEST" than device firmware is not able to hit profile server may be because it is not encoding it when doing macro expansion and this is causing some error when sending GET request to server.

My Profile Rule was using GPP_C variable and when I saved the Date Time in it. All of our devices stop hitting our profile web server. If someone can suggest the solution to acces these devices without going on each device again that would be highly appreciated.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Patrick Born Thu, 10/29/2009 - 06:11
User Badges:
  • Cisco Employee,

Hi Tahir,

The SPA devices do not support redirection.

The SPA devices look to a provisioning server pointed to by option 66 in the DHCP OFFER.

Consider updating the DHCP server so that option 66 points the SPA devices to the appropriate provisioning server.

I escalated the second part of your question to Development Engineering, here's the response:

"The GPP variable will get expanded as is.

For example if your profile rule is$C

and your GPP_C is This is a test

then that profile rule will get expanded to a test

perhaps your "C" can't handle spaces as an argument.

It's best if you don't use spaces then, where you can try "this-is-a-test". or better - follow my example on 3) below

3) Typically, provisioning is used so that you don't need to configure every devices that you have one by one.

It's probably best if you use our .xml or .cfg profile (spc tool can generate example for this) and have

the unit resync to its profile using the default built in macro.

for example, your profile rule can be pointing to your webserver :$MA.cfg

All units if configured like the above, will try to fetch its profile named to be "mac_address".cfg.

That way it is cleaner on which unit have which exact configuration."





This Discussion

Related Content