« Back to TCL-API

Why is the disconnect cause always di_016 or di_017?

Combination View Flat View Tree View
Threads [ Previous | Next ]
Why is the disconnect cause always di_016 or di_017?
Answer
3/1/12 12:51 PM
The manual specifies tens of different disconnect causes, but I alwasy get either di_016 or di_017. Is this normal?
 
I would like to get a more detailed reason as to why an outbound call did not connect. For example, I would like to know that the call was rejected because the called party was busy or because nobody answered.
 
thanks!
Flag

RE: Why is the disconnect cause always di_016 or di_017?
Answer
2/29/12 7:25 AM as a reply to Adolfo Arizpe.
Hi Adolfo,

when called party was busy you will get di_017 and you will get di_019 when no answer.

016 Normal
017 Busy
018 No response from the user
019 No answer from the user

Thanks,
Raghavendra
Flag

RE: Why is the disconnect cause always di_016 or di_017?
Answer
2/29/12 5:02 PM as a reply to Raghavendra Gutty Veeranagappa.
Hi Raghavendra,

I have tried different combinations of busy, no answer and even using wrong numbers. I always get di_017.

Anywa, thanks for your help.
Flag