Enquiry about push notifications

Daisuke Ushijima <[email protected]> Tue, 30 Dec 2025 13:58:20 +0800
Newsgroups gmane.comp.voip.linphone.user
Message-ID <CAL_Z0s=XM6bzN76BPVcP2QLvM9YDBEeba5rHjWxjoGdtde5DKg@mail.gmail.com>
--===============4469499294092334298==
Content-Type: multipart/alternative; boundary="0000000000009a4aad0647250c24"

--0000000000009a4aad0647250c24
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Linphone / Belledonne Communications team,

I=E2=80=99m planning to run my own SIP infrastructure (Flexisip) and would =
like to
support reliable push notifications on iOS/Android while continuing to use
the official Linphone mobile apps.

Could you please advise whether you offer a paid SaaS / service that
enables push notifications for third-party SIP accounts (i.e., accounts
registered to our own Flexisip server) on the official Linphone iOS/Android
apps?

In particular, I would appreciate clarification on:

1) Availability / Scope
- Do you provide a push notification SaaS that works with the official
Linphone iOS/Android apps for third-party SIP accounts (our own Flexisip)?

2) Service architecture
- If available, which model applies?
(a) Belledonne operates a hosted =E2=80=9Cpush service=E2=80=9D that relays=
 notifications
for our users, or
(b) We configure our Flexisip to connect to your service / gateway, or
another integration approach
- Any required configuration details or prerequisites would be helpful
(high-level is fine).

3) Commercial terms
- Pricing model (per user, per device, per MAU, etc.)
- Minimum number of users / minimum monthly commitment
- SLA / support scope and response times

4) Technical requirements
- Required server components and minimum specs (we currently plan to use a
small VPS initially)
- Required ports / TLS requirements, certificates, etc.
- Supported client versions (Linphone iOS/Android: which versions are
supported, and any limitations)

5) If the above is not possible
- If push notifications for third-party SIP accounts on the official
Linphone apps are not supported via SaaS, could you provide an estimate for
a white-label / branded mobile app (iOS/Android) including ongoing
maintenance/support?

If you need more context about our use case or architecture, I=E2=80=99m ha=
ppy to
share details.

Thank you in advance, and I look forward to your guidance.

Best regards,
Daisuke Ushijima
Kookai PTE LTD
Singapore

--0000000000009a4aad0647250c24
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div style=3D"font-size:inherit" dir=3D"auto">Hello Linphone / Belledonne C=
ommunications team,<br style=3D"font-size:inherit"><br style=3D"font-size:i=
nherit">I=E2=80=99m planning to run my own SIP infrastructure (Flexisip) an=
d would like to support reliable push notifications on iOS/Android while co=
ntinuing to use the official Linphone mobile apps.<br style=3D"font-size:in=
herit"><br style=3D"font-size:inherit">Could you please advise whether you =
offer a paid SaaS / service that enables push notifications for third-party=
 SIP accounts (i.e., accounts registered to our own Flexisip server) on the=
 official Linphone iOS/Android apps?<br style=3D"font-size:inherit"><br sty=
le=3D"font-size:inherit">In particular, I would appreciate clarification on=
:<br style=3D"font-size:inherit"><br style=3D"font-size:inherit">1) Availab=
ility / Scope<br style=3D"font-size:inherit">- Do you provide a push notifi=
cation SaaS that works with the official Linphone iOS/Android apps for thir=
d-party SIP accounts (our own Flexisip)?<br style=3D"font-size:inherit"><br=
 style=3D"font-size:inherit">2) Service architecture<br style=3D"font-size:=
inherit">- If available, which model applies?<br style=3D"font-size:inherit=
">  (a) Belledonne operates a hosted =E2=80=9Cpush service=E2=80=9D that re=
lays notifications for our users, or  <br style=3D"font-size:inherit">  (b)=
 We configure our Flexisip to connect to your service / gateway, or another=
 integration approach  <br style=3D"font-size:inherit">- Any required confi=
guration details or prerequisites would be helpful (high-level is fine).<br=
 style=3D"font-size:inherit"><br style=3D"font-size:inherit">3) Commercial =
terms<br style=3D"font-size:inherit">- Pricing model (per user, per device,=
 per MAU, etc.)<br style=3D"font-size:inherit">- Minimum number of users / =
minimum monthly commitment<br style=3D"font-size:inherit">- SLA / support s=
cope and response times<br style=3D"font-size:inherit"><br style=3D"font-si=
ze:inherit">4) Technical requirements<br style=3D"font-size:inherit">- Requ=
ired server components and minimum specs (we currently plan to use a small =
VPS initially)<br style=3D"font-size:inherit">- Required ports / TLS requir=
ements, certificates, etc.<br style=3D"font-size:inherit">- Supported clien=
t versions (Linphone iOS/Android: which versions are supported, and any lim=
itations)<br style=3D"font-size:inherit"><br style=3D"font-size:inherit">5)=
 If the above is not possible<br style=3D"font-size:inherit">- If push noti=
fications for third-party SIP accounts on the official Linphone apps are no=
t supported via SaaS, could you provide an estimate for a white-label / bra=
nded mobile app (iOS/Android) including ongoing maintenance/support?<br sty=
le=3D"font-size:inherit"><br style=3D"font-size:inherit">If you need more c=
ontext about our use case or architecture, I=E2=80=99m happy to share detai=
ls.<br style=3D"font-size:inherit"><br style=3D"font-size:inherit">Thank yo=
u in advance, and I look forward to your guidance.<br style=3D"font-size:in=
herit"><br style=3D"font-size:inherit">Best regards,<br style=3D"font-size:=
inherit">Daisuke Ushijima<br style=3D"font-size:inherit">Kookai PTE LTD<br =
style=3D"font-size:inherit">Singapore</div>

--0000000000009a4aad0647250c24--


--===============4469499294092334298==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTGlucGhvbmUt
dXNlcnMgbWFpbGluZyBsaXN0CkxpbnBob25lLXVzZXJzQG5vbmdudS5vcmcKaHR0cHM6Ly9saXN0
cy5ub25nbnUub3JnL21haWxtYW4vbGlzdGluZm8vbGlucGhvbmUtdXNlcnMK

--===============4469499294092334298==--