Hello,
Using kamailio 5.1, I am trying to use sip_trace() from a
branch route to send a copy of the current sip message to another location.
Sending the message works fine but I note that the message being sent is the
original incoming request and does not contain what was changed for the
I have one Kamailio that makes an outbound register on two Asterisk.
I have a dispatcher with that same two Asterisk destinations, on INVITE
message I call replace_from("", ) in order
to call a internal extension and on failure route I receive 401 and call
the process of authorization is OK.
The
So the strange thing is that I use kamcmd to get the list of users and that
works. Are there special permissions needed to delete them?
On Wed, Mar 10, 2021 at 4:38 AM Ilie Soltanici wrote:
> Hello,
>
> Sorry, there is actually no need for the callid argument, I mixed it up
> with another
Hi!
But there would be a connection after app will wake up.
Wake up -> REGISTER -> Connection.
And after this it's about a time to send to app any info on canceled or
already answered calls.
Regards,
Igor
On 10.03.2021 18:18, Jurijs Ivolga wrote:
Hi,
If you look into this:
Hi,
If you look into this:
https://developer.apple.com/documentation/pushkit/responding_to_voip_notifications_from_pushkit
Full quote:
After sending the initial push notification, don’t send additional push
> notifications to cancel the call or communicate new details to your app.
> Instead,
Hi,
But Apple prohibits to use 2nd push for call cancel. That's not my decision.
https://developer.apple.com/documentation/pushkit/responding_to_voip_notifications_from_pushkit
After sending the initial push notification, don’t send additional
push notifications to cancel the call or
Hi,
My point is that you're referring to documentation where it is assumed that
there is always connection between iOS app and Kamailio, but this might not
be the case, like in the scenario that I described.
I think somebody who put this documentation is not really aware of all use
cases and for
Hi!
That is exactly my question. Now I have workaround for this
(https://samael28.blogspot.com/2021/03/kamailio-and-delayed-cancel-on-ios.html)
but maybe there is more efficient way, like "storing" dead transactions.
Regards,
Igor
On 10.03.2021 15:07, Jurijs Ivolga wrote:
Hi,
So if there
Hi,
So if there is no connection between iOS app and Kamailio, what should we
do? Lets imagine scenario: call arrives, app receives push notifications
and then call is cancelled, even before connection is established.
Jurijs
On Wed, Mar 10, 2021 at 4:04 PM Igor Olhovskiy
wrote:
> Hello,
>
>
Hello,
As I got, this is should be supported by app itself, not iOS.
And Apple docs says explicitly:
After sending the initial push notification, don’t send additional
push notifications to cancel the call or communicate new details to
your app. Instead, communicate with the app directly
Hello,
On Cancel we are sending just another Push Notification that indicates the
call is cancelled, and the calling screen dissapear.
Regards,
On Wed 10 Mar 2021 at 12:28, Igor Olhovskiy wrote:
> Hello!
>
> Is there any way to "store" already finished transactions in tsilo? Idea
> is to
Hello!
Is there any way to "store" already finished transactions in tsilo? Idea
is to deliver, for example, canceled calls to the phone, when call
already was answered on other device, but push notification arrive
later? Major problem here, that there how it's working on iOS.
On iOS phone
Hello,
Sorry, there is actually no need for the callid argument, I mixed it up
with another command.
As Daniel recommended try to check the permissions. Which user the script
is running with and what are the permission for /var/run/kamailio/
Regards,
On Wed, 10 Mar 2021 at 09:26, Ilie Soltanici
Hello,
kamcmd dlg.end_dlg $h_entry $h_id
>
I think you are missing the callid parameter when calling kamcmd command:
Try kamcmd dlg.end_dlg $h_entry $h_id $SIPCallID
Regards,
On Tue, 9 Mar 2021 at 13:03, Andrew Chen wrote:
> Thanks guys.
> Here is the whole function I created:
>
> function
14 matches
Mail list logo
