The EVENT header then provides the reason (reg, for
registration) the registration was changed.
EVENT: reg
Expires The EXPIRES header is used for multiple purposes. It allows the sender to
express when an event (such as a user??™s registration) is to expire. For example, when
the EXPIRES header is sent within a REGISTER message, the EXPIRES value indicates
when the registration is to expire. The user must then register again prior to the
EXPIRES value.
The use of this header varies upon its implementation. It is flexible in that it can be
used to express any expiration (not just registration) based on the method or request it
is contained within. The value is expressed in decimal as seconds.
EXPIRES: 3
From The FROM header identifies the initiator of a request. There are a number of
ways it can be expressed, including a display name or the URI. The URI can be a TEL
URI as well. This field is primarily for user consumption and is not used by the network
for routing. For example, a device could use this information for name display. However,
care should be taken when using this header, as it can easily be compromised.
When the URI is being presented along with the name display, the URI is contained
within brackets, and the name display is contained within quotations.
FROM: "Travis Russell"
In-Reply-To This header is used for applications where calls that previously were unanswered
are returned.
Pages:
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171