On 04/23/2014 12:08 PM, Richard Fuchs wrote:
Can you please clarify: does it not send anything at all, or does it send an answer instead of an offer?
Well, I suppose I can't say for sure, but it looks like it's not sending anything at all. When I grep a particular Call-ID, the first thing I get is:
Apr 23 15:28:37 sd-rtp01 mediaproxy-ng[7910]: Got valid command from xxx.xxx.xxx.xxx:43733: answer - { "sdp": "v=0#015#012o=- 1398266077 1398266077 IN IP4 xxx.xxx.xxx.xxx#015#012s=VOS2009#015#012c=IN IP4 yyy.yyy.yyy.yyy#015#012t=0 0#015#012m=audio 33576 RTP/AVP 18 101#015#012a=rtpmap:18 G729/8000#015#012a=fmtp:18 annexb=no#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-16#015#012", "replace": [ "origin" ], "call-id": "15109646-3607255707-160030@xxx", "received-from": [ "IP4", "xxx.xxx.xxx.xxx" ], "from-tag": "3607255707-160035", "to-tag": "Fa1Fe4ZSvBQSF", "command": "answer" }
If my understanding of the control protocol is correct, this is actually an answer, not a mislabeled offer, since the offer would contain some other attributes.
But maybe not?
I expect an answer because I have an rtpproxy_manage() in an onreply_route for 18x/2xx+SDP responses to this INVITE, of course.