A VXML error message is generated when the application tries to read a value that is associated with a new header that has been added to the SIP header tag configuration file,
Below is an example of the error message in the VRBE log file when an attempt in read the value associated with my-new-sip-header-string is made:
2021-03-24 10:15:28.363 call 3:10.142.209.52 PID[0:6] (VXI00000) FAILURE: 760775408340697091-0:VarScope::eval:The undefined value has no properties.:error executing:getInboundHeader('my-new-sip-header-string').value
This file is only read when the BVR trunks are started. Therefore any changes to the file whilst BVR is running will not be effective and will not be recognised by BVR until a restart is performed.
There are three available options to force BVR to read the updated file:
Stop and restart BVR completely by either following the documented steps in the BVR product manuals or your own defined shutdown and restart process.
Disable and re-enable all BVR trunks using
This does not require BVR to be restarted and has less downtime.
- Login as the dtuser id and get to the command line prompt
- To disable all trunks, run this command:
wvrtrunk -d -t all
- To enable all trunks, run this command:
wvrtrunk -e -t all
Disable and re-enable all BVR trunks using the BVR GUI.