Re: Can a Call Disconnection cause Q.850, can made a call not co
Typically calls are only billed if they go to a connect state. Any call that fails during ringdown (which is what I would expect here for this cause) should have the audio for the error cut through with a progress with a PI of 8 and never proceed to a connect state.
You should not be billed for this call, because this error signifies the call can't even get delivered to the remote party. From the q.850 spec:
cause indicates that the destination indicated by the user cannot be
reached because the interface to the destination is not functioning
correctly. The term "not functioning correctly" indicates that a
signalling message was unable to be delivered to the remote party; e.g. a
physical layer or data link layer failure at the remote party, or user
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...