Hi Jon, and All
While I was thinking through this approach, one question popped up in my
thought.
Since we run on a full load most of the hours, even if we limit the number
of calls to the faulty destination, it is very much possible that call
drain can happen as the faulty destination errors
Chris, it is not about removing lines from the script. It is about not
executing those lines when they are inappropriate.
i.e. "for any SIP requests or SIP responses coming from MS Teams"
Mark, there are several gotchas that I know of with Teams, but I cannot
guess which might apply in your case
i dont see how you can handle moh and attended transfer with opensips only.
On Mon, Jul 27, 2020, 11:31 Chris Johnson wrote:
> We were only able to remove one of the fix_nated_contact lines before it
> broke more than it did fix.
>
>
>
> We’re currently seeking support from Opensips directly
We were only able to remove one of the fix_nated_contact lines before it broke
more than it did fix.
We're currently seeking support from Opensips directly to get it all working
correctly.
From: Mark Miranda
Sent: 24 July 2020 21:21
To: john.qu...@smartvox.co.uk; OpenSIPS users mailling list
Thanks everyone for your valuable feedback.
I think we can send the branches to be delayed back to opensips and in this
way, it would be a new call in opensips so we can easily handle it with
extra configs.
Anyways, we changed the business logic a bit(send to phones only if
registered) and were
Any pointer?
I am using mongo for other modules and don't want to keep separate
database(mysql) for this module only
Ryan.
On Sun, 19 Jul 2020 at 15:32, ryan embgrets wrote:
> Greeting,
>
> I am just wondering if someone has been using mongodb for the user
> blacklist module or even if it is
Hi, Johan!
Unfortunately we are not using those features in proto_smpp, and it is
very hard for me to create a testing environment for something that I
don't fully understand how it works. That's why those issues have been
put back.
Nevertheless, they shouldn't be closed - this seems like a
Hi,
a few months ago, volga629 and myself added bugs and a feature request for
proto_smpp.
Now, after 30 days these issues are closed.
Is there any chance that these can be picked up ?
wkr,
___
Users mailing list
Users@lists.opensips.org
thanks Razvan,
btw, I will be starting on push notifications also.
Op ma 27 jul. 2020 om 09:32 schreef Răzvan Crainea :
> Hi, Johan!
>
> We haven't got a chance to tune OpenSIPS CP for 3.1, although we need to
> do this ASAP.
> Nevertheless, there were no major changes between 3.0 and 3.1,
Hi, Johan!
We haven't got a chance to tune OpenSIPS CP for 3.1, although we need to
do this ASAP.
Nevertheless, there were no major changes between 3.0 and 3.1, therefore
you should be able to use 3.1.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
Hi, Sasmita!
You should only check the `$avp(trl)` value if `dp_translate` succeeeds.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 7/22/20 11:51 AM, Sasmita Panda wrote:
Hi All ,
in opensips 1.11 I was using dp_translate function as below and its
Hi, John!
According to your snippet, you're logging the attributes when do_routing
fails - well, if do_routing fails, it means that id didn't find any
rule, gateway or carrier that is able to handle the call, therefore it
is normal that all of them are NULL.
Best regards,
Răzvan Crainea
Hi, Mark!
Unfortunately the drouting module does not export any statistics. You
can however use the statistics module[1] and define your own statistics,
that you have to manually update them from the script according to your
needs.
[1] https://opensips.org/docs/modules/3.1.x/statistics.html
Hi, James!
Please compile your sources with memory debugging [1] (QM_MALLOC) to
gather more information.
[1] https://www.opensips.org/Documentation/TroubleShooting-OutOfMem
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 7/16/20 8:30 PM, James via
14 matches
Mail list logo
