Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Can a Call Disconnection cause Q.850, can made a call not considered to be billed?

There are some valid/good (answered) calls (Connect and realese signals sent/received), with duration, that have disconnect cause 27  (destination out of order) (H323 Protocol)…

·         How can that be explained?

·         What is the real purpose and significance of cause 27  (destination out of order)?

·         Why do real-good answered calls end with disconnection cause 27

·         Why should calls with disconnection cause 27 be accepted, and billed?

·         Is there regulation that may consider that disconnection causes are used to determine if a call is billable?

·         Do you know any kind of document – white paper - call flow that may explain clearly this situation (like ITU regulation - standard or from a different organization)

·         Is it correct to conclude that calls with duration which cleared with disconnection cause 27 are non billable?

Thank you very much for your cooperation on this matter.

Cisco Employee

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:

This 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 equipment offline