This document was generated from CDN thread
Created by: Frode M on 02-09-2009 12:55:37 PM
Hi, I'm wondering what is the recommended method for observing call statuses. Currently I've registered a listener with
But when placing a call to an invalid number, such as with
but then no call status events are produced. "xStat call" shows 0 active calls.
By using "xFeedback register *", there seems to be a few events to choose from, to detect such a failed dial command:
and
I can't recall having seen the "*h" response types before. What are these (compared to "*e" events and "*s" status updates)? is registering for these "CallDisconnect" events best practice? Those are the easiest, as they are already "*e" events and they refer to the CallId directly, while the "'h" things seem to use yet another call id "422" (as well as being fairly verbose)
Ideally such a situation would result in a
type response, but since it doesn't I guess I'll have to work with the CallDisconnect events.
Is there any documentation available for the "CauseValue" constants?
Suggestions are most welcome
- Frode
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 02-09-2009 02:23:06 PM
Frode,
I'd register this:
Then you get the following response:
So you DO get your ideal situation with the ghost=True message! (see line 21)
The *h is call history (run the command "xHistory")
ps: I strongly discourage ever using xfeedback register * in an application :-)
I don't have a complete list of the cause codes, but many of them actually date back from good old ISDN days - you can find some of the most common cause codes here: http://networking.ringofsaturn.com/RemoteAccess/isdncausecodes.php
David
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Frode M on 02-09-2009 02:28:17 PM
I don't get the ghost=true line. This is what I get:
... which is good enough, I guess. Very strange though, that I don't get the "*s Call" lines you get?
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 02-09-2009 02:49:26 PM
I have just tested on my C90 with same sw version as you are using and I get the ghost=True feedback. Strange!
You don't seem to get ANY status feedback! Could you run "xfeed list" to list the registered expressions and make sure that status/call is there?
If not it could be that you have run out of expressions - in TC2.0 you can register a maximum of 13 expressions in total - if you have multiple connections to the codec (serial + ssh = 2) they may already have used some of the slots. (although in TC2.0 you should get the warning "You have reached the maximum number of feedback expressions on this system."
iif still no luck, please try to reboot and try again and see if that has any effect.
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Frode M on 02-09-2009 02:59:01 PM
Sure:
The status/call feedback works because I get "*s Call " status when I dial a working number.
Haven't tried rebooting yet, but I noticed the calldisconnect cause I get is different from yours. It might be related to the fact that I haven't set up a h323 gatekeeper? I noticed that if I try to force sip with an invalid number, I *do* get "*s call" statuses:
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 02-09-2009 03:06:04 PM
Spot on! :-)
Yes, I get the same as you when i deregistered my system from the gatekeeper.
This is a bug and I'll file it in our bug-system!
Thank you for your help and until fixed I suggest using the *e CallDisconnect event if the setup requires dialling on IP
David
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Frode M on 02-09-2009 03:11:56 PM
Excellent, thanks for your help as well
- Frode
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Øyvind Ludvigsen on 24-09-2010 03:46:46 PM
Hi David.
I strongly discourage ever using xfeedback register * in an application :-)
Can you elaborate on this ?
I have a C60 running and sometimes i get into a state where i dont get any more feedbacks on call status, other feedbacks registered such as xfeedback register Status/Audio is still reporting and in good shape
To confirm that this was not an issue with our software I (when in state described above)
used telnet and logged into tandberg system and manually registered xfeedback register Status/Call without the system responding with any feedback to any calls.....
doing xstatus call command in telnet on the other hand reports on the correct call states
The system stays in this state (no feedback on calls) until i reset TandbergSystem. Then it's all good again.
This has happened to me a couple of times.
Is this a known bug ?
SystemInfo:
TC2.1.1.200802
TANDBERG Codec C60
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 24-09-2010 04:23:25 PM
Hi Øyvind!
Sure,
if you execute" xfeedback register *" the codec will give feedback on ALL status changes, events and configuration changes. If you use ssh or telnet and do little handling of the feedback then things are probably ok, however if you use serial or your application does some processing of the feedback data then you might end up with data flooding. And for every feature we add to the codec in new firmwares this will become subsequently worse. Therefore, register only for the feedback your application needs.
Is this on serial or ssh/telnet?
We have seen this in older firmware versions. We recommend that the firmware is upgraded to TC 3.x.
Cheers,
David
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Øyvind Ludvigsen on 28-09-2010 02:03:22 PM
Thnx David
This is on a telnet connection
We will try to update firmware
Øyvind
Created by: Frode M on 02-09-2009 12:55:37 PM
Hi, I'm wondering what is the recommended method for observing call statuses. Currently I've registered a listener with
1xFeedback register status/call
which seems to work fine for regular calls (I get status events with "status: connecting", "status: connected", etc and a "(ghost=true)" entry when the call is gone. But when placing a call to an invalid number, such as with
1xCommand Dial Number: "invalid"
I get a response like this:1*r DialResult (status=OK):
2 CallId: 31
3 ConferenceId: 29
4** end
2 CallId: 31
3 ConferenceId: 29
4** end
but then no call status events are produced. "xStat call" shows 0 active calls.
By using "xFeedback register *", there seems to be a few events to choose from, to detect such a failed dial command:
1*h CallLogs Call 422 CallId: 31
2*h CallLogs Call 422 Protocol: "h323"
3*h CallLogs Call 422 Direction: Outgoing
4*h CallLogs Call 422 CallType: Unknown
5*h CallLogs Call 422 RemoteNumber: "h323:invalid"
6*h CallLogs Call 422 CallbackNumber: "h323:invalid"
7*h CallLogs Call 422 DisplayName: ""
8*h CallLogs Call 422 CallRate: 0
9*h CallLogs Call 422 DisconnectCauseValue: 11
10*h CallLogs Call 422 DisconnectCause: "MC:Caller not registered"
11*h CallLogs Call 422 StartTime: "2009/09/02 10:42:22"
12*h CallLogs Call 422 Duration: 0
13*h CallLogs Call 422 Encryption: "None"
14**end
15(.....)
16*h CallLogs Call 422 RemoteNumber: "h323:invalid"
17** end
18*h CallLogs Call 422 CallbackNumber: "h323:invalid"
19** end
20*h CallLogs Call 422 DisplayName: ""
21** end
22*h CallLogs Call 422 CallRate: 0
23** end
24*h CallLogs Call 422 DisconnectCauseValue: 11
25** end
26*h CallLogs Call 422 DisconnectCause: "MC:Caller not registered"
27** end
28(....)
2*h CallLogs Call 422 Protocol: "h323"
3*h CallLogs Call 422 Direction: Outgoing
4*h CallLogs Call 422 CallType: Unknown
5*h CallLogs Call 422 RemoteNumber: "h323:invalid"
6*h CallLogs Call 422 CallbackNumber: "h323:invalid"
7*h CallLogs Call 422 DisplayName: ""
8*h CallLogs Call 422 CallRate: 0
9*h CallLogs Call 422 DisconnectCauseValue: 11
10*h CallLogs Call 422 DisconnectCause: "MC:Caller not registered"
11*h CallLogs Call 422 StartTime: "2009/09/02 10:42:22"
12*h CallLogs Call 422 Duration: 0
13*h CallLogs Call 422 Encryption: "None"
14**end
15(.....)
16*h CallLogs Call 422 RemoteNumber: "h323:invalid"
17** end
18*h CallLogs Call 422 CallbackNumber: "h323:invalid"
19** end
20*h CallLogs Call 422 DisplayName: ""
21** end
22*h CallLogs Call 422 CallRate: 0
23** end
24*h CallLogs Call 422 DisconnectCauseValue: 11
25** end
26*h CallLogs Call 422 DisconnectCause: "MC:Caller not registered"
27** end
28(....)
and
1*e CallDisconnect CallId: 31 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
2** end
3*e CallDisconnect CallId: 31 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
4** end
5*e CallDisconnect CallId: 31 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
6** end
2** end
3*e CallDisconnect CallId: 31 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
4** end
5*e CallDisconnect CallId: 31 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
6** end
I can't recall having seen the "*h" response types before. What are these (compared to "*e" events and "*s" status updates)? is registering for these "CallDisconnect" events best practice? Those are the easiest, as they are already "*e" events and they refer to the CallId directly, while the "'h" things seem to use yet another call id "422" (as well as being fairly verbose)
Ideally such a situation would result in a
1*s Call 31 (ghost=True):
2** end
2** end
type response, but since it doesn't I guess I'll have to work with the CallDisconnect events.
Is there any documentation available for the "CauseValue" constants?
Suggestions are most welcome
- Frode
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 02-09-2009 02:23:06 PM
Frode,
I'd register this:
1xfeedback register event/CallDisconnect
2xfeedback register status/call
2xfeedback register status/call
Then you get the following response:
1xCommand Dial Number: "invalid"
2
3OK
4*r DialResult (status=OK):
5 CallId: 5
6 ConferenceId: 4
7** end
8*s Call 5 Status: Dialling
9*s Call 5 Direction: Outgoing
10*s Call 5 Protocol: "h323"
11*s Call 5 RemoteNumber: "invalid"
12*s Call 5 CallbackNumber: "h323:invalid"
13*s Call 5 DisplayName: ""
14*s Call 5 TransmitCallRate: 0
15*s Call 5 ReceiveCallRate: 768
16*s Call 5 Encryption Type: "Aes-128"
17*s Call 5 PlacedOnHold: False
18** end
19*e CallDisconnect CallId: 5 CauseValue: "network_rejected" CauseString: "MC:Request denied" OrigCallDirection: "outgoing"
20** end
21*s Call 5 (ghost=True):
22** end
2
3OK
4*r DialResult (status=OK):
5 CallId: 5
6 ConferenceId: 4
7** end
8*s Call 5 Status: Dialling
9*s Call 5 Direction: Outgoing
10*s Call 5 Protocol: "h323"
11*s Call 5 RemoteNumber: "invalid"
12*s Call 5 CallbackNumber: "h323:invalid"
13*s Call 5 DisplayName: ""
14*s Call 5 TransmitCallRate: 0
15*s Call 5 ReceiveCallRate: 768
16*s Call 5 Encryption Type: "Aes-128"
17*s Call 5 PlacedOnHold: False
18** end
19*e CallDisconnect CallId: 5 CauseValue: "network_rejected" CauseString: "MC:Request denied" OrigCallDirection: "outgoing"
20** end
21*s Call 5 (ghost=True):
22** end
So you DO get your ideal situation with the ghost=True message! (see line 21)
The *h is call history (run the command "xHistory")
ps: I strongly discourage ever using xfeedback register * in an application :-)
I don't have a complete list of the cause codes, but many of them actually date back from good old ISDN days - you can find some of the most common cause codes here: http://networking.ringofsaturn.com/RemoteAccess/isdncausecodes.php
David
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Frode M on 02-09-2009 02:28:17 PM
I don't get the ghost=true line. This is what I get:
1
2Welcome to c90.2
3TANDBERG Codec Release TC2.0.0.191232
4SW Release Date: 2009-07-03
5
6OK
7
8xfeedback register event/CallDisconnect
9** end
10
11OK
12xfeedback register status/call
13** end
14
15OK
16xCommand Dial Number: "invalid"
17
18OK
19*r DialResult (status=OK):
20 CallId: 43
21 ConferenceId: 41
22** end
23*e CallDisconnect CallId: 43 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
24** end
2Welcome to c90.2
3TANDBERG Codec Release TC2.0.0.191232
4SW Release Date: 2009-07-03
5
6OK
7
8xfeedback register event/CallDisconnect
9** end
10
11OK
12xfeedback register status/call
13** end
14
15OK
16xCommand Dial Number: "invalid"
17
18OK
19*r DialResult (status=OK):
20 CallId: 43
21 ConferenceId: 41
22** end
23*e CallDisconnect CallId: 43 CauseValue: 11 CauseString: "MC:Caller not registered" OrigCallDirection: "outgoing"
24** end
... which is good enough, I guess. Very strange though, that I don't get the "*s Call" lines you get?
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 02-09-2009 02:49:26 PM
I have just tested on my C90 with same sw version as you are using and I get the ghost=True feedback. Strange!
You don't seem to get ANY status feedback! Could you run "xfeed list" to list the registered expressions and make sure that status/call is there?
If not it could be that you have run out of expressions - in TC2.0 you can register a maximum of 13 expressions in total - if you have multiple connections to the codec (serial + ssh = 2) they may already have used some of the slots. (although in TC2.0 you should get the warning "You have reached the maximum number of feedback expressions on this system."
iif still no luck, please try to reboot and try again and see if that has any effect.
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Frode M on 02-09-2009 02:59:01 PM
Sure:
1xfeed list
2event/CallDisconnect
3status/call
4** end
2event/CallDisconnect
3status/call
4** end
The status/call feedback works because I get "*s Call " status when I dial a working number.
Haven't tried rebooting yet, but I noticed the calldisconnect cause I get is different from yours. It might be related to the fact that I haven't set up a h323 gatekeeper? I noticed that if I try to force sip with an invalid number, I *do* get "*s call" statuses:
1xCommand Dial Number: "sip:invalid"
2
3OK
4*r DialResult (status=OK):
5 CallId: 50
6 ConferenceId: 48
7** end
8*s Call 50 Status: Dialling
9*s Call 50 Direction: Outgoing
10*s Call 50 Protocol: "sip"
11*s Call 50 RemoteNumber: "invalid"
12*s Call 50 CallbackNumber: "sip:invalid"
13*s Call 50 DisplayName: ""
14*s Call 50 CallRate: 768
15*s Call 50 TransmitCallRate: 0
16*s Call 50 ReceiveCallRate: 768
17*s Call 50 Encryption Type: "Aes-128"
18*s Call 50 PlacedOnHold: False
19** end
20*e CallDisconnect CallId: 50 CauseValue: 11 CauseString: "MC:DNS Failure" OrigCallDirection: "outgoing"
21** end
22*s Call 50 (ghost=True):
23** end
2
3OK
4*r DialResult (status=OK):
5 CallId: 50
6 ConferenceId: 48
7** end
8*s Call 50 Status: Dialling
9*s Call 50 Direction: Outgoing
10*s Call 50 Protocol: "sip"
11*s Call 50 RemoteNumber: "invalid"
12*s Call 50 CallbackNumber: "sip:invalid"
13*s Call 50 DisplayName: ""
14*s Call 50 CallRate: 768
15*s Call 50 TransmitCallRate: 0
16*s Call 50 ReceiveCallRate: 768
17*s Call 50 Encryption Type: "Aes-128"
18*s Call 50 PlacedOnHold: False
19** end
20*e CallDisconnect CallId: 50 CauseValue: 11 CauseString: "MC:DNS Failure" OrigCallDirection: "outgoing"
21** end
22*s Call 50 (ghost=True):
23** end
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 02-09-2009 03:06:04 PM
Spot on! :-)
Yes, I get the same as you when i deregistered my system from the gatekeeper.
This is a bug and I'll file it in our bug-system!
Thank you for your help and until fixed I suggest using the *e CallDisconnect event if the setup requires dialling on IP
David
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Frode M on 02-09-2009 03:11:56 PM
David A Bruun-Lie:Spot on! :-)
Yes, I get the same as you when i deregistered my system from the gatekeeper.
This is a bug and I'll file it in our bug-system!
Thank you for your help and until fixed I suggest using the *e CallDisconnect event if the setup requires dialling on IP
David
Excellent, thanks for your help as well
- Frode
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Øyvind Ludvigsen on 24-09-2010 03:46:46 PM
Hi David.
I strongly discourage ever using xfeedback register * in an application :-)
Can you elaborate on this ?
I have a C60 running and sometimes i get into a state where i dont get any more feedbacks on call status, other feedbacks registered such as xfeedback register Status/Audio is still reporting and in good shape
To confirm that this was not an issue with our software I (when in state described above)
used telnet and logged into tandberg system and manually registered xfeedback register Status/Call without the system responding with any feedback to any calls.....
doing xstatus call command in telnet on the other hand reports on the correct call states
The system stays in this state (no feedback on calls) until i reset TandbergSystem. Then it's all good again.
This has happened to me a couple of times.
Is this a known bug ?
SystemInfo:
TC2.1.1.200802
TANDBERG Codec C60
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: David Bruun-Lie on 24-09-2010 04:23:25 PM
Hi Øyvind!
Øyvind Ludvigsen:Hi David.
I strongly discourage ever using xfeedback register * in an application :-)
Can you elaborate on this ?
Sure,
if you execute" xfeedback register *" the codec will give feedback on ALL status changes, events and configuration changes. If you use ssh or telnet and do little handling of the feedback then things are probably ok, however if you use serial or your application does some processing of the feedback data then you might end up with data flooding. And for every feature we add to the codec in new firmwares this will become subsequently worse. Therefore, register only for the feedback your application needs.
Øyvind Ludvigsen:
I have a C60 running and sometimes i get into a state where i dont get any more feedbacks on call status, other feedbacks registered such as xfeedback register Status/Audio is still reporting and in good shape
To confirm that this was not an issue with our software I (when in state described above)
used telnet and logged into tandberg system and manually registered xfeedback register Status/Call without the system responding with any feedback to any calls.....
doing xstatus call command in telnet on the other hand reports on the correct call states
The system stays in this state (no feedback on calls) until i reset TandbergSystem. Then it's all good again.
This has happened to me a couple of times.
Is this a known bug ?
SystemInfo:
TC2.1.1.200802
TANDBERG Codec C60
Is this on serial or ssh/telnet?
We have seen this in older firmware versions. We recommend that the firmware is upgraded to TC 3.x.
Cheers,
David
Subject: RE: Call disconnect status/event when dialing invalid number
Replied by: Øyvind Ludvigsen on 28-09-2010 02:03:22 PM
Thnx David
This is on a telnet connection
We will try to update firmware
Øyvind