I checked this as well - I don’t think that the flag “directional” ever
makes it from opensips to rtpengine
On 21 Jan 2025 at 23:27:56, Alberto <alberto.rina...@gmail.com> wrote:
> Hi Răzvan,
>
> Thanks, but then I don't know what I'm doing wrong.
>
> Here's a piece of my config:
>
> branch_route[invite_branch_route] {
> if (has_body("application/sdp")) {
> xlog("L_NOTICE", "[ln $cfg_line] [$ci | $si | $rm] Start rtp
> streams\n");
> rtpengine_manage("directional RTP/AVP trust-address replace-origin
> replace-session-connection codec-strip-all codec-except-telephone-event
> codec-except-CN codec-except-PCMA");
> }
> }
>
> onreply_route[invite_onreply_route] {
> $acc_extra(callee_domain) = $si;
>
> if (has_body("application/sdp")) {
> xlog("L_NOTICE", "[ln $cfg_line] [$ci | $si | $rm | $rs] Update rtp
> streams\n");
> rtpengine_manage();
>
> xlog("L_NOTICE", "[ln $cfg_line] [$ci | $si | $rm | $rs] Block DTMF
> from $tt\n");
> rtpengine_block_dtmf("directional from-tag=$tt");
> }
> }
>
> I wasn't sure where to put the directional flag, so I tried first in
> rtpengine_manage, then in rtpengine_block_dtmf, then in both. Result is the
> same, DTMF are always blocked for the entire call.
>
> Logs from opensips:
> Jan 21 23:22:26 local-opensips opensips[2027]: Jan 21 23:22:26 [2027]
> NOTICE:[ln 361] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | INVITE]
> t_relay
> Jan 21 23:22:26 local-opensips opensips[2027]: Jan 21 23:22:26 [2027]
> NOTICE:[ln 371] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | INVITE]
> Start rtp streams
> Jan 21 23:22:26 local-opensips opensips[2029]: Jan 21 23:22:26 [2029]
> NOTICE:[ln 380] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.46 | INVITE
> | 200] Update rtp streams
> Jan 21 23:22:26 local-opensips opensips[2029]: Jan 21 23:22:26 [2029]
> NOTICE:[ln 383] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.46 | INVITE
> | 200] Block DTMF from a369dd65-3212-4728-a22d-4bcdd0857b39
> Jan 21 23:22:26 local-opensips opensips[2029]: Jan 21 23:22:26 [2029]
> NOTICE:[ln 271] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | ACK]
> topology_hiding_match OK
> Jan 21 23:22:26 local-opensips opensips[2029]: Jan 21 23:22:26 [2029]
> NOTICE:[ln 300] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | ACK]
> t_relay
> Jan 21 23:22:33 local-opensips opensips[2027]: Jan 21 23:22:33 [2027]
> NOTICE:[ln 271] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | BYE]
> topology_hiding_match OK
> Jan 21 23:22:33 local-opensips opensips[2027]: Jan 21 23:22:33 [2027]
> NOTICE:[ln 296] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | BYE]
> Close rtp streams if any
> Jan 21 23:22:33 local-opensips opensips[2027]: Jan 21 23:22:33 [2027]
> NOTICE:[ln 300] [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc | 10.0.0.69 | BYE]
> t_relay
>
> Logs from rtpengine:
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Received command 'offer'
> from 127.0.0.1:52434
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [core] replace-session-connection
> flag encountered, but not supported anymore.
> Jan 21 23:22:26 local-opensips rtpengine[1254]: NOTICE:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [core] Creating new call
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Replying to 'offer' from
> 127.0.0.1:52434 (elapsed time 0.000364 sec)
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Received command 'answer'
> from 127.0.0.1:38934
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Replying to 'answer' from
> 127.0.0.1:38934 (elapsed time 0.000505 sec)
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Received command 'block
> DTMF' from 127.0.0.1:38934
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [core] Blocking DTMF (entire call)
> Jan 21 23:22:26 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Replying to 'block DTMF'
> from 127.0.0.1:38934 (elapsed time 0.000037 sec)
> Jan 21 23:22:30 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc/63c659c2-ff03-4673-a4f9-96a145ec6d45/1
> port 28640]: [core] Confirmed peer address as 10.0.0.69:19446
> Jan 21 23:22:30 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc/63c659c2-ff03-4673-a4f9-96a145ec6d45/1
> port 28640]: [core] Kernelizing media stream: 10.0.0.69:19446 ->
> 10.0.0.18:28640 | 10.0.0.18:31230 -> 10.0.0.46:19502
> Jan 21 23:22:31 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc/63c659c2-ff03-4673-a4f9-96a145ec6d45/1
> port 28641]: [core] Confirmed peer address as 10.0.0.69:19447
> Jan 21 23:22:31 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc/63c659c2-ff03-4673-a4f9-96a145ec6d45/1
> port 28641]: [core] Kernelizing media stream: 10.0.0.69:19447 ->
> 10.0.0.18:28641 | 10.0.0.18:31231 -> 10.0.0.46:19503
> Jan 21 23:22:31 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc/a369dd65-3212-4728-a22d-4bcdd0857b39/1
> port 31231]: [core] Confirmed peer address as 10.0.0.46:19503
> Jan 21 23:22:31 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc/a369dd65-3212-4728-a22d-4bcdd0857b39/1
> port 31231]: [core] Kernelizing media stream: 10.0.0.46:19503 ->
> 10.0.0.18:31231 | 10.0.0.18:28641 -> 10.0.0.69:19447
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Received command 'query'
> from 127.0.0.1:52434
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Replying to 'query' from
> 127.0.0.1:52434 (elapsed time 0.000230 sec)
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Received command 'delete'
> from 127.0.0.1:52434
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [core] Scheduling deletion of call
> branch '63c659c2-ff03-4673-a4f9-96a145ec6d45' (via-branch '') in 30 seconds
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [core] Scheduling deletion of call
> branch 'a369dd65-3212-4728-a22d-4bcdd0857b39' (via-branch '') in 30 seconds
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [core] Scheduling deletion of
> entire call in 30 seconds
> Jan 21 23:22:33 local-opensips rtpengine[1254]: INFO:
> [ef0c76ea-adbc-4a09-bf2d-9df7f6f872bc]: [control] Replying to 'delete' from
> 127.0.0.1:52434 (elapsed time 0.000232 sec)
>
>
> On Tue, 21 Jan 2025 at 15:10, Răzvan Crainea <raz...@opensips.org> wrote:
>
>> Hi, Alberto!
>>
>> Nothing to do explicitely in opensips, simply pass the "directional"
>> flag to the command.
>>
>> Best regards,
>>
>> Răzvan Crainea
>> OpenSIPS Core Developer / SIPhub CTO
>> http://www.opensips-solutions.com / https://www.siphub.com
>>
>> On 1/21/25 1:47 AM, Alberto wrote:
>> > Hi,
>> >
>> > In short, I was using opensips 3.4.8 and rtpengine 11.5 until a few days
>> > ago, and rtpengine_block_dtmf was able to block DTMF in a single
>> direction.
>> > Recently I updated rtpengine to 12.5 and that stopped working, now DTMF
>> are
>> > always blocked in both directions.
>> >
>> > Can someone please take a look at
>> > https://groups.google.com/g/rtpengine/c/4dFexHvFmeo/m/YxTxXylXDAAJ ?
>> > Is this something that needs to be implemented in opensips?
>> >
>> > Thanks
>> >
>> >
>> > Hi,
>> >
>> > In short, I was using opensips 3.4.8 and rtpengine 11.5 until a few
>> days
>> > ago, and rtpengine_block_dtmf was able to block DTMF in a single
>> direction.
>> > Recently I updated rtpengine to 12.5 and that stopped working, now DTMF
>> > are always blocked in both directions.
>> >
>> > Can someone please take a look at
>> https://groups.google.com/g/rtpengine/
>> > c/4dFexHvFmeo/m/YxTxXylXDAAJ <https://groups.google.com/g/rtpengine/
>> > c/4dFexHvFmeo/m/YxTxXylXDAAJ> ?
>> > Is this something that needs to be implemented in opensips?
>> >
>> > Thanks
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users@lists.opensips.org
>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
