Discussion:
[SR-Users] Kamamilio ignores RTP engine returned string
Yuriy Gorlichenko
2014-07-16 21:25:09 UTC
Permalink
Hello Rtpengine (rtpproxy-ng module) works fine with kamailio till today.

Without any changes at kamailio or rtpengine kamailio ignores changed by
rtpengine SDP content.

To check this I use sdp_get() and after tying to call I print avp from this
function and returned sdp body by rtpengine != this content

My log:

Jul 16 17:17:27 test rtpengine[5521]: Got valid command from 127.0.0.1:36484:
offer - { "sdp": "v=0#015#012o=- 8380958077563183406 2 IN IP4
127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE
audio#015#012a=msid-semantic: WMS
o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE#015#012m=audio 56984 UDP/TLS/RTP/SAVPF
111 103 104 0 8 106 105 13 126#015#012c=IN IP4
192.168.56.1#015#012a=rtcp:56984 IN IP4
192.168.56.1#015#012a=candidate:2999745851 1 udp 2122260223 192.168.56.1
56984 typ host generation 0#015#012a=candidate:2999745851 2 udp 2122260223
192.168.56.1 56984 typ host generation 0#015#012a=candidate:2448668656 1
udp 2122194687 192.168.142.1 56985 typ host generation
0#015#012a=candidate:2448668656 2 udp 2122194687 192.168.142.1 56985 typ
host generation 0#015#012a=candidate:1206525147 1 udp 2122129151
192.168.2.120 56986 typ host generation 0#015#012a=candidate:1206525147 2
udp 2122129151 192.168.2.120 56986 typ host generation
0#015#012a=candidate:3374335715 1 udp 2122063615 10.34.8.7 56987 typ host
generation 0#015#012a=candidate:3374335715 2 udp 2122063615 10.34.8.7 56987
typ host generation 0#015#012a=candidate:2602400937 1 udp 2121998079
192.168.214.1 56988 typ host generation 0#015#012a=candidate:2602400937 2
udp 2121998079 192.168.214.1 56988 typ host generation
0#015#012a=candidate:4233069003 1 tcp 1518280447 192.168.56.1 0 typ host
generation 0#015#012a=candidate:4233069003 2 tcp 1518280447 192.168.56.1 0
typ host generation 0#015#012a=candidate:3748678400 1 tcp 1518214911
192.168.142.1 0 typ host generation 0#015#012a=candidate:3748678400 2 tcp
1518214911 192.168.142.1 0 typ host generation
0#015#012a=candidate:157933611 1 tcp 1518149375 192.168.2.120 0 typ host
generation 0#015#012a=candidate:157933611 2 tcp 1518149375 192.168.2.120 0
typ host generation 0#015#012a=candidate:2275654163 1 tcp 1518083839
10.34.8.7 0 typ host generation 0#015#012a=candidate:2275654163 2 tcp
1518083839 10.34.8.7 0 typ host generation 0#015#012a=candidate:3583934553
1 tcp 1518018303 192.168.214.1 0 typ host generation
0#015#012a=candidate:3583934553 2 tcp 1518018303 192.168.214.1 0 typ host
generation
0#015#012a=ice-ufrag:Oglxt4kDKBr8sfXY#015#012a=ice-pwd:iZAp/WE5TCqIoPA0hIpxztqq#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256
E3:E7:04:57:80:03:27:12:D6:88:F6:E7:3E:64:4A:55:DA:AD:3F:DA:4E:41:6E:6F:F0:D0:69:A6:AB:AE:79:4F#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1
urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=extmap:3
http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time#015#012a=sendrecv#015#012a=rtcp-mux#015#012a=rtpmap:111
opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103
ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106
CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13
CN/8000#015#012a=rtpmap:126
telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:3151729659
cname:wvwdxd7V5hVETGHP#015#012a=ssrc:3151729659
msid:o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE
bdfb98b7-2eed-4d85-bdbb-b097df5c09f2#015#012a=ssrc:3151729659
mslabel:o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE#015#012a=ssrc:3151729659
label:bdfb98b7-2eed-4d85-bdbb-b097df5c09f2#015#012", "ICE": "remove",
"flags": [ "force", "trust-address" ], "replace": [ "origin",
"session-connection" ], "transport-protocol": "RTP/AVP", "call-id":
"60m6hpu9sclqnjvhql2q", "received-from": [ "IP4", "213.108.168.163" ],
"from-tag": "6oo4g9fr4c", "command": "offer" }

Jul 16 17:17:27 test rtpengine[5521]: Unknown flag encountered: 'force'

Jul 16 17:17:27 test rtpengine[5521]: [60m6hpu9sclqnjvhql2q] Creating new
call

Jul 16 17:17:27 test rtpengine[5521]: [60m6hpu9sclqnjvhql2q] Returning to
SIP proxy: d3:sdp770:v=0#015#012o=- 8380958077563183406 2 IN IP4
123.33.24.45#015#012s=-#015#012t=0 0#015#012a=msid-semantic: WMS
o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE#015#012m=audio 30008 RTP/AVP 111 103
104 0 8 106 105 13 126#015#012c=IN IP4 123.33.24.45#015#012a=rtpmap:111
opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103
ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106
CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13
CN/8000#015#012a=rtpmap:126
telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:3151729659
cname:wvwdxd7V5hVETGHP#015#012a=ssrc:3151729659
msid:o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE
bdfb98b7-2eed-4d85-bdbb-b097df5c09f2#015#012a=ssrc:3151729659
mslabel:o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE#015#012a=ssrc:3151729659
label:bdfb98b7-2eed-4d85-bdbb-b097df5c09f2#015#012a=sendrecv#015#012a=rtcp:30009#015#012a=rtcp-mux#015#0126:result2:oke

Jul 16 17:17:27 test /usr/sbin/kamailio[6969]: INFO: <script>: Faltured
{INVITE}

Jul 16 17:17:27 test /usr/sbin/kamailio[6969]: INFO: <script>: This is not
falture {INVITE}

Jul 16 17:17:27 test /usr/sbin/kamailio[6969]: INFO: <script>: SDP is
{v=0#015#012o=- 8380958077563183406 2 IN IP4
127.0.0.1#015#012s=-#015#012t=0 0#015#012a=group:BUNDLE
audio#015#012a=msid-semantic: WMS
o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE#015#012m=audio 56984 UDP/TLS/RTP/SAVPF
111 103 104 0 8 106 105 13 126#015#012c=IN IP4
192.168.56.1#015#012a=rtcp:56984 IN IP4
192.168.56.1#015#012a=candidate:2999745851 1 udp 2122260223 192.168.56.1
56984 typ host generation 0#015#012a=candidate:2999745851 2 udp 2122260223
192.168.56.1 56984 typ host generation 0#015#012a=candidate:2448668656 1
udp 2122194687 192.168.142.1 56985 typ host generation
0#015#012a=candidate:2448668656 2 udp 2122194687 192.168.142.1 56985 typ
host generation 0#015#012a=candidate:1206525147 1 udp 2122129151
192.168.2.120 56986 typ host generation 0#015#012a=candidate:1206525147 2
udp 2122129151 192.168.2.120 56986 typ host generation
0#015#012a=candidate:3374335715 1 udp 2122063615 10.34.8.7 56987 typ host
generation 0#015#012a=candidate:3374335715 2 udp 2122063615 10.34.8.7 56987
typ host generation 0#015#012a=candidate:2602400937 1 udp 2121998079
192.168.214.1 56988 typ host generation 0#015#012a=candidate:2602400937 2
udp 2121998079 192.168.214.1 56988 typ host generation
0#015#012a=candidate:4233069003 1 tcp 1518280447 192.168.56.1 0 typ host
generation 0#015#012a=candidate:4233069003 2 tcp 1518280447 192.168.56.1 0
typ host generation 0#015#012a=candidate:3748678400 1 tcp 1518214911
192.168.142.1 0 typ host generation 0#015#012a=candidate:3748678400 2 tcp
1518214911 192.168.142.1 0 typ host generation
0#015#012a=candidate:157933611 1 tcp 1518149375 192.168.2.120 0 typ host
generation 0#015#012a=candidate:157933611 2 tcp 1518149375 192.168.2.120 0
typ host generation 0#015#012a=candidate:2275654163 1 tcp 1518083839
10.34.8.7 0 typ host generation 0#015#012a=candidate:2275654163 2 tcp
1518083839 10.34.8.7 0 typ host generation 0#015#012a=candidate:3583934553
1 tcp 1518018303 192.168.214.1 0 typ host generation
0#015#012a=candidate:3583934553 2 tcp 1518018303 192.168.214.1 0 typ host
generation
0#015#012a=ice-ufrag:Oglxt4kDKBr8sfXY#015#012a=ice-pwd:iZAp/WE5TCqIoPA0hIpxztqq#015#012a=ice-options:google-ice#015#012a=fingerprint:sha-256
E3:E7:04:57:80:03:27:12:D6:88:F6:E7:3E:64:4A:55:DA:AD:3F:DA:4E:41:6E:6F:F0:D0:69:A6:AB:AE:79:4F#015#012a=setup:actpass#015#012a=mid:audio#015#012a=extmap:1
urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=extmap:3
http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time#015#012a=sendrecv#015#012a=rtcp-mux#015#012a=rtpmap:111
opus/48000/2#015#012a=fmtp:111 minptime=10#015#012a=rtpmap:103
ISAC/16000#015#012a=rtpmap:104 ISAC/32000#015#012a=rtpmap:0
PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:106
CN/32000#015#012a=rtpmap:105 CN/16000#015#012a=rtpmap:13
CN/8000#015#012a=rtpmap:126
telephone-event/8000#015#012a=maxptime:60#015#012a=ssrc:3151729659
cname:wvwdxd7V5hVETGHP#015#012a=ssrc:3151729659
msid:o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE
bdfb98b7-2eed-4d85-bdbb-b097df5c09f2#015#012a=ssrc:3151729659
mslabel:o2PCyrMBSdtfFMt6oYXoSeBdfUskxKN6dWXE#015#012a=ssrc:3151729659
label:bdfb98b7-2eed-4d85-bdbb-b097df5c09f2#015#012}
Richard Fuchs
2014-07-16 21:37:52 UTC
Permalink
Post by Yuriy Gorlichenko
Hello Rtpengine (rtpproxy-ng module) works fine with kamailio till today.
Without any changes at kamailio or rtpengine kamailio ignores changed by
rtpengine SDP content.
To check this I use sdp_get() and after tying to call I print avp from
this function and returned sdp body by rtpengine != this content
I don't know if this answers your question, but you may not see the
changes to the SDP body within Kamailio until you call
msg_apply_changes() or actually send the message back out.

cheers
Yuriy Gorlichenko
2014-07-16 21:53:24 UTC
Permalink
I see SDP body at Asterisk behind kamamilio, And I see that body have no
changes.
Post by Richard Fuchs
Post by Yuriy Gorlichenko
Hello Rtpengine (rtpproxy-ng module) works fine with kamailio till today.
Without any changes at kamailio or rtpengine kamailio ignores changed by
rtpengine SDP content.
To check this I use sdp_get() and after tying to call I print avp from
this function and returned sdp body by rtpengine != this content
I don't know if this answers your question, but you may not see the
changes to the SDP body within Kamailio until you call
msg_apply_changes() or actually send the message back out.
cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Olli Heiskanen
2014-08-15 15:02:18 UTC
Permalink
Hello,

I don't know if this helps but I noticed you have a log entry:
Unknown flag encountered: 'force'

This is because rtpengine does not support this flag any more, it's
mentioned in the rtpengine module documentation:
http://kamailio.org/docs/modules/devel/modules/rtpengine.html#rtpengine.f.rtpengine_offer
You may want to try rtpengine module instead of rtpproxy-ng module, this is
just a guess but hopefully a good one.

I wonder do you have changes in Asterisk side? In my case changes in
Asterisk realtime table changed the behavior concerning sdp, you may want
to check that on your sip traces. In my setup Asterisk changed the sdp but
I'm not sure if this applies to your case.

I hope this helps any.

cheers,
Olli
Post by Yuriy Gorlichenko
I see SDP body at Asterisk behind kamamilio, And I see that body have no
changes.
Post by Yuriy Gorlichenko
Post by Yuriy Gorlichenko
Hello Rtpengine (rtpproxy-ng module) works fine with kamailio till
today.
Post by Yuriy Gorlichenko
Without any changes at kamailio or rtpengine kamailio ignores changed by
rtpengine SDP content.
To check this I use sdp_get() and after tying to call I print avp from
this function and returned sdp body by rtpengine != this content
I don't know if this answers your question, but you may not see the
changes to the SDP body within Kamailio until you call
msg_apply_changes() or actually send the message back out.
cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Loading...