Verification of SIP OPTIONS and REGISTER Support for Keep-Alive / Re-Registration

[kyk]

I’m writing to confirm whether your SIP trunk service supports the **SIP OPTIONS** and **SIP REGISTER** methods for endpoint keep-alive and registration maintenance.

My only available internet connection is an **unstable wired broadband link**—it suffers frequent packet-loss and jitter, and I have no way to upgrade or replace it—so dependable SIP keep-alive mechanisms are essential.

* **SIP OPTIONS** (RFC 3261, §11) lets a client probe server reachability and capabilities.
* **SIP REGISTER** (RFC 3261, §10) binds a user’s SIP URI to its current IP address and keeps inbound calling functional.
* Diagnostic tools such as **sipsak** can send these requests—for example

```bash
sipsak -U -s sip:[email protected]
```

to verify server behaviour as explained at

https://voipnuggets.com/2023/09/24/sips ... sting-tool "Sipsak: Effective SIP Diagnostics and Testing tool - AI and VoIP Blog"
https://manpages.ubuntu.com/manpages/ja ... sak.1.html "sipsak - a utility for various tests on sip servers and user agents"

Could you please confirm:

1. Whether your platform accepts **SIP OPTIONS** requests so that I can monitor registration status.
2. Whether it accepts repeat **SIP REGISTER** requests (beyond the initial registration) for manual or automated re-registration.
3. Any specific headers, parameters, or interval recommendations your implementation requires.

Knowing this will let me build a reliable monitoring solution that power-cycles my equipment **only** if registration truly drops.

[kyk]

айпишнЕги Ы?

[Mad Hatter]

Ты не умничай, а пальцем покажи.