HowTo troubleshoot a vxml

From SIPfoundry sipXecs IP PBX, The Open Source SIP PBX for Linux - Calivia

• 20080806: Created this page, will add more later this week

• Disclaimer: The views and opinions of the author expressed herein do not necessarily state or reflect those of the SipFoundry or any associated company

Contents 1 Prerequisites 2 Useful commands 3 Useful references 4 Step-by-step 5 Errors (attempted at) explained

Prerequisites

My configuration, while probably not ideal, is all I have available. 1 laptop running XP using VS2005 and X-Lite. Then 1 testbed desktop running the sipfoundry-3.10.2-centos5-i386.iso server as well as smb for ease of access to the vxml files. For my example on troubleshooting, you will need [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY.

Useful commands

tail -F /var/log/sipxpbx/vxmlengine.log

tail -F /var/log/sipxpbx/mediaserver.log

nano /etc/sipxpbx/mappingrules.xml.in

   <userMatch>
     <description>Test_IVR</description>
     <userPattern>900</userPattern>
     <permissionMatch>
       <transform>
         <url><sip:{digits}@{mediaserver};voicexml={voicemail}%2Fcgi-bin%2Fvoicemail%2Fmediaserver.cgi%3Faction%3Dautoattendant%26name%3DTest></url>
       </transform>
     </permissionMatch>
   </userMatch>

• Replace "Test" in the url with the corresponding portion of your vxml filename

nano /usr/share/www/doc/aa_vxml/Test-schedule.xml

nano /etc/sipxpbx/mediaserver-config.in

Useful references

HTTP Status codes explained Alot of the vxmlengine.log entries reference an http status code.

sipX source code tree

Step-by-step

• mediaserver.log.level VXIString DEBUG

create \\10.10.10.69\share\usr\share\www\doc\aa_vxml\autoattendant-Test_IVR.vxml

add wavs to \\10.10.10.69\share\var\sipxdata\mediaserver\data\prompts\Test_IVR

Errors (attempted at) explained

These are simply errors that I've run across

No feedback errors in vxmlengine.log but call hangs up

I had a "." in a block name <block name="FR023.1">

Bad nesting or nesting is out of spec from expected DOM.

In this case, it was a <script> tag nested within a <block> tag.

Wed, Aug 6 2008 20:00:39.94 GMT|TUCPU=0|TKCPU=0|2|pingtel.com.OSBjsi|502|e=t|l=6|l= |t=)

Wed, Aug 6 2008 20:00:39.94 GMT|TUCPU=0|TKCPU=0|2|pingtel.com.OSBjsi|502|e=u|l=6|l=|t=

Returned content from a <submit> tag was not understand and subsequently triggered a "reset content" status code

Wed, Aug 6 2008 20:48:02.85 GMT|TUCPU=2|TKCPU=0|13|pingtel.com.OSBinet|302|U=h

Wed, Aug 6 2008 20:48:02.85 GMT|TUCPU=2|TKCPU=0|13|pingtel.com.vxi|205|uri=https://10.10.10.68:444/bene/InterfaceClientIVRs.aspx

Returned from <transfer name="varTransfer" bridge="true" dest="tel:+18004777822" />

Thu, Aug 7 2008 01:01:58.03 GMT|TUCPU=0|TKCPU=0|7|pingtel.com.vxi|999|message=unexpected executable element

Returned from a <submit> to a page that doesn't exist. Hence the 404 entry.

Thu, Aug 7 2008 02:06:19.22 GMT|TUCPU=2|TKCPU=0|26|pingtel.com.OSBinet|219|U=h|M=P|E=-404

Thu, Aug 7 2008 02:06:19.22 GMT|TUCPU=2|TKCPU=0|26|pingtel.com.OSBinet|204|r=50

Thu, Aug 7 2008 02:06:19.22 GMT|TUCPU=2|TKCPU=0|26|pingtel.com.vxi|203|uri=https://localhost:8091/bene/InterfaceClientIVRs.aspx