Re: [OpenSIPS-Users] RTPEngine - changing codec format parameters from default values when transcoding - OpenSIPS 3.1

[Răzvan Crainea]

I think the proper way to do it is 
`transcode-opus/48000/2/32000//maxplaybackrate--48000;stereo--0;useinbandfec--1;maxaveragebitrate--32000`
Anyway, as Johan suggests, follow the rtpengine documentation, you will 
find more info there.


Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 9/14/21 15:51, Mark Allen wrote:

Hi Răzvan

OpenSIPS passes the commands to RTPengine as you supply them, so in
theory this should be supported. Did you try to set this up? Can you
provide any logs about this?


No. I'm not sure how I would specify this in the opensips.cfg 
rtpengine_offer parameters. From the documentation for the 
rptengine OpenSIPS module, it doesn't seem as if something like the 
following is an option...


 
transcode-opus='opus/48000/2/32000//maxplaybackrate=48000;stereo=0;useinbandfec=1;maxaveragebitrate=32000' 



...however, if I have tried this in the code (with or without quotes) it 
doesn't produce an error, either from OpenSIPS or rtpengine, but neither 
does it do anything - Opus fmtp in the SDP is not changed. I guess I'm 
looking for the correct OpenSIPS syntax to pass these parameters 
successfully to rtpengine




___
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

Re: [OpenSIPS-Users] RTPEngine - changing codec format parameters from default values when transcoding - OpenSIPS 3.1

[Johan De Clercq]

Follow the rtpengine documentation. The necessary flags are given there,
just pass them in an avp to rtpengine_offer or answer

On Tue, Sep 14, 2021, 14:55 Mark Allen  wrote:

> Hi Răzvan
>
> OpenSIPS passes the commands to RTPengine as you supply them, so in
>> theory this should be supported. Did you try to set this up? Can you
>> provide any logs about this?
>>
>>
> No. I'm not sure how I would specify this in the opensips.cfg
> rtpengine_offer parameters. From the documentation for the
> rptengine OpenSIPS module, it doesn't seem as if something like the
> following is an option...
>
>
> transcode-opus='opus/48000/2/32000//maxplaybackrate=48000;stereo=0;useinbandfec=1;maxaveragebitrate=32000
> '
>
> ...however, if I have tried this in the code (with or without quotes) it
> doesn't produce an error, either from OpenSIPS or rtpengine, but neither
> does it do anything - Opus fmtp in the SDP is not changed. I guess I'm
> looking for the correct OpenSIPS syntax to pass these parameters
> successfully to rtpengine
>
>
> ___
> 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

Re: [OpenSIPS-Users] RTPEngine - changing codec format parameters from default values when transcoding - OpenSIPS 3.1

[Mark Allen]

Hi Răzvan

OpenSIPS passes the commands to RTPengine as you supply them, so in
> theory this should be supported. Did you try to set this up? Can you
> provide any logs about this?
>
>
No. I'm not sure how I would specify this in the opensips.cfg
rtpengine_offer parameters. From the documentation for the
rptengine OpenSIPS module, it doesn't seem as if something like the
following is an option...


transcode-opus='opus/48000/2/32000//maxplaybackrate=48000;stereo=0;useinbandfec=1;maxaveragebitrate=32000
'

...however, if I have tried this in the code (with or without quotes) it
doesn't produce an error, either from OpenSIPS or rtpengine, but neither
does it do anything - Opus fmtp in the SDP is not changed. I guess I'm
looking for the correct OpenSIPS syntax to pass these parameters
successfully to rtpengine
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] 481 dialog does not exist issue

[Răzvan Crainea]

Hi, Vinayak!

OpenSIPS does not send 481 by itself - that code must have been returned 
from your script. Please provide more details about the script before we 
can give you more information.


Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 9/13/21 14:29, Vinayak Makwana wrote:

Hello all,
              I am facing issue 481 dialog does not exist for BYE 
packet.in  that I am using the record-route module. 
but when I sent the BYE packet at that time opensips send me 481 reply 
and i also observed the packet in that but not getting any dialog 
termination related issues like to-tag also .

Can anyone help me for this?

here is BYE packet,

20xx/xx/xx xx:xx:xx.715975 originator_pub_ip:port -> opensips_pub_ip:port
BYE sip:destination_pub_ip:port;transport=udp SIP/2.0
Via: SIP/2.0/UDP 
originator_pub_ip:port;rport;branch=z9hG4bKcbdf32009866-30-2e7d22

From: ;tag=bbd030726p
To: ;tag=ad147951571820219109630
Max-Forwards: 66
Call-ID: ae5a569f-22c9bc14-986912c2-e3626da0
User-Agent: xyz
CSeq: 2 BYE
Route: 
Content-Length: 0

*Disclaimer*
In addition to generic Disclaimer which you have agreed on our website, 
any views or opinions presented in this email are solely those of the 
originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from 
taking any action on the basis of any of the information contained in 
this email is hereby excluded.


*Confidentiality*
This communication (including any attachment/s) is intended only for the 
use of the addressee(s) and contains information that is PRIVILEGED AND 
CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or 
copying of this communication is prohibited. Please inform originator if 
you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any attachments, may not be free of 
viruses, trojans, similar or new contaminants/malware, interceptions or 
interference, and may not be compatible with your systems. You shall 
carry out virus/malware scanning on your own before opening any 
attachment to this e-mail. The sender of this e-mail and Company 
including its sister concerns shall not be liable for any damage that 
may incur to you as a result of viruses, incompleteness of this message, 
a delay in receipt of this message or any other computer problems.


___
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

Re: [OpenSIPS-Users] RTPEngine - changing codec format parameters from default values when transcoding - OpenSIPS 3.1

[Răzvan Crainea]

Hi, Mark!

OpenSIPS passes the commands to RTPengine as you supply them, so in 
theory this should be supported. Did you try to set this up? Can you 
provide any logs about this?


Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 9/14/21 14:01, Mark Allen wrote:

Hi all,

I'm using RTPEngine for transcoding between Opus and PCMU. According to 
the RTPEngine documentation (https://github.com/sipwise/rtpengine 
), it can accept formatting 
parameters for CODECs that support them. For instance, Opus allows you 
to change the maxaveragebitrate. However, in the OpenSIPS documentation 
for the RTPEngine module, it only seems to show support for the default 
options when transcoding - e.g."transcode-opus". Is there a way in 
OpenSIPS to tell RTPEngine to use values other than the defaults?


___
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

[OpenSIPS-Users] RTPEngine - changing codec format parameters from default values when transcoding - OpenSIPS 3.1

[Mark Allen]

Hi all,

I'm using RTPEngine for transcoding between Opus and PCMU. According to the
RTPEngine documentation (https://github.com/sipwise/rtpengine), it can
accept formatting parameters for CODECs that support them. For instance,
Opus allows you to change the maxaveragebitrate. However, in the OpenSIPS
documentation for the RTPEngine module, it only seems to show support for
the default options when transcoding - e.g."transcode-opus". Is there a way
in OpenSIPS to tell RTPEngine to use values other than the defaults?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users