2024-01-02: Site is back on track, self-hosted on a rpi because you get the Internet you fund.
2025-02-06: Oh well, some power grid issues caused the rpi to reboot, I really should configure uwsgi to restart automatically --'

00000000-0000-1000-8000-000a95a0e128
Seen in rfc5626

Seen in rfc5626

Seen in RFC 5626
Counts : rfc5626:2
Seen 2 times in more than 1 page, showing only the first.
RFC 5626          Client-Initiated Connections in SIP       October 2009


   sequences (CRLF), while for transports that are not connection
   oriented, this is accomplished by using a SIP-specific usage profile
   of STUN (Session Traversal Utilities for NAT) [RFC5389].

3.2.  Single Registrar and UA

   In the topology shown below, a single server is acting as both a
   registrar and proxy.

      +-----------+
      | Registrar |
      | Proxy     |
      +-----+-----+
            |
            |
       +----+--+
       | User  |
       | Agent |
       +-------+

   User Agents that form only a single flow continue to register
   normally but include the instance-id as described in Section 4.1.
   The UA also includes a "reg-id" Contact header field parameter that
   is used to allow the registrar to detect and avoid keeping invalid
   contacts when a UA reboots or reconnects after its old connection has
   failed for some reason.

   For clarity, here is an example.  Bob's UA creates a new TCP flow to
   the registrar and sends the following REGISTER request.

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 192.0.2.2;branch=z9hG4bK-bad0ce-11-1036
   Max-Forwards: 70
   From: Bob <sip:bob@example.com>;tag=d879h76
   To: Bob <sip:bob@example.com>
   Call-ID: 8921348ju72je840.204
   CSeq: 1 REGISTER
   Supported: path, outbound
   Contact: <sip:line1@192.0.2.2;transport=tcp>; reg-id=1;
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000A95A0E128>"
   Content-Length: 0

   The registrar challenges this registration to authenticate Bob.  When
   the registrar adds an entry for this contact under the AOR for Bob,
   the registrar also keeps track of the connection over which it
   received this registration.





Jennings, et al.            Standards Track                     [Page 7]
-1 RFC regex push