ā02-07-2017 07:32 AM - edited ā03-14-2019 05:00 PM
Good evenning.
WeĀ“re facing the error "abnormally disconnected with code 38." on VXML server daily. We have 10 VXML's servers on version Version 15.5(3)M1 and 18 CVP callservers running on version 9.0. What logs we should collect and analyze.
Tks for helping.
ā02-07-2017 02:06 PM
Hello,
Usually If a call error is detected on the CVP VRU leg, the incoming call is disconnected with a cause code 38. Its based on the TCL files used
Have a look at the below document which explains the CVP TCL files
But still you need find out the cause for the problem. You might want to get the below logs and analyze
You can check the Tracing levels of CVP and Gateway here. But be cautious when you enabled on the Gateway as the logs will be more.
Regards,
Senthil Kumar
ā02-08-2017 08:27 AM
Here's the complete message:
18049132: Feb 8 10:51:49.932: %IVR-3-APP_ERR:
**** CVP HANDOFF.TCL: 682A8EDE.ED2311E6.AA4DDFCB.B180692A abnormally disconnected with code 38. ****
Which debug Should I enable on VXML?
ā02-08-2017 04:22 PM
So basically the VXML Gateway uses sip/http protocols to communicate to the CVP Call Server.
So the below mentioned debugs should help you to find whats going on
debug ccsip mess
debug voip ccapi inout
debug http client all
debug voip application vxml all
debug voip application all
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: