Enter the user, host, port and transport. The tool validates each part, percent-encodes unsafe characters and shows the finished URI.
A SIP URI has the general form sip:user:password@host:port;uri-parameters?headers. In practice you use the scheme, the user, the host, sometimes a port and sometimes a transport parameter. Passwords in URIs are discouraged by RFC 3261 and this tool never includes them.
sip or sips. sips requires TLS on every hop.user=phone parameter in formal contexts.udp, tcp or tls. Omit it to let the client choose per RFC 3263.sip:1002@pbx.example.com
sip:+15550100@sip.provider.example;transport=tcp
sips:alice@secure.example.com
sip:bob@[2001:db8::10]:5080A SIP URI identifies a user or service on a SIP network, in the form sip:user@host:port;parameters. It is defined in RFC 3261 section 19.1. The user part is often an extension number; the host is the domain or IP address of the server.
sips: means every hop must use TLS. Use it when your server supports it and you want that guarantee. Many servers instead accept sip: with transport=tls, which encrypts the first hop only. RFC 5630 discusses the trade-offs.
The user part allows a limited set of characters unescaped. Anything else must be percent-encoded so servers parse the URI correctly. Spaces, #, and non-ASCII letters are common examples.
No. SIPdia takes the server, username and password as separate fields and builds the URI itself. This tool helps when you write dial strings, PBX configuration or documentation by hand.