Hi, Michael!
You can't (and shouldn't, at least not in an easy way) respond to
re-INVITE from a proxy - your best chance is to route the re-INVITE down
to the endpoint - he is the one that should respond.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
The Customer is unable to keep calls open past 15 minutes.
If the duration of the call was a multiple of 15 minutes, please make
sure that you can properly respond to the keep-alive RE-INVITE that
the carrier sends every 15 minutes.
How do I make sure that Opensips responds to any REINVITES?
Hi, Pat!
Then create a logic to detect whether the call should be sent to
dispatcher and call that route only for those calls, and call lookup for
the others.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 2/2/23 16:19, Pat M via Users wrote:
Hi
Hi Razvan
When i put it there then it does not allow calls between the uac - uac again
and tries to send all calls to the dispatcher :(
Sent with Proton Mail secure email.
--- Original Message ---
On Thursday, February 2nd, 2023 at 12:35 PM, Răzvan Crainea
wrote:
> Yes, that's
Yes, that's one valid option.
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 2/2/23 13:33, Pat M via Users wrote:
Hi Razvan,
Do you mean here?
route[relay] {
# for INVITEs enable some additional helper routes
if (is_method("INVITE")) {
Hi Razvan,
Do you mean here?
route[relay] {
# for INVITEs enable some additional helper routes
if (is_method("INVITE")) {
t_on_branch("per_branch_ops");
t_on_reply("handle_nat");
t_on_failure("missed_call");
route(DISPATCH_OUT);
}
Sent with Proton Mail secure email.
---
Hi, Pat!
What do you mean by "internal calls fail"? If you don't want to route
calls between extensions, I would expect the DISPATCH_OUT to be called
in the main route, rather on branch route.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 2/1/23
Are you using the default systemd script in OpenSIPS[1].
[1]
https://github.com/OpenSIPS/opensips/blob/master/packaging/redhat_fedora/opensips.service
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 1/18/23 13:40, Stefan Tobé wrote:
Hi,
I have an
rabbitmq_publish currently only runs in blocking mode, you cannot make
async requests with it. Unless the command is async at the protocol
level, i.e. you are not waiting for the response.
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 1/17/23
I am pretty sure you don't actually need a re-INVITE here, but rather an
actual INVITE to Asterisk. Check out how push notifications should be
handled in OpenSIPS:
https://blog.opensips.org/tag/push-notification/
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
Not sure how t_suspend works, but if you're trying to run a script and
fetch the output, then continue processing, you can use the exec async
functions[1].
[1] https://opensips.org/docs/modules/3.3.x/exec.html#afunc_exec
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
Hello!
Does it stop to any TLS operation, even for new ones? What TLS lib are
you using, openssl or wolfssl?
Are there any errors in the logs related to TLS?
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 12/30/22 16:00, L S wrote:
One more thing:
Make sure you fix the WSS client's contact using fix_nated_contact();
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 1/19/23 20:27, nutxase via Users wrote:
Hi guys
So i notice when i register a WSS client to opensips the contact shows
something
13 matches
Mail list logo
