VXML gateway configuration clarification

[Ayodeji Okanlawon]

Gents I have seen a few configuration on vxml gateways that look like this..

My question is why do we need all the additional "paramspace" commands. I have deployed VXML configs in production and lab without any of the additional parameters. I have also checked the CVP IOS template and it doesnt have any of these parameters. 

application
  service new-call flash:bootstrap.vxml
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
  !
  service cvp-survivability flash:survivability.tcl
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
  !
  service ringtone flash:ringtone.tcl
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
  !
  service cvperror flash:cvperror.tcl
  paramspace english language en
  paramspace english index 0
  paramspace english location flash
  paramspace english prefix en
  !
  service load bootstrap
  !
  service handoff flash:handoff.tcl
  paramspace english index 0
  paramspace english language en
  paramspace english location flash
  paramspace english prefix enexit
  !
  service bootstrap flash:bootstrap.tcl
  paramspace english index 0
  paramspace english language en
  paramspace english location flash
  paramspace english prefix en

[Ayodeji Okanlawon]

Any thoughts on this gents?

[geoff]

Look up paramspace in the IOS commands and how it is used for TCL files. There must be a built-in application called "english" that is exporting those variables and the paramspace command is telling it to use those variables in the service. If you look inside some of CVP gateway TCL files you will find configuration suggested as above. It certainly was like that in the early version (I started with CVP 3.0).

My guess is they are not needed any longer.

Regards,
Geoff