Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

query command not returning "streams" element #3

Closed
bhlangonijr opened this issue Apr 22, 2014 · 4 comments
Closed

query command not returning "streams" element #3

bhlangonijr opened this issue Apr 22, 2014 · 4 comments

Comments

@bhlangonijr
Copy link

Hello,

I developed a java client for rtpengine using the ng protocol. Everything went fine until I tried to retrieve channel stats by issuing a 'query' command and passing the call-id of the current streaming as the only parameter. I only got the 'result=ok' and so there was missing the 'streams' element with all channels stats as described in the documentation: https://github.com/sipwise/rtpengine#query-message

Any thoughts? Below the relevant log parts in linux syslog:

Thanks!

Apr 22 02:02:07 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: ping - { "command": "ping" }
Apr 22 02:02:07 bhlangonijr-lap rtpengine[12389]: Returning to SIP proxy: d6:result4:ponge
Apr 22 02:02:08 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: offer - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "offer", "flags": [ "trust address" ], "from-tag": "alice.vlncco4_24130402@127.0.0.1", "sdp": "v=0#015#012o=root 123 123 IN IP4 127.0.0.1#015#012s=stream#015#012c=IN IP4 127.0.0.1#015#012t=0 0#015#012m=audio 20000 RTP/AVP#015#012" }
Apr 22 02:02:08 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Creating new call
Apr 22 02:02:08 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d3:sdp342:v=0#015#012o=root 123 123 IN IP4 127.0.0.1#015#012s=stream#015#012c=IN IP4 127.0.0.1#015#012t=0 0#015#012a=ice-lite#015#012m=audio 30060 RTP/AVP#015#012a=sendrecv#015#012a=rtcp:30061#015#012a=ice-ufrag:lQuPNmPc#015#012a=ice-pwd:mQy8MinKorIo1lVmpDJ6ZkbiaD7Y#015#012a=candidate:88bsieY2c5oyVJlM 1 UDP 2130706432 127.0.0.1 30060 typ host#015#012a=candidate:88bsieY2c5oyVJlM 2 UDP 2130706431 127.0.0.1 30061 typ host#015#0126:result2:oke
Apr 22 02:02:08 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: answer - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "answer", "flags": [ "trust address" ], "from-tag": "alice.vlncco4_24130402@127.0.0.1", "sdp": "v=0#015#012o=root 123 123 IN IP4 127.0.0.1#015#012s=stream#015#012c=IN IP4 127.0.0.1#015#012t=0 0#015#012m=audio 20002 RTP/AVP#015#012", "to-tag": "bob.vlncco4_24130402@127.0.0.1" }
Apr 22 02:02:08 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d3:sdp342:v=0#015#012o=root 123 123 IN IP4 127.0.0.1#015#012s=stream#015#012c=IN IP4 127.0.0.1#015#012t=0 0#015#012a=ice-lite#015#012m=audio 30062 RTP/AVP#015#012a=sendrecv#015#012a=rtcp:30063#015#012a=ice-ufrag:XV8kLGqx#015#012a=ice-pwd:WNiidYHejCAJejNbDWrMzxIxsQPd#015#012a=candidate:88bsieY2c5oyVJlM 1 UDP 2130706432 127.0.0.1 30062 typ host#015#012a=candidate:88bsieY2c5oyVJlM 2 UDP 2130706431 127.0.0.1 30063 typ host#015#0126:result2:oke
Apr 22 02:02:13 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:13 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:18 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:18 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:23 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:23 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
^[[AApr 22 02:02:28 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:28 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:33 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:33 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:38 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:38 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:43 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:43 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:47 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: ping - { "command": "ping" }
Apr 22 02:02:47 bhlangonijr-lap rtpengine[12389]: Returning to SIP proxy: d6:result4:ponge
Apr 22 02:02:48 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:48 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:53 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:53 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:02:58 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:02:58 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:03:03 bhlangonijr-lap rtpengine[12389]: Got valid command from 127.0.0.1:18426: query - { "call-id": "vlncco4_24130402@127.0.0.1", "command": "query" }
Apr 22 02:03:03 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Returning to SIP proxy: d6:result2:oke
Apr 22 02:03:10 bhlangonijr-lap NetworkManager[1176]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: Closing call branch due to timeout
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] Final packet stats:
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] --- Tag 'bob.vlncco4_24130402@127.0.0.1', created 2:01 ago, in dialogue with 'alice.vlncco4_24130402@127.0.0.1'
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] ------ Media #1, port 30062 <>       127.0.0.1:6020 , 5992 p, 947940 b, 0 e
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] ------ Media #1, port 30063 <>       127.0.0.1:6021  (RTCP), 37 p, 2868 b, 0 e
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] --- Tag 'alice.vlncco4_24130402@127.0.0.1', created 2:01 ago, in dialogue with 'bob.vlncco4_24130402@127.0.0.1'
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] ------ Media #1, port 30060 <>       127.0.0.1:6022 , 5991 p, 947904 b, 0 e
Apr 22 02:04:09 bhlangonijr-lap rtpengine[12389]: [vlncco4_24130402@127.0.0.1] ------ Media #1, port 30061 <>       127.0.0.1:6023  (RTCP), 31 p, 2484 b, 0 e
@rfuchs
Copy link
Member

rfuchs commented Apr 22, 2014

Hi,

The stats output (both for "delete" and "query") is not implemented at this time. The layout of the response (as seen in the docs) will have to be redesigned to accommodate the new internal stream handling and I haven't gotten around to it. Should be fixed in the coming weeks.

@bhlangonijr
Copy link
Author

Thanks for the quick reply.
Is there any other way to get this info (channel stats)? I would hate to fallback to the old rtpproxy protocol. By the way, does the XMLRPC "call killer" callback method work if you use ng protocol for setting up the relayed call?

Thanks again.

@rfuchs
Copy link
Member

rfuchs commented Apr 22, 2014

Right now, no there isn't, all the relevant code is just commented out and waiting to be re-implemented. Do you need this urgently?

@bhlangonijr
Copy link
Author

Yes, I was betting on that for a production case... :)
Are you available for chatting? So I can explain you the details. In case you are available please drop me an email at bhlangonijr at gmail.com with your contact.

@rfuchs rfuchs closed this as completed in 011a426 Apr 30, 2014
@SipSeb SipSeb mentioned this issue Jan 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants