Scribd
Upload
73 views

Understanding SIP Registration

SIP registration associates a user's address of record (AOR) with one or more device locations by including a contact header with the IP address. Registrations are time-based and must be periodically refreshed by sending a new REGISTER with the same headers. The SIP registrar can challenge the registration with a nonce for authentication, and the client responds with a second REGISTER containing an encrypted authorization header with the password. Registration allows devices to securely associate a user with an IP address to enable communication through a SIP registrar.

Uploaded by

SK_shivam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
73 views

Understanding SIP Registration

SIP registration associates a user's address of record (AOR) with one or more device locations by including a contact header with the IP address. Registrations are time-based and must be periodically refreshed by sending a new REGISTER with the same headers. The SIP registrar can challenge the registration with a nonce for authentication, and the client responds with a second REGISTER containing an encrypted authorization header with the password. Registration allows devices to securely associate a user with an IP address to enable communication through a SIP registrar.

Uploaded by

SK_shivam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

UNDERSTANDING SIP REGISTRATION

May 29, 2014 · by Andrew Prokop · in SIP · 79 Comments


Let’s start at the very beginning

a very good place to start

when you read you begin with A B C

when you sing you begin with Do Re Mi

I have always loved musicals and Rogers and Hammerstein’s “The Sound of Music” is high on my list of
favorites. Sure, it’s corny and far from historically accurate, but that doesn’t bother me in the least. I am
always willing to set aside any sense of reality for good singing, romance, and adventure and “The Sound
of Music” has them all.

So, what does this have to do with unified communications? REGISTER, of course. Like Do Re Me, you
begin SIP with REGISTER.

Can you get SIP devices to communicate without REGISTER? Absolutely. In fact, when I teach my SIP
class, the students put their SIP clients into point-to-point mode which does not require REGISTER. This
means that clients send SIP requests and responses directly to the other clients and not through a proxy.
The clients can do everything all by themselves.

However, point-to-point without REGISTER has a serious downfall. The clients are required to know the
IP addresses of all the other clients they wish to communicate with. While this is fine in a limited
classroom environment, it becomes unwieldy after you grow beyond a handful of endpoints.

As an analogy, imagine having to know the IP address of everyone you wanted to send an email to.   That’s
the same problem you have if you don’t use REGISTER. It’s simply not practical.

The Tie that Binds

REGISTER associates a user’s identification, or Address of Record (AOR), with one or more locations.
Note that I said locations. You are not limited to registering an AOR to a single device. Personally, I
routinely register my AOR to a physical desk phone and multiple SIP soft-clients. Present day Avaya Aura
supports up to ten such registrations per user. That’s enough to make even the most device crazy nerd
happy.

You bind an AOR to an IP address with a Contact header.  For example, one of my soft clients might tell
a SIP registrar that aprokop can be reached at 192.168.0.14 with this Contact header.

Contact: Andrew Prokop <SIP:[email protected]>


Registrations are time-based and will eventually expire. This requires the client to periodically refresh a
REGISTER with a new REGISTER. Actually, new isn’t the correct word to use for this. Subsequent
REGISTER messages must contain the same Contact, To, From, call-ID, and From tag  as the
original registration. This allows the SIP registrar to know that it’s simply a refresh and not a new
registration for the same AOR.

Please note that CSeq will increment with each REGISTER sent.

To learn more about registration timers, please see my article, Understanding SIP Timers Part II.

Keeping Things Secure

I may tell my communications system that I am Andrew Prokop, but it would be foolish to trust me at face
value. That’s why SIP allows a REGISTER to be challenged as to the authenticity of the user.

Before I go through a REGISTER challenge, allow me to define something known as a nonce.

Nonce stands for Number Once and is an arbitrary number used only once in a cryptographic
communication. The recipient of a nonce will use it to encrypt his or her credentials. Number once refers
to the fact that encryption with this nonce can only be done one time. If someone were to sniff the LAN
and obtain someone’s encrypted password, it won’t do them any good because it can only be used in a
single transaction. It becomes stale and useless immediately after its first use.

A REGISTER flow is fairly simple and follows these steps:

1. A user sends a REGISTER to the SIP registrar. The To and From headers contain the user’s

AOR. The user specifies the number of seconds the registration should be valid in

the Expires header. This value can be later raised or lowered by the registrar.

2. The registrar returns a 401 Unauthorized response with a WWW-Authenticate header.  This

header contains data that must be used to encrypt the user’s communications password.

Specifically, it contains a nonce along with the name of the encryption algorithm that the client

must use.
3. The user sends a second REGISTER to the SIP registrar. This REGISTER contains

an Authorization header.   Within Authorization is the user’s encrypted password.

4. If the correct password is received by the registrar, a 200 Ok response is sent to signify a

successful registration. An Expires header may be present with a different value than what the

user requested.  This is the time the registration will be valid as determined by the registrar’s

policies.

A registration is removed by sending a REGISTER with an Expires header value of 0 (zero).

In a picture, we have this.

Using the traceSM tool on an Avaya Aura Session Manager, I captured the following trace which shows a
REGISTER, the challenge, and a REGISTER with encrypted credentials.  Take a look at the headers and
you will see that they are doing exactly what I said they would do.
In the case of my daily life, my various SIP devices will each send a REGISTER, be challenged, and resend
the REGISTER with the encrypted credentials. They periodically refresh their registrations to ensure that
I am able to make and receive calls on all my devices until I am finished for the day.

Speaking of finished for the day, that’s about all I have to say about REGISTER.  It’s not that complicated
once you understand the basics.  Just keep in mind that while registration isn’t absolutely mandatory, it
enables a secure, scalable, and easy to manage SIP solution.

And these are a few of my favorite things.

You might also like