TABLE 7.11 DIAMETER AVPs (continued)
190 Chapter 7
There are several AVPs that are not yet defined by the RFCs. This is still work in
progress at the time this book went to print. If there is no definition given for an AVP,
and no code assigned in Table 7.11, the committee is still working on fully defining the
AVP and its use. They will be defined in future revisions of this book.
Acct-Application-ID This parameter is found in the Vendor-specific-application-ID
message; it contains the value of 1. This AVP is only used in offline charging within the
IMS domain.
Amount-of-UUS-data The amount of user-to-user data is identified in this AVP. The
value identifies the number of octets worth of data carried in the message body of a
SIP message. This could then be used by the operator to charge based on data size (the
amount of user data received/sent).
Application-provided-called-party-address The called party number in the form of
a SIP URI or E.164 number is provided in this AVP if the application server is able to
determine what the called party number is. This information can be useful in determining
if the called number was different than the number being routed to (for example,
the called number was a subscriber??™s work number, but the session was redirected to
the subscriber??™s home number).
Application-server This AVP provides the URL of the application server that is used
for the identified session.
Pages:
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374