linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Linphone-developers Digest, Vol 239, Issue 7


From: Ihor Olkhovskyi
Subject: Re: [Linphone-developers] Linphone-developers Digest, Vol 239, Issue 7
Date: Fri, 13 Jan 2023 11:47:49 +0100

Flavio,

Maybe a bit stupid question, but when app is active (foreground) you do usually have a corresponding usrloc entry after last REGISTER.
Also, on a network state change Linphone sends another REGISTER to indicate this. Also it can send reINVITE's on network change. Or we're talking on some intermediate network changes, that are not known to device?

Cheers,|
Ihor

Le jeu. 12 janv. 2023 à 20:10, Flavio Goncalves <flavio@voffice.com.br> a écrit :
The problem is a bit different. When the phone is NOT in foreground everything works.  The problem occurs in Foreground because the phone does not send a REGISTER when receiving a PUSH notification in this state. So if the phone is in Foreground, it does not receive the call because I do not send an INVITE unless I receive a REGISTER (where I can get the updated address and port). Also for sequential requests such as RE-INVITE and BYE they may eventually fail because the NAT mapping is closed after some time. The RFC specifies the pn-purr for this purpose, but I'm not sure if Linphone supports it.

Cheers, 
Flavio E. Goncalves




Em qui., 12 de jan. de 2023 às 14:03, <linphone-developers-request@nongnu.org> escreveu:
Send Linphone-developers mailing list submissions to
        linphone-developers@nongnu.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.nongnu.org/mailman/listinfo/linphone-developers
or, via email, send a message with subject or body 'help' to
        linphone-developers-request@nongnu.org

You can reach the person managing the list at
        linphone-developers-owner@nongnu.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linphone-developers digest..."


Today's Topics:

   1. PUSH Notification on IOS and support for RFC8599
      (Flavio Goncalves)
   2. Re: PUSH Notification on IOS and support for RFC8599
      (Igor Olhovskiy)


----------------------------------------------------------------------

Message: 1
Date: Thu, 12 Jan 2023 08:52:38 -0300
From: Flavio Goncalves <flavio@voffice.com.br>
To: linphone-developers@nongnu.org
Subject: [Linphone-developers] PUSH Notification on IOS and support
        for RFC8599
Message-ID:
        <CAJkFROyhT9M2KWSgBhJpguHWV2Txt3y=_yU3tnY-fCbnOtWVvg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

In the last weeks I have been testing the support of Linphone and OpenSIPS
to the RFC8599. I have managed to make everything work except for the calls
in Foreground.

The process of the RFC8599 is to send a push and wait for the REGISTER
before sending a new INVITE (this is necessary because the address or port
could have been changed).

However, when the phone is in foreground (IOS) after receiving the PUSH
notification it does not send the REGISTER, because it was not awake.

Another issue I have to workaround, is to handle three registrations after
a PUSH. One I got to suppress by changing the setting of the repeat call
notification to off. Because of the two REGISTERs, two INVITEs are
generated and a 486 busy comes from the phone. I had to drop one of them in
the proxy to make it work, but it is a horrible patch (the REGISTERs came
with different call-ids).

My questions are:

Is it possible to send a REGISTER after a PUSH even in the foreground?
Is it possible to send only one REGISTER after the PUSH rather than two? I
have pcaps and logs
of all the tests.

Best regards,

Flavio E. Goncalves
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nongnu.org/archive/html/linphone-developers/attachments/20230112/9c1223e5/attachment.htm>

------------------------------

Message: 2
Date: Thu, 12 Jan 2023 17:15:45 +0100
From: Igor Olhovskiy <igorolhovskiy@gmail.com>
To: linphone-developers@nongnu.org
Subject: Re: [Linphone-developers] PUSH Notification on IOS and
        support for RFC8599
Message-ID:
        <CAJTkRNuDHQrAg7jRZZ4F7NsTj-rx5_-2+21Nh6x9Dzcuohq3aQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Flavio,

Actually, we've faced something similar that you are describing, correct me
if I'm wrong, it's about CallKit showing dial screen and even after sending
REGISTER by app, the app might not receive an INVITE, cause call is ended
already.

We've overcome it with
https://blog.provoip.org/2021/03/kamailio-and-delayed-cancel-on-ios.html
(On Kamailiio, but I don't think it's critical here).

Not sure if it's what you're looking for, but it's the way we got it
correctly working.

Cheers,
Ihor

Le jeu. 12 janv. 2023 à 17:00, Flavio Goncalves <flavio@voffice.com.br> a
écrit :

> Hi,
>
> In the last weeks I have been testing the support of Linphone and OpenSIPS
> to the RFC8599. I have managed to make everything work except for the calls
> in Foreground.
>
> The process of the RFC8599 is to send a push and wait for the REGISTER
> before sending a new INVITE (this is necessary because the address or port
> could have been changed).
>
> However, when the phone is in foreground (IOS) after receiving the PUSH
> notification it does not send the REGISTER, because it was not awake.
>
> Another issue I have to workaround, is to handle three registrations after
> a PUSH. One I got to suppress by changing the setting of the repeat call
> notification to off. Because of the two REGISTERs, two INVITEs are
> generated and a 486 busy comes from the phone. I had to drop one of them in
> the proxy to make it work, but it is a horrible patch (the REGISTERs came
> with different call-ids).
>
> My questions are:
>
> Is it possible to send a REGISTER after a PUSH even in the foreground?
> Is it possible to send only one REGISTER after the PUSH rather than two? I
> have pcaps and logs
> of all the tests.
>
> Best regards,
>
> Flavio E. Goncalves
>
>
> _______________________________________________
> Linphone-developers mailing list
> Linphone-developers@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/linphone-developers
>


--
Best regards,
Ihor (Igor)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nongnu.org/archive/html/linphone-developers/attachments/20230112/df9e6bc4/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Linphone-developers mailing list
Linphone-developers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-developers


------------------------------

End of Linphone-developers Digest, Vol 239, Issue 7
***************************************************
_______________________________________________
Linphone-developers mailing list
Linphone-developers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/linphone-developers


--
Best regards,
Ihor (Igor)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]