12 CCR Triggers
DIAMETER Message SIP Trigger
CCR [initial] SIP INVITE
SIP NOTIFY
SIP MESSAGE
SIP REGISTER
SIP SUBSCRIBE
SIP REFER
SIP PUBLISH
CCR [update] SIP 200 OK (acknowledging INVITE, or UPDATE)
CCR [terminate] SIP BYE
SIP 200 OK (acknowledging non-session SIP methods)
SIP CANCEL
SIP 2xx (except 200 OK)
SIP 3xx, 4xx, 5xx, 6xx
CCR [event] SIP NOTIFY
SIP MESSAGE
SIP REGISTER
SIP REFER
SIP PUBLISH
SIP 4xx, 5xx, 6xx
TABLE 7.13 ACR Triggers
DIAMETER Message SIP/ISUP Trigger
ACR [start] SIP 200 OK (acknowledging receipt of an initial INVITE)
ISUP ANM
ACR [interim] SIP 200 OK (acknowledging receipt of a subsequent INVITE or UPDATE)
Expiration of AVP
ACR [stop] SIP BYE
ISUP REL
ACR [event] SIP 200 OK (acknowledging NOTIFY, MESSAGE, REGISTER, SUBSCRIBE, or
PUBLISH)
SIP 202 ACCEPTED (acknowledging REFER)
SIP 2xx (not 200 OK)
SIP 3xx, 4xx, 5xx, 6xx Final Response
SIP CANCEL
200 Chapter 7
Charging Data Correlation When multiple network entities are involved with the same
session, there will be multiple CDRs from all of these different elements. The SIP protocol
is used to correlate all of the CDRs received from the various entities. Specifically,
the IMS Charging Identifier (ICID) parameter is sent in a P-CHARGING-VECTOR
header from the origination to the termination point and included in all CDRs for the
same session.
The ICID is created by the first IMS entity to receive a request.
Pages:
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388