Date: Fri, 29 Mar 2024 05:40:22 +0100 (CET) Message-ID: <1085975146.3524.1711687222033@teamwork> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3523_299661801.1711687222032" ------=_Part_3523_299661801.1711687222032 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Valid for: |
N610 |
N670 |
N870 |
N870E |
Embedded Integrator |
Virtual Integrator |
We sometimes get the question if it is possible to limit the simultaneou= s SIP Registrations after a reboot of the system. There are platforms that = do not like up to 250 SIP Registrations at the same time and could put the = N870 on a blacklist.
For this, the first SIP REGISTRATION behavior can be changed via auto-pr= ovisioning.
Provisioning example
<?xml version=3D"1.=
0" encoding=3D"UTF-8"?>
<provisioning version=
span>=3D"1.1" productID=3D"e2"&=
gt;
<nvm>
<= !-- WithDeregOnHsNotReachable means that the SIP REGISTRATION starts when t= he handset is connected via DECT, after reboot it depends on the base and h= andset when this happens. It is random !!! -->
<= ;param name=3D"SipProvider.0.Wi= thDeregOnHsNotReachable" value= =3D"1"/>
<= !-- FirstRegEarlyRefresh is default on 5 seconds. This parameter takes care= that .. seconds after the first SIP REGISTER a new SIP REGISTER is started= . This is developed for Large systems with multiple DECT managers where som= e platforms require a second delayed SIP REGISTER after .. time. "0" means = disabled and no second SIP REGISTER is done after .. seconds. -->=
<= ;param name=3D"SipProvider.0.Fi= rstRegEarlyRefresh" value=3D"0"= />
</nvm>
</provisioning>