I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n

ITU-T Q.3610
TELECOMMUNICATION (05/2009)
STANDARDIZATION SECTOR
OF ITU

SERIES Q: SWITCHING AND SIGNALLING

Signalling requirements and protocols for the NGN –
Service and session control protocols – supplementary
services

Signalling requirements and protocol profiles

for customized ring-back tone service

Recommendation ITU-T Q.3610

 ITU-T Q-SERIES RECOMMENDATIONS
SWITCHING AND SIGNALLING

SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1–Q.3

INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4–Q.59
FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60–Q.99
CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100–Q.119
SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120–Q.499
DIGITAL EXCHANGES Q.500–Q.599
INTERWORKING OF SIGNALLING SYSTEMS Q.600–Q.699
SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700–Q.799
Q3 INTERFACE Q.800–Q.849
DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850–Q.999
PUBLIC LAND MOBILE NETWORK Q.1000–Q.1099
INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100–Q.1199
INTELLIGENT NETWORK Q.1200–Q.1699
SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700–Q.1799
SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL Q.1900–Q.1999
CONTROL (BICC)
BROADBAND ISDN Q.2000–Q.2999
SIGNALLING REQUIREMENTS AND PROTOCOLS FOR THE NGN Q.3000–Q.3999
General Q.3000–Q.3029
Network signalling and control functional architecture Q.3030–Q.3099
Network data organization within the NGN Q.3100–Q.3129
Bearer control signalling Q.3130–Q.3179
Signalling and control requirements and protocols to support attachment in NGN environments Q.3200–Q.3249
Resource control protocols Q.3300–Q.3369
Service and session control protocols Q.3400–Q.3499
Service and session control protocols – supplementary services Q.3600–Q.3649
NGN applications Q.3700–Q.3849
Testing for NGN networks Q.3900–Q.3999

For further details, please refer to the list of ITU-T Recommendations.

Recommendation ITU-T Q.3610

Signalling requirements and protocol profiles for customized

ring-back tone service

Summary
Recommendation ITU-T Q.3610 specifies the signalling requirements and protocol profiles for NGN
customized ring-back tone (CRBT) service in support of customized multimedia ringing (CMR).

Source
Recommendation ITU-T Q.3610 was approved on 7 May 2009 by ITU-T Study Group 11
(2009-2012) under Recommendation ITU-T A.8 procedures.

Keywords
CRBT, IMS, NGN, SDP, SIP.

Rec. ITU-T Q.3610 (05/2009) i

 FOREWORD
The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of
telecommunications, information and communication technologies (ICTs). The ITU Telecommunication
Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical,
operating and tariff questions and issuing Recommendations on them with a view to standardizing
telecommunications on a worldwide basis.
The World Telecommunication Standardization Assembly (WTSA), which meets every four years,
establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on
these topics.
The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
In some areas of information technology which fall within ITU-T's purview, the necessary standards are
prepared on a collaborative basis with ISO and IEC.

NOTE
In this Recommendation, the expression "Administration" is used for conciseness to indicate both a
telecommunication administration and a recognized operating agency.
Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain
mandatory provisions (to ensure e.g., interoperability or applicability) and compliance with the
Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some
other obligatory language such as "must" and the negative equivalents are used to express requirements. The
use of such words does not suggest that compliance with the Recommendation is required of any party.

INTELLECTUAL PROPERTY RIGHTS

ITU draws attention to the possibility that the practice or implementation of this Recommendation may
involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence,
validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others
outside of the Recommendation development process.
As of the date of approval of this Recommendation, ITU had not received notice of intellectual property,
protected by patents, which may be required to implement this Recommendation. However, implementers
are cautioned that this may not represent the latest information and are therefore strongly urged to consult the
TSB patent database at http://www.itu.int/ITU-T/ipr/.

© ITU 2010
All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the
prior written permission of ITU.

ii Rec. ITU-T Q.3610 (05/2009)

 CONTENTS
Page
1 Scope ............................................................................................................................ 1
2 References..................................................................................................................... 1
3 Definitions .................................................................................................................... 2
3.1 Terms defined elsewhere................................................................................ 2
3.2 Terms defined in this Recommendation......................................................... 2
4 Abbreviations and acronyms ........................................................................................ 2
5 CRBT service and architecture..................................................................................... 4
5.1 General description......................................................................................... 4
5.2 General architecture........................................................................................ 4
5.3 Possible CRBT service architectures.............................................................. 5
6 Service models.............................................................................................................. 7
7 Media formats............................................................................................................... 7
7.1 Audio .............................................................................................................. 7
7.2 Video .............................................................................................................. 7
7.3 Text................................................................................................................. 7
7.4 Still image....................................................................................................... 7
8 Signalling requirements ................................................................................................ 7
8.1 Requirements for the originating UE ............................................................. 8
8.2 Requirements for the originating P-CSC-FE.................................................. 8
8.3 Requirements for the I-CSC-FE ..................................................................... 9
8.4 Requirements for the S-CSC-FE .................................................................... 9
8.5 Requirements for the IBC-FE......................................................................... 9
8.6 Requirements for the AMG-FE ...................................................................... 9
8.7 Requirements for the call server..................................................................... 9
8.8 Requirements for the AS-FE .......................................................................... 9
8.9 Requirements for the MRC-FE ...................................................................... 11
8.10 Requirements for the terminating P-CSC-FE................................................. 11
8.11 Requirements for the terminating UE............................................................. 11
9 Protocol profiles............................................................................................................ 11
9.1 IMS-based CRBT service............................................................................... 12
9.2 Call server-based CRBT service .................................................................... 14
10 Interactions between networks ..................................................................................... 15
10.1 Providing circuit-switched network CRBT to the originating UE in the
IMS domain .................................................................................................... 15
10.2 Providing IMS CRBT to the originating UE in circuit switched network ..... 16
11 Interactions with other services on NGN...................................................................... 17
11.1 Originating identification presentation (OIP)................................................. 17
11.2 Originating identification restriction (OIR).................................................... 17

Rec. ITU-T Q.3610 (05/2009) iii

 Page
11.3 Terminating identification presentation (TIP)................................................ 17
11.4 Terminating identification restriction (TIR)................................................... 17
11.5 Communication HOLD (HOLD) ................................................................... 17
11.6 Communication DIVersion (CDIV) services ................................................. 17
11.7 Explicit communication transfer (ECT) service............................................. 18
11.8 Originating CRBT service interacting with terminating CRBT service ........ 18
11.9 Terminating early media services to calling party other than CRBT ............. 18
12 Security considerations................................................................................................. 19
Annex A – Multi-dialog model................................................................................................ 20
A.1 General description......................................................................................... 20
A.2 Signalling requirements.................................................................................. 20
Appendix I – Signalling flows ................................................................................................. 21
I.1 IMS-based CRBT service by gateway model with PRACK and UPDATE
(Originating IMS-UE case) ............................................................................ 21
I.2 IMS-based CRBT service by gateway model with re-INVITE
(Originating IMS-UE case) ............................................................................ 25
I.3 CRBT service by application server model.................................................... 31
I.4 CRBT service by HTTP model (Originating IMS-UE case).......................... 35
I.5 CRBT service by gateway model (Originating PSTN/ISDN interworking
case)................................................................................................................ 37
I.6 CRBT service by gateway model (Originating POTS-UE case).................... 40
I.7 Call server-based CRBT service by gateway model (Originating IMS-UE
case)................................................................................................................ 42
I.8 Originating CRBT service interacts with terminating CRBT service by
AS model ........................................................................................................ 45
I.9 Providing circuit switched network CRBT to the originating UE in IMS
domain ............................................................................................................ 52
I.10 Providing IMS CRBT to the originating UE in circuit switched network
domain ............................................................................................................ 58
Bibliography ............................................................................................................................ 63

iv Rec. ITU-T Q.3610 (05/2009)

Recommendation ITU-T Q.3610

Signalling requirements and protocol profiles for customized

ring-back tone service

1 Scope
This Recommendation specifies signalling requirements and protocol profiles of customized
ring-back tone (CRBT) service in support of customized multimedia ringing (CMR). This
Recommendation also contains signalling flows.
The CRBT service is defined in next generation networks (NGNs) including IP multimedia
subsystems (IMS) and call-server based networks.
This Recommendation covers the protocol profiles over the user-network interface (UNI) and
network-to-network interface (NNI) based on [ITU-T Q.3402] and [ITU-T Q.3401], respectively. In
addition, it also covers [ITU-T H.248.1] based protocol profile for the interface between the access
media gateway functional entity (AMG-FE) and the service control functions. More detailed
protocol profiles for other interfaces may be subject to future specifications.

2 References
The following ITU-T Recommendations and other references contain provisions which, through
reference in this text, constitute provisions of this Recommendation. At the time of publication, the
editions indicated were valid. All Recommendations and other references are subject to revision;
users of this Recommendation are therefore encouraged to investigate the possibility of applying the
most recent edition of the Recommendations and other references listed below. A list of the
currently valid ITU-T Recommendations is regularly published. The reference to a document within
this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
[ITU-T H.248.1] Recommendation ITU-T H.248.1 (2005), Gateway control protocol:
Version 3.
[ITU-T Q.3401] Recommendation ITU-T Q.3401 (2007), NGN NNI signalling profile
(Protocol Set 1); Amendment 1 (2008).
[ITU-T Q.3402] Recommendation ITU-T Q.3402 (2008), NGN UNI signalling profile
(Protocol Set 1).
[ITU-T T.81] Recommendation ITU-T T.81 (1992) | ISO/IEC 10918-1:1994,
Information technology – Digital compression and coding of
continuous-tone still images: Requirements and guidelines.
[ITU-T Y.2012] Recommendation ITU-T Y.2012 (2006), Functional requirements
and architecture of the NGN release 1.
[ITU-T Y.2701] Recommendation ITU-T Y.2701 (2007), Security requirements for
NGN release 1.
[IETF RFC 2616] IETF RFC 2616 (1999), Hypertext Transfer Protocol – HTTP/1.1.
[IETF RFC 3261] IETF RFC 3261 (2002), SIP: Session Initiation Protocol.
[IETF RFC 3262] IETF RFC 3262 (2002), Reliability of Provisional Responses in the
Session Initiation Protocol (SIP).
[IETF RFC 3311] IETF RFC 3311 (2002), The Session Initiation Protocol (SIP)
UPDATE Method.

Rec. ITU-T Q.3610 (05/2009) 1

[IETF RFC 3372] IETF RFC 3372 (2002), Session Initiation Protocol for Telephones
(SIP-T): Context and Architectures.
[IETF RFC 3959] IETF RFC 3959 (2004), The Early Session Disposition Type for the
Session Initiation Protocol (SIP).
[IETF RFC 3960] IETF RFC 3960 (2004), Early Media and Ringing Tone Generation
in the Session Initiation Protocol (SIP).
[IETF RFC 4566] IETF RFC 4566 (2006), SDP: Session Description Protocol.
[IETF RFC 5009] IETF RFC 5009 (2007), Private Header (P-Header) Extension to the
Session Initiation Protocol (SIP) for Authorization of Early Media.

3 Definitions

3.1 Terms defined elsewhere

This Recommendation uses the following term defined elsewhere:
3.1.1 early media [IETF RFC 3959]: The media (e.g., audio and video) that is exchanged before
a particular session is accepted by the called user.

3.2 Terms defined in this Recommendation

This Recommendation defines the following terms:
3.2.1 calling CRBT service subscriber: The calling party who subscribes to the CRBT service.
3.2.2 called CRBT service subscriber: The called party who subscribes to the called party
configured CRBT service.
3.2.3 CRBT service user: The calling party who experiences the CRBT service.
3.2.4 early media for CRBT: The early media that is delivered to the calling party with the
media contents configured by the service subscriber. It can be generated by the originating network
or the terminating network, depending on the location of service subscriptions.
3.2.5 icon ring tone server (IRT server): Icon ring tone (IRT) server stores the ringing tone
media such as audio, video and picture files. The IRT server behaves as a web server and can be
provided by content providers or operators. A user terminal can interact with the IRT server via, for
example, HTTP to download the ringing tone media.

4 Abbreviations and acronyms

This Recommendation uses the following abbreviations and acronyms:
ACM Address Complete Message
AGC-FE Access Gateway Control Functional Entity
AMG-FE Access Media Gateway Functional Entity
ANM Answer Message
AS Application Server
AS-FE Application Support Functional Entity
AVP Audio Video Profile
B2BUA Back-to-Back User Agent
BGC-FE Breakout Gateway Control Functional Entity

2 Rec. ITU-T Q.3610 (05/2009)

CDIV Communication DIVersion
CFNR Call Forwarding on No Reply
CRBT Customized Ring-Back Tone
CRBT-O Customized Ring-Back Tone by Originating network
CRBT-T Customized Ring-Back Tone by Terminating network
CSN Circuit Switched Network
ECT Explicit Communication Transfer
EUF End-User Functions
GSM Global System for Mobile communications
HOLD Communication HOLD
HTTP HyperText Transfer Protocol
IAM Initial Address Message
IBC-FE Interconnection Border Gateway Control Functional Entity
I-CSC-FE Interrogating Call Session Control Functional Entity
IMS IP Multimedia Subsystem
IRT Icon Ring Tone
ISDN Integrated Services Digital Network
ISUP ISDN User Part
MGCF Media Gateway Control Function
MGC-FE Media Gateway Control Functional Entity
MRC-FE Media Resource Control Functional Entity
MRFC Media Resource Function Controller
MRP-FE Media Resource Processing Functional Entity
MSC Mobile Switching Centre
NGN Next Generation Network
NNI Network-to-Network Interface
OIP Originating Identification Presentation
OIR Originating Identification Restriction
P-CSC-FE Proxy Call Session Control Functional Entity
POTS Plain Old Telephone Service
PSTN Public Switched Telephone Network
RTCP RTP Control Protocol
RTP Real-Time Transport Protocol
SCF Service Control Functions
S-CSC-FE Serving Call Session Control Functional Entity
SDP Session Description Protocol
SG-FE Signalling Gateway Functional Entity

Rec. ITU-T Q.3610 (05/2009) 3

SIP Session Initiation Protocol
SIP UA SIP User Agent
SUP-FE Service User Profile Functional Entity
TIP Terminating Identification Presentation
TIR Terminating Identification Restriction
TMG-FE Trunk Media Gateway Functional Entity
UAC User Agent Client
UAS User Agent Server
UDP User Datagram Protocol
UE User Equipment
UE-A User Equipment for user A
UE-B User Equipment for user B
UNI User-to-Network Interface
URL Uniform Resource Locator
UUI User-to-User Information

5 CRBT service and architecture

5.1 General description

Customized ring-back tone (CRBT) service provides the calling party with the called/calling party's
customized ring-back tone. The service is based on subscription and can be subscribed by the
called party or the calling party. The service is invoked to provide customized ring-back tone to the
calling party, according to the service configuration. The CRBT contents can be image, audio,
video, text or a combination of all.

5.2 General architecture

The CRBT service is defined and provided in the NGN architecture, which is either IMS-based or
call-server based. Figure 5-1 shows a general architecture that is compliant to [ITU-T Y.2012] for
providing the CRBT service based on IMS, and/or call-server networks.

4 Rec. ITU-T Q.3610 (05/2009)

 Originating network Terminating network
service stratum service stratum
ASF/SSF ASF/SSF

CRBT service CRBT service

Legacy terminal
SCF
Call Server SCF Call Server
component component

IMS terminal H.248.1 IMS IMS

component component

Originating Transport Transport stratum

AMG-FE
End User Function stratum

NGN UNI NGN NNI

Figure 5-1 – CRBT service functional architecture

5.3 Possible CRBT service architectures

Terminating IMS-based and call-server based architectures for CRBT services are shown in
Figures 5-2 and 5-3, respectively. The originating IMS-based and call-server based architectures for
CRBT services are shown in Figures 5-4 and 5-5, respectively. These figures show general
scenarios assuming that the originating network is different from the terminating network.
Although functional architectures are different for IMS- and call-server based networks, the service
control mechanisms are identical.

Originating network Terminating network

CRBT service

AS-FE
SUP-FE

CRBT service user I-CSC-FE S-CSC-FE MRC-FE

Originating
End User Function P-CSC-FE MRP-FE
Service stratum
NGN terminal Service stratum
(*)
Legacy terminal
Transport stratum Transport stratum

(*) If the originating network is call-server based, the legacy terminal is accommodated.

Figure 5-2 – Terminating IMS-based CRBT service architecture

Rec. ITU-T Q.3610 (05/2009) 5

 Originating network Terminating network

CRBT service

AS-FE
SUP-FE

CRBT service user IBC-FE Call Server MRC-FE

Originating
End User Function MRP-FE
Service stratum
NGN terminal Service stratum
(*)
Legacy terminal
Transport stratum Transport stratum

(*) If the originating network is call-server based, the legacy terminal is accommodated.

Figure 5-3 – Terminating call-server based CRBT service architecture

Originating network Terminating network

CRBT service

AS-FE SUP-FE

CRBT service user

MRC-FE S-CSC-FE I-CSC-FE
Originating
End User Function
MRP-FE P-CSC-FE
NGN terminal Service stratum
Service stratum
Legacy terminal
AMG-FE Transport stratum Transport stratum

Figure 5-4 – Originating IMS-based CRBT service architecture

Originating network Terminating network

CRBT service

AS-FE SUP-FE

CRBT service user

Call Server IBC-FE
Originating MRC-FE
End User Function
MRP-FE
Service stratum Service stratum

Legacy terminal
AMG-FE Transport stratum Transport stratum

Figure 5-5 – Originating call-server based CRBT service architecture

6 Rec. ITU-T Q.3610 (05/2009)

6 Service models
There are three models for ring-back tone generations. The CRBT service is provided based on at
least one of these service models, and can be provided with more than one model.
– Gateway model is to establish early media sessions in the same way as regular sessions,
using offer/answer exchanges. The gateway model consists of managing early media
sessions using offer/answer exchanges in reliable provisional exchanges, PRACKs, and
UPDATEs [IETF RFC 3960]. In case of non-reliable provisional exchanges, re-INVITE
can be used.
– Application server model is to establish early media by distinguishing early sessions from
regular sessions by using the early-session option tag. By indicating support of the
early-session disposition type in the user agent client (UAC), the user agent server (UAS)
knows that offer/answer exchanges for early media (early-session disposition type) are kept
separate from regular media (session disposition type) [IETF RFC 3960].
– HTTP model is to provide the web URL of the subscriber's repository for the CRBT
contents to be presented during early session. This information is filled by and delivered
from the CRBT service system, within the response bearing a 18x code, responding to the
initial INVITE.

7 Media formats
In order to guarantee a certain level of early media support and compatibility between the calling
and called party terminals, appropriate media formats shall be negotiated or selected to play the
CRBT contents.

7.1 Audio
If audio is supported, the codec list shall be as specified in clause 8.1 of [ITU-T Q.3401] and
[ITU-T Q.3402].

7.2 Video
If video is supported, the codec list shall be as specified in clause 8.1 of [ITU-T Q.3401] and
[ITU-T Q.3402].

7.3 Text
If plain text is supported, any character encoding (charset) that contains a subset of the logical
characters (e.g., Unicode [b-Unicode]) can be used.

7.4 Still image

If still image is supported, JPEG encoding in compliance with [ITU-T T.81] shall be supported. In
addition, the interchange format described in [b-JFIF] may be used with JPEG. Other encoding
formats (e.g., GIF ([b-GIF87a], and [b-GIF89a]), or PNG [b-IETF RFC 2083]) may be supported.

8 Signalling requirements
The following clauses describe the signalling requirements for providing CRBT services in each
functional entity.

Rec. ITU-T Q.3610 (05/2009) 7

8.1 Requirements for the originating UE
8.1.1 Requirements for supporting CRBT on gateway model
If the originating user equipment (UE) wishes to receive early media authorization indication, it
should add the P-Early-Media header, which has value of "supported" to the initial INVITE request
as described in [IETF RFC 5009].
The originating UE does not need to distinguish early media and regular media before and after a
final answer is received, so there is no requirement for the originating UE when the called user
answers the communication.
8.1.2 Requirements for supporting CRBT on application server model
If the originating UE wishes to receive early media authorization descriptions, as described in
[IETF RFC 3959], it shall set the "early-session" option tag in the supported header field to the
initial INVITE request.
If the originating UE wishes to exchange reliable provisional responses, it shall set the "100rel"
option tag in the supported header field to the initial INVITE request as defined in [IETF
RFC 3262].
If the originating UE uses different media port and/or connection address for regular media and
early media, when regular media is received, or a final answer is received on the dialog, the
originating UE should stop playing early media.
8.1.3 Requirements for supporting CRBT on HTTP model
The originating UE shall support Alert-Info and/or Call-Info header field as specified in [IETF
RFC 3261].
If the media file indicated in the Alert-Info and/or Call-Info header field has been downloaded, the
originating UE shall play the downloaded information to override the local ring-back information,
except if the user denies or stops it.
The originating UE should stop playing the downloaded information, except when the local policy
determines to keep playing the CRBT contents, when a final answer is received on the dialog.
8.1.4 Requirements for supporting multiple CRBT service models
When multiple service models are applied, the originating UE may be configured to determine
whether to play downloaded information and/or early media information, if different media types
are involved, and if the same media type is involved, then the preference is set by the local policy.

8.2 Requirements for the originating P-CSC-FE

8.2.1 Requirements for supporting CRBT on gateway model
The P-CSC-FE may add, remove, or modify the P-Early-Media header field within the forwarded
SIP requests and responses, according to the procedures in [IETF RFC 5009].
8.2.2 Requirements for supporting CRBT on application server model
The P-CSC-FE may add, remove, or modify, the early-session SDP within the forwarded SIP
requests and responses, according to the procedures in [IETF RFC 3959].
8.2.3 Requirements for supporting CRBT on HTTP model
The P-CSC-FE may have local policy to remove, or modify the Alert-Info, and/or Call-Info header
field.

8 Rec. ITU-T Q.3610 (05/2009)

8.3 Requirements for the I-CSC-FE
CRBT has no impact on this FE.

8.4 Requirements for the S-CSC-FE

CRBT has no impact on this FE.

8.5 Requirements for the IBC-FE

8.5.1 Requirements for supporting CRBT on gateway model
The IBC-FE may add, remove, or modify, the P-Early-Media header field within the forwarded SIP
requests and responses, according to the operator's policy.
8.5.2 Requirements for supporting CRBT on application server model
The IBC-FE may add, remove, or modify, the early-session SDP within the forwarded SIP requests
and responses, according to the operator's policy.
8.5.3 Requirements for supporting CRBT on HTTP model
The IBC-FE may have local policy to remove, or modify the Alert-Info, and/or Call-Info header
field.

8.6 Requirements for the AMG-FE

CRBT has no impact on this FE.

8.7 Requirements for the call server

CRBT has no impact on this FE.

8.8 Requirements for the AS-FE

The requirements in this clause are for invocation and operation to the CRBT service. The
activation, deactivation, and configuration of the CRBT service are out of scope of this
Recommendation.
The AS-FE provides CRBT service regardless of whether the network is call-server based or
IMS-based.
8.8.1 Requirements for providing CRBT service on gateway model
After receiving an initial INVITE request with an SDP offer from the originating UE or receiving
an 18x response to the initial INVITE request from the terminating UE, the AS-FE shall:
a) Acquire SDP for CRBT from MRC-FE;
NOTE – The SDP for CRBT can be acquired by sending an INVITE request without SDP to
MRC-FE.
b) Send SDP answer for CRBT via a response bearing a 18x code to the initial INVITE
request with "100rel" option tag in the Require header.
The AS-FE may set all the media's bandwidth in SDP towards the terminating side to 0, in order to
avoid RTCP error.
For preconditions on the gateway model, when sending an SDP offer towards the terminating side
to establish communication with the media types expected by the originating user, the AS-FE may
add the missing media types, according to the media types received in the previous SDP answer
from the terminating side.

Rec. ITU-T Q.3610 (05/2009) 9

If a final answer is received by the AS-FE on a dialog, the CRBT managed by the AS-FE on the
dialog should be stopped.
Before forwarding the final answer, the AS-FE shall send the UPDATE request with the
terminating UE's SDP answer, then after updating the session description, the AS-FE shall send it
via a "200 OK" response without SDP towards the originating side.
8.8.2 Requirements for providing CRBT service by application server model
If the initial INVITE request with "early-session" option tag in the supported header, then,
according to [IETF RFC 3959], the AS-FE shall:
a) Acquire SDP for CRBT from MRC-FE;
NOTE – The SDP for CRBT can be acquired by sending an INVITE request without SDP to
MRC-FE.
b) Add a new message body that has an early-session disposition type in the provisional
response to contain the acquired SDP;
c) Set "early-session" option tag in the Require header field if it does not exist;
d) Set "100rel" option tag in the Require header field if it does not exist;
e) Send the provisional response towards the originating UE.
If a final answer is received by the AS-FE on a dialog, the CRBT managed by the AS-FE on the
dialog should be stopped.
8.8.3 Requirements for providing CRBT service by HTTP model
If an initial INVITE request has been received, then when the first provisional response bearing a
18x code to the INVITE request is received, according to [IETF RFC 3261], the CRBT AS-FE is
required to act as following:
a) If an iconic photo, photo explanation text, and/or card information need to be presented on
the originating UE's screen, the AS-FE should add a Call-Info header field, and, according
to [IETF RFC 3261], set the HTTP URL of the iconic photo file in the Call-Info header
field using "icon" value for the purpose parameter, set the photo explanation text in the
Call-Info header field using "info" value for the purpose parameter, and/or set the card
information in the Call-Info header field using "card" value for the purpose parameter;
b) If multimedia information need to be played on the originating UE, the AS-FE may add an
Alert-Info and/or Call-Info header field, and set the HTTP URL of the multimedia file to
the value of the Alert-Info/Call-Info header field;
c) If the INVITE request does not carry "early-session" option tag in the Supported header, the
AS-FE shall send the provisional response bearing a 18x code towards the originating UE;
d) Otherwise, proceed as described in clauses 8.8.1 and 8.8.2.
NOTE – It is recommended that the size of the multimedia file and photo file be small in order not
to delay communication establishment.
8.8.4 Requirements for supporting multiple models
It is the operator's policy (e.g., according to the subscriber's profile) to specify which model is
applied when the originating UE supports multiple models.
It is recommended for the operator policy to have a rule to apply the AS-model, if the
Supported/Required header field of the initial INVITE request has an early-session option tag and
the AS-FE supports the AS model.

10 Rec. ITU-T Q.3610 (05/2009)

In case the gateway model or the application server model is applied, the AS-FE should have the
policy to determine whether to play downloaded information and/or early media information, if
different media types are involved, and if the same media type is involved, then the preference is set
by the policy.
This policy should be configured by the calling CRBT service subscriber, the called CRBT service
subscriber, the originating network's operator and the terminating network's operator.
8.8.5 Requirements when providing interoperation from AS model to gateway model
If a provisional response bearing a 18x code with session SDP is received by the AS-FE on a
dialog, and neither the originating nor the terminating UE supports the application server model, the
AS-FE shall add early-session option tag in the Supported header field to the forwarded 18x
response.
If successive PRACK/UPDATE request with early-session SDP Offer is received, the AS-FE shall:
a) Generate session SDP Offer based on the early-session SDP Offer,
b) Remove the early-session SDP Offer, and
c) Add the session SDP Offer into the request, and forward the request.
The AS-FE may add more media type information in the session SDP Offer, which is in the original
session SDP Offer/Answer.
And if the "200 OK" response with session SDP Answer to the PRACK/UPDATE request is
received, the AS-FE shall:
a) Generate early-session SDP Answer based on the session SDP Answer,
b) Remove the session SDP Answer, and
c) Add the early-session SDP Answer into the response, and forward the response.

8.9 Requirements for the MRC-FE

CRBT impact on this FE is for further study.

8.10 Requirements for the terminating P-CSC-FE

CRBT has no impact on this FE.

8.11 Requirements for the terminating UE

CRBT has no impact on this FE.

9 Protocol profiles
The protocol profiles for CRBT services shall be based on the following ITU-T Recommendations.

Table 9-1 – Base Recommendations for CRBT protocol profiles

Profile Interval Protocol Recommendation
NGN UNI Between the originating end user function and the SIP/SDP [ITU-T Q.3402]
service control function in the originating
network
NGN NNI Between the service control functions of the SIP/SDP [ITU-T Q.3401]
originating and terminating networks
Gateway control Between the AMG-FE and service control H.248/SDP [ITU-T H.248.1]
protocol functions in the originating network

Rec. ITU-T Q.3610 (05/2009) 11

This clause provides CRBT service specific messages and headers, among the above
Recommendations and relevant IETF RFCs.
Other messages and headers that are not specific for CRBT may be supported as specified in the
base Recommendations in Table 9-1, if they are not explicitly specified in this Recommendation.

9.1 IMS-based CRBT service

9.1.1 Protocol profiles for gateway model
Initial INVITE shall include SDP. If early media session establishes with the reliable provisional
response, the 'PRACK' method shall be used as defined in [IETF RFC 3262].
If the early media connection is established by the exchanges of initial INVITE and non-reliable
provisional response, after finishing early media session, regular session can be made by media
re-negotiation exchanging second Offer SDP and Answer SDP after completion of the first
dialogue.
Unidirectional early media may also be supported by responding to initial INVITE with
non-reliable provisional response before sending actual media. Regular session is then established
by responding with a final SDP answer to the initial INVITE.
Table 9-2 illustrates the SIP messages that are specific to the CRBT service. Other SIP messages
may be supported, as specified in the base Recommendations in Table 9-1.

Table 9-2 – CRBT service specific methods and headers for gateway model

a) Early session establishment

Originating EUF Æ SCF/CRBT AS-FE
Early session Request
code Header code Description References
establishment Method
Reliable INVITE M Supported M Supported100rel
provisional Require O Require:100rel IETF RFC 3262
response-
based PRACK M RAck M
Non-Reliable
provisional
INVITE M – – – IETF RFC 3261
response-
based
SCF/CRBT AS-FE Æ Originating EUF
Early session
Response code Header code Description References
establishment
Reliable RSeq M
provisional
18x M IETF RFC 3262
response- Require M Require:100rel
based
Non-Reliable
provisional
18x M – – – IETF RFC 3261
response-
based

12 Rec. ITU-T Q.3610 (05/2009)

 b) Regular session establishment
Method/response code Header code Description Reference
UPDATE – 200 OK M – – – IETF RFC 3311
re-INVITE – 200 OK O – – – IETF RFC 3261

See clauses I.1 and I.2 for signalling flows and message usages.
If the CRBT service is provided to the legacy terminal with the IMS based PSTN/ISDN emulation
systems, the same H.248.1 profile, which is described in clause 9.2.1, shall be applied to the CRBT
services.
9.1.2 Protocol profiles for application server model
9.1.2.1 SIP profile
Initial INVITE shall include SDP. If early media session is established with the reliable provisional
response, the option tag "100rel" shall be supported and PRACK method shall be used as defined in
[IETF RFC 3262]. If early media session is provided, option tag "early-session" shall be supported,
the disposition type "early-session" shall be supported, and the content type "multipart/mixed" may
be supported, to specify distinctive session types (e.g., regular session and early session) within a
single message, as defined in [IETF RFC 3959].
Table 9-3 illustrates the SIP messages that are specific to the CRBT service. Other SIP messages
may be supported, as specified in the base Recommendations in Table 9-1.

Table 9-3 – CRBT service specific methods and headers for application server model
Originating EUF Æ SCF/CRBT AS-FE
Request
code Header code Description References
method
INVITE M Supported M Supported:100rel, early-session IETF RFC
Require O Require:100rel, early-session 3262
Content-Type O Content-Type: multipart/mixed
PRACK E RAck M –

SCF/CRBT AS-FE Æ Originating EUF

Response code Header code Description References
18x M RSeq O – IETF RFC
Require O Require:100rel, early-session 3262
IETF RFC
3959

See clause I.3 for signalling flows and message usages.

9.1.2.2 SDP profile
Different types of media such as audio, video, text and image can be utilized as different ring-back
tones and ringing tones. Each media type shall be specified in "m =" line (i.e., m = text, m = audio,
m = video).

Rec. ITU-T Q.3610 (05/2009) 13

9.1.3 Protocol profiles for HTTP model
If the CRBT URL information is delivered in provisional response, a response bearing a 18x code
shall include Call-Info header and 'purpose' parameters or/and Alert-Info header as defined in [IETF
RFC 3261].
Table 9-4 illustrates the SIP messages that are specific to the CRBT service.

Table 9-4 – CRBT service specific methods and headers for HTTP model
SCF/CRBT AS-FE ÆOriginating EUF
Method/response Code Header Code Description Reference
18x M Call-Info O purpose IETF RFC 3261
180 M Alert-Info O –

The calling party shall support HTTP/1.1 as defined in [IETF RFC 2616] in order to get CRBT
contents.
See clause I.4 for signalling flows and message usages.

9.2 Call server-based CRBT service

9.2.1 Protocol profiles for gateway model
The access media gateway control shall be supported based on [ITU-T H.248.1] and as described in
Table 9-5. The basic packages of Annex E of [ITU-T H.248.1] are applied to CRBT services. The
SIP profile described in clause 9.1.1 is applicable.

Table 9-5 – H.248.1 packages and SDP

H.248.1 packages SDP
Early and regular Annex E basic packages IETF RFC 4566
media session H.248.1 clause C.11

9.2.2 Protocol profiles for application server model

The call-server based CRBT service is provided by an AS-FE connected to and controlled by a
call-server. The AS-FE may support application server (AS) model regardless of whether the
session system is call-server or IMS-based. The call-server under the control of AS-FE may relay
SIP messages for service control to the originating network, or may map between the SIP and
H.248.1 and the service control for the plain old telephone service (POTS) terminal.
In the following cases, the AS model is not applicable:
a) The originating network provides call-server based CRBT.
b) The terminating network provides call-server based CRBT, and the originating network is
the call-server.
In the following case, the SIP and SDP profiles described in clause 9.1.2 are applicable:
a) The terminating network provides call-server based CRBT, and the originating network is
IMS.
9.2.3 Protocol profiles for HTTP model
It may be possible that the AMG-FE receives specific tone information from the AS-FE delivered
through the Ut1 interface [b-ITU-T Y.2031], but this usage is for further study.
Otherwise, this model is not applicable to POTS subscribers of the call-server.

14 Rec. ITU-T Q.3610 (05/2009)

The calling party shall support HTTP/1.1 as defined in [IETF RFC 2616] in order to get the CRBT
contents.

10 Interactions between networks

10.1 Providing circuit-switched network CRBT to the originating UE in the IMS domain
When the calling party in the IMS domain makes a session with the called party in the
circuit-switched network, the call request from the calling party first arrives at the MGC-FE. MGC-
FE is responsible for communicating with the called party in the circuit-switched network (CSN)
and holds an early media session negotiation with the calling party. If negotiation is successful, the
circuit-switched network plays CRBT to the calling party. When the called party answers the call,
PSTN stops playing CRBT and the MGC-FE connects the calling party.
The CRBT service is activated within circuit-switched networks such as PSTN or GSM, upon
receipt of one of the following messages:
a) Address complete message (ACM) with the value of the called party's status indicator
"subscriber free"; or
b) ACM with the value of the called party's status indicator "no indication", optionally, the
ACM also has "in-band information indicator" set to 1 (in-band info), or "ISDN User Part
indicator" set to 0 (ISDN User Part not used all the way);

MGC-FE
ACM
18x (Subscriber free/
(P-Early-Media/
No indication)
early-session)

CRBT media

c) CPG message, when:

– Event indicator is set to alerting; or
– Event indicator is set to "in-band information or an appropriate pattern is now
available"; or
– Event indicator is set to "Progress", optionally, the CPG also has "in-band information
indicator" set to 0 (in-band info), or "ISDN User Part indicator" set to 0 (ISDN User
Part not used all the way).

MGC-FE
CPG
18x (Alerting/
(P-Early-Media/ in-band information available)
early-session)

CRBT media

Rec. ITU-T Q.3610 (05/2009) 15

If the MGC-FE supports the P-Early-Media header as a network option, and
a) has received the P-Early-Media header in the INVITE request; and
b) has not already sent a provisional response including a P-Early-Media header with the
parameters indicating authorization of early media; and
c) preconditions are not used or applicable preconditions have been met,
then the gateway model is applied and the MGC-FE shall send a response bearing a 18x code with a
P-Early-Media header.
Or if the MGC-FE supports the early-session SDP as a network option, and
a) has received "early-session" option tag in the INVITE request; and
b) has not already sent a provisional response including an early-session SDP indicating
authorization of early media,
then the application server model is applied and the MGC-FE shall send a response bearing a 18x
code with early-session SDP.
The HTTP model is not applicable in this case.
See clause I.9 for the signal flow.

10.2 Providing IMS CRBT to the originating UE in circuit switched network

When the calling party in the circuit switched network makes a session with the called party in the
IMS-based network, the call request from the calling party arrives at MGC-FE. MGC-FE triggers
the CRBT service and is responsible for communicating with the CRBT AS-FE. If the UE in the
CSN is capable of video, the CRBT AS-FE decides to play the CRBT to the calling party, and if
CRBT SDP contains the video stream, the MGC-FE should ask the MSC to connect the calling
party, according to the message from the CRBT AS-FE and holds an early media session
negotiation with the calling party. If negotiation is successful, MRC/P-FE plays the CRBT to the
calling party. When the called party answers the call, MRC/P-FE stops playing the CRBT and
MGC-FE connects the calling party.
If the Address Complete Message (ACM) has not yet been sent, and either of the following
conditions are met, the MGC-FE shall send the Address Complete Message (ACM) with "in-band
information indicator" set to 1 (in-band info):
a) the reception of the first response bearing a 18x code that includes a P-Early-Media header
authorizing early media; and
b) SDP preconditions are not used, or applicable SDP preconditions have been met;
Or when the application server model is applied, and if the MGC-FE supporting the early-session
SDP as a network option; and
a) the reception of the first response bearing a 18x code that includes early-session SDP
authorizing early media.

MGC-FE 18x
(P-Early-Media/
ACM early-session)
in-band information available

CRBT media

16 Rec. ITU-T Q.3610 (05/2009)

If the Address Complete Message (ACM) has already been sent, at an MGC-FE and either of the
following conditions are met, the MGC-FE shall send Call Progress Message (CPG) that Event
indicator is set to "in-band information or an appropriate pattern is now available".
When the gateway model is applied, and if the MGC-FE supporting the P-Early-Media header as a
network option, and
a) the reception of a response bearing a 18x code that includes the first P-Early-Media header
authorizing early media,
Or when the application server model is applied, and if the MGC-FE supporting the early-session
SDP as a network option, and
a) the reception of a response bearing a 18x code that includes early-session SDP authorizing
early media.

MGC-FE 18x
CPG (P-Early- media/
(in-band information) early-session)

CRBT media

See clause I.10 for the signal flow.

The HTTP model is not applicable in this case.

11 Interactions with other services on NGN

11.1 Originating identification presentation (OIP)

No impact on the CRBT service.

11.2 Originating identification restriction (OIR)

No impact on the CRBT service.

11.3 Terminating identification presentation (TIP)

No impact on the CRBT service.

11.4 Terminating identification restriction (TIR)

If the CRBT service is associated with the terminator's id information, the terminating side CRBT
AS-FE shall not apply the service on the communication if TIR service has restriction rules on the
terminating identity information.

11.5 Communication HOLD (HOLD)

No impact on the CRBT service.

11.6 Communication DIVersion (CDIV) services

11.6.1 General
If the diverting party has both CRBT service and CDIV active, and the diverted-to party has CRBT
service active, then the CRBT service of the diverted-to party should be applied to the session by
the AS-FE providing the CRBT service of diverted-to party, except in the case of CFNR. The
interaction of CRBT service with call forwarding on no reply (CFNR) is described in clause 11.6.2.

Rec. ITU-T Q.3610 (05/2009) 17

If the diverting party has CRBT service and CDIV active, and the diverted-to party does not have an
active service, no CRBT service should be applied to the session when CDIV is invoked.
As a network operator option, the CRBT service of the diverting party may be applied to the session
by the AS-FE providing the CRBT service for the diverting party, without the CRBT service for the
diverted-to party applied to the session.
NOTE – The above network operator option can be deployed in cases where diversion of the call is hidden
from the calling party.
11.6.2 Call forwarding on no reply (CFNR)
If the diverting party has both CRBT service and CFNR active, and the diverted-to party has CRBT
service active, then the CRBT service of the diverting party should be applied to the session by the
AS-FE providing the CRBT service for the diverting party until the CFNR timer expires. Upon the
CFNR timer expiry, the AS providing the CRBT service for the diverting party should stop
applying the CRBT for the diverting user and the AS providing the CRBT service for the diverted-
to party should apply the CRBT service of the diverted-to party.
If the diverting party has CRBT service and CFNR active, and the diverted-to party does not have
an active service, the CRBT service of the diverting party should be applied to the session by the
AS providing the CRBT service for the diverting party until the CFNR timer expires.
As a network operator option, the CRBT service of the diverting party may be applied to the session
by the AS-FE providing the CRBT service for the diverting party, without the CRBT service for the
diverted-to party applied to the session.
NOTE – The above network operator option can be deployed in cases where diversion of the call is hidden
from the calling party.

11.7 Explicit communication transfer (ECT) service

If the transfer target has CRBT service active, the AS-FE providing the CRBT service shall apply
the transfer target's CRBT in the case of blind transfer. The AS-FE providing the CRBT service
shall not apply the transfer target's CRBT in the case of consultative transfer while the call is being
transferred to the transfer target.
The CRBT service of the transferor shall not be applied when ECT is invoked.

11.8 Originating CRBT service interacting with terminating CRBT service

If the originating CRBT service is triggered and the terminating CRBT service is also triggered, and
as both services provide early media to the calling party, a conflict occurs.
In this case, some priority mechanism as to which CRBT (the originating CRBT or the terminating
CRBT) should be played is required and the priority mechanism within SIP is for further study.
A no other mechanism is to configure the priority between service operators by pre-arrangement.
The configuration is set on the service profiles by the subscribers or the operators. In this case, since
the calling party is usually the subscriber of the originating CRBT, the originating CRBT has higher
priority over the terminating CRBT. The priority also can be configured in the terminal by an
individual subscriber.
The signal flow for priority service between the originating and the terminating CRBT is presented
in clause I.8.

11.9 Terminating early media services to calling party other than CRBT
If the originating CRBT and the terminating early media services toward the calling party such as
announcement, interactive voice response (IVR) or voice mail service (VMS) are invoked, and as
both services provide early media to the calling party, a conflict occurs.

18 Rec. ITU-T Q.3610 (05/2009)

When a terminating early media service to the calling party is an announcement providing network
or services information, or IVR services such as prepaid or VMS, the terminating early media
service is more important than the originating CRBT. In this case, the terminating early media
service has priority over the originating CRBT.
In order to control priority, the terminating early media service may send an indication to the
originating system that the terminating service will provide early media toward the calling party, in
order for the originating service to decide its service invocation or not.
A priority mechanism within SIP requires further study.
If the terminating CRBT and the terminating early media services toward the calling party are
invoked in parallel, the priority is set according to the service operator's policy.

12 Security considerations
The CRBT service is required to use the appropriate security mechanisms to meet the general
security requirements of NGN [ITU-T Y.2701].
Also, as the CRBT service provides early/regular media transport and signalling messages, the
NGN network infrastructure for CRBT service should ensure the confidentiality and integrity of the
signalling flows transported on it.
Therefore, it is recommended to provide the transport and/or network security (respectively,
e.g., TLS [b-IETF RFC 2246] and/or IPSec [b-IETF RFC 2401]) and/or the application security
(such as S/MIME [b-IETF RFC 2633]) for signalling messages using SIP between two endpoints,
as described in the security considerations of the core SIP specification [IETF RFC 3261], the Early
Media and Ringing Tone Generation specification [IETF RFC 3960], and Session Initiation
Protocol for Telephones (SIP-T [IETF RFC 3372]).
In the gateway model and the AS model, the transport and network security and/or the application
security should be applied.
In the HTTP model, the application-layer security should be applied, because the body of the
signalling message (e.g., Alert-info of SIP [IETF RFC 3261]) contains the web URL. Placing the
URL in the header field can pose a security risk. If a called party (UE-B) fetches the URLs provided
by a malicious caller (UE-A), the called party may be at risk for displaying inappropriate or
offensive content, dangerous or illegal content, and so on. Hence, the application security
(e.g., S/MIME) should be applied in order to provide the message authentication mechanism.

Rec. ITU-T Q.3610 (05/2009) 19

 Annex A

Multi-dialog model
(This annex forms an integral part of this Recommendation)

A.1 General description

The multi-dialog model establishes both early and regular dialog together during the establishment
of the communication. Since it uses a forking mechanism for making both dialogs, they are
correlated with the CRBT service.

A.2 Signalling requirements

A.2.1 Requirements for the originating UE
If the originating UE wishes to receive early media authorization indications, as described in
[IETF RFC 5009], it shall add the P-Early-Media header, which has the value of "supported" to the
initial INVITE request.
A.2.2 Requirements for the AS-FE
If the initial INVITE request with P-Early-Media header that has "supported" value, and without
"early-session" option tag in the Supported header, then, according to [IETF RFC 5009], the AS-FE
shall:
a) Acquire SDP for CRBT from MRFC;
NOTE 1– The SDP for the CRBT can be acquired by sending an INVITE request without SDP to
MRFC.
b) Create a new provisional response bearing a 18x code;
c) Set the To header tag value of the new provisional response bearing a 18x code different
from the To header tag value in the received provisional response bearing a 18x code;
d) Add a P-Early-Media header field in the new provisional response; the value of the
P-Early-Media header field has one of the following values: "sendonly", or "inactive";
e) Add a message body that has session disposition type in the new provisional response to
contain the acquired SDP;
f) Send the new provisional response bearing a 18x code and the received provisional
response bearing a 18x code towards the originating UE.
NOTE 2 – If the CRBT AS-FE wants to provide CRBT information with the new media type, the
CRBT AS-FE shall send out an UPDATE request.

20 Rec. ITU-T Q.3610 (05/2009)

 Appendix I

Signalling flows
(This appendix does not form an integral part of this Recommendation)

The detailed message examples are not shown for simplicity and most of the headers are shown in
the first message which includes the significant ones.

I.1 IMS-based CRBT service by gateway model with PRACK and UPDATE (Originating
IMS-UE case)
Figure I.1 signalling flow shows an IMS-based CRBT service provided by the gateway model
scenario with PRACK and UPDATE.

Originating Net. CRBT P-CSC-FE/

P/S/I-CSC-FE MRC/P-FE
UE-A AS-FE UE-B

S1:INVITE(offer A)
S2:INVITE(offer A)
S3:INVITE(offer A)
S4:180
S5:180
Connection &
Acquire CRBT sdp

S6:183 (CRBT answer)

S7: PRACK

Media control

CRBT play

Play CRBT with RTP

S8: 200 OK(PRACK)

Answer
S9: 200 OK(ans B)
S10:200 OK(ans B)
Disconnection

S11: UPDATE(offer B)

S12: 200 OK(ans A)

CRBT stop

S13: 200 OK

S14:ACK

S15: ACK

S16: ACK

Figure I.1 – IMS-based CRBT service by gateway model with PRACK and UPDATE

Rec. ITU-T Q.3610 (05/2009) 21

S1 INVITE (UE-A toward S-CSC-FE)
The INVITE request is sent from the UE-A to S-CSC-FE of the terminating side. The S-CSC-FE
evaluates the initial filter criteria and forwards the INVITE to the CRBT AS-FE. The contact value
includes UE-A's SIP URI that contains the IP address.

INVITE sip:ue-b@term_ngn.net SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID: ueacb03a0suea00234123
Cseq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>,<tel:+1-222-555-3333>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer,100rel
Accept: application/sdp
Session-Expires: 3600;refresh=uac
Content-Type: application/sdp
...

S3 INVITE (S-CSC-FE toward UE-B)

INVITE is sent toward the UE-B through network elements (AS-FE should be B2BUA server). The
contact value includes AS-FE's SIP URI.

INVITE sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=asfe171828
To: <tel:+1-222-333-4444>
Call-ID: asfed03a0sasfe0234123
Cseq:1 INVITE
Contact: <sip:192.100.100.100:5070>
Content-Type: application/sdp
...

S4-5 180 (UE-B toward AS-FE)

180 (ringing) is sent toward the AS-FE through network elements. The contact value includes
UE-B's SIP URI.

SIP/2.0 180 Ringing

From: <sip:ue-a@orig_ngn.net>;tag=asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>

22 Rec. ITU-T Q.3610 (05/2009)

S6 183 with SDP (AS-FE toward UE-A)
The AS-FE sends an 183 provisional response with the SDP of MRP-FE. The contact value
includes AS-FE's SIP URI.

SIP/2.0 183 Session Progress

From: <sip:ue-a@ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=asfe22222122
Call-ID : ueacb03a0suea00234123
Require:100rel
Contact: <sip:192.100.100.100:5070>
Content-Type: application/sdp
...

S7 PRACK (UE-A toward AS-FE)

The UE-A sends a PRACK request, which acknowledges the SIP 183 (Session Progress)
provisional response, to the AS-FE.

PRACK 192.100.100.100:5070 SIP/2.0

From: <sip:ue-a@ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=asfe22222122
Call-ID : ueacb03a0suea00234123
Cseq: 1 PRACK
Contact: <sip:192.100.200.51:5090>
...

S8 200 OK (AS-FE toward UE-A)

The AS-FE sends a 200 OK response to the PRACK request (7). The S-CSC-FE forwards the 200
OK response to the UE-A.

SIP/2.0 200 OK
From: <sip:ue-a@ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=asfe22222122
Call-ID : ueacb03a0suea00234123
Cseq: 1 PRACK
...

Rec. ITU-T Q.3610 (05/2009) 23

S9-10 200 OK (UE-B toward AS-FE)
When the called party answers, the UE-B sends a 200 OK (with SDP B) final response to the
INVITE request (3). The S-CSC-FE forwards the 200 OK response to the AS-FE.

SIP/2.0 200 OK
From: <sip:ue-a@ngn.net>;tag=asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
Cseq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
...

S11 UPDATE (AS-FE toward UE-A)

The AS-FE sends an UPDATE request containing the SDP received in the 200 OK (10) from the
UE-B.

UPDATE sip:192.100.200.51:5090 SIP/2.0

From: <tel:+1-222-333-4444>;tag=asfe22222122
To: <sip:ue-a@ngn.net>;tag=171828
Call-ID : ueacb03a0suea00234123
Cseq: 1 UPDATE
Contact: <sip:192.100.100.100:5070>
Content-Type: application/sdp
...

S12 200 OK (UE-A toward AS-FE)

The UE-A sends a 200 OK to the UPDATE request (11). The S-CSC-FE forwards the 200 OK
response to the AS-FE.

SIP/2.0 200 OK
From: <tel:+1-222-333-4444>;tag=asfe22222122
To: <sip:ue-a@ngn.net>;tag=171828
Call-ID : ueacb03a0suea00234123
Cseq: 1 UPDATE
Contact: <sip:192.100.200.51:5090>
Content-Type: application/sdp
...

24 Rec. ITU-T Q.3610 (05/2009)

S13 200 (OK) response to INVITE (AS-FE toward UE-A)
The AS-FE sends a 200 OK final response to the INVITE request (1). The S-CSC-FE forwards the
200 OK response to the UE-A.

SIP/2.0 200 OK
From: <sip:ue-a@ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=asfe22222122
Call-ID : ueacb03a0suea00234123
Contact: <sip:192.100.100.100:5070>
Cseq: 1 INVITE
...

S14 ACK (UE-A toward AS-FE)

The UE-A responds to the 200 OK (13) with an ACK request toward AS-FE.

ACK sip:192.100.100.100:5070 SIP/2.0

From: <sip:ue-a@ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=asfe22222122
Call-ID : ueacb03a0suea00234123
Cseq: 1 ACK
...

S15-16 ACK (AS-FE toward UE-B)

The AS-FE responds to the 200 OK (9) with an AC request toward the UE-B.

ACK sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@ngn.net>;tag=asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
Cseq: 1 ACK
...

I.2 IMS-based CRBT service by gateway model with re-INVITE (Originating IMS-UE
case)
Figure I.2 signalling flow shows an IMS-based CRBT service provided by the gateway model
scenario with non-reliable provisional response in the IMS-UE originating case:
NOTE – This signalling flow shows the case of regular session establishment with re-INVITE.

Rec. ITU-T Q.3610 (05/2009) 25

 Originating Net. CRBT P-CSC-FE/
P/S/I-CSC-FE MRC/P-FE
UE-A AS-FE UE-B

S1:INVITE(offer A)
S2:INVITE(offer A)
S3:INVITE(offer A)
S4:180
S5:180
Connection &
Acquire CRBT sdp
S8:183 (CRBT answer)
Media control
CRBT play
Play CRBT with RTP

Answer
S12:200OK(answer B)
S13:200OK(answer B)

Disconnection
S16:200OK (CRBT answer)
S17:ACK
S17:ACK
S17:ACK

S18:RE-INVITE(No SDP)
S19:200 OK (offer A)
S20:RE-INVITE(offer A)
CRBT stop
S21:RE-INVITE(offer A)
S22:200 OK (answer B)
S23:200 OK (answer B)
S24:ACK(answer B)
S25:ACK
S26:ACK

A-B with RTP

Figure I.2 – IMS-based CRBT service by gateway model with re-INVITE

26 Rec. ITU-T Q.3610 (05/2009)

The procedures of SIP signalling are as follows:
S1 INVITE (UE-A toward S-CSC-FE/AS-FE)
The INVITE request is sent from the UE-A to S-CSC-FE of the terminating side. The S-CSC-FE
evaluates the initial filter criteria and forwards the INVITE to the CRBT AS-FE. The contact value
includes UE-A's SIP URI that contains the IP address.

INVITE sip:ue-b@term_ngn.net SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>, <tel:+1-222-555-3333>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer
Accept: application/sdp
Session-Expires: 3600;refresher=uac
Content-Type: application/sdp
...

S2-3 INVITE (AS-FE/S-CSC-FE toward UE-B)

INVITE is sent toward the UE-B through network elements (AS-FE should be B2BUA server). The
contact value includes AS-FE's SIP URI.

INVITE sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=asfe171828
To: <tel:+1-222-333-4444>
Call-ID : asfed03a0sasfe0234123
CSeq: 1 INVITE
Contact: <sip:192.100.100.100:5070>
Content-Type: application/sdp
...

S4-5 180 (UE-B toward AS-FE)

180 (ringing) is sent toward the AS-FE through network elements. The contact value includes
UE-B's SIP URI.

SIP/2.0 180 Ringing

From: <sip:ue-a@orig_ngn.net>;tag=asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

Rec. ITU-T Q.3610 (05/2009) 27

S8 183 with SDP (AS-FE toward UE-A)
The AS-FE sends an 183 provisional response with the SDP of the MRP-FE. The contact value
includes AS-FE's SIP URI.

SIP/2.0 183 Session Progress

From: <sip:ue-a@ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=asfe22222122
Call-ID : ueacb03a0suea00234123
Contact: <sip:192.100.100.100:5070>
Content-Type: application/sdp
...

S12-13 200 OK (UE-B toward AS-FE)

When the called party answers, the UE-B sends a 200 OK (with SDP B) final response to the
INVITE request (3). The S-CSC-FE forwards the 200 OK response to the AS-FE.

SIP/2.0 200 OK
From: <sip:ue-a@orig_ngn.net>;tag= asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
...

S16 200 OK (AS-FE toward UE-A)

The AS-FE sends a 200 OK without SDP for SDP offer-answer model [b-IETF RFC 3264]. The
S-CSC-FE forwards the 200 OK response to the UE-A.

SIP/2.0 200 OK
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag= asfe22222122
Call-ID : ueacb03a0suea00234123
Contact: <sip:192.100.100.100:5070>
Cseq: 1 INVITE
...

S17 ACK (UE-A toward P/S-CSC-FE)

The UE-A responds to the 200 OK with an ACK request towards the UE-B.

ACK sip:192.100.100.100:5070 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag= asfe22222122
Call-ID : ueacb03a0suea00234123
Cseq: 1 INVITE
...

28 Rec. ITU-T Q.3610 (05/2009)

S18 Re-INVITE (AS-FE toward UE-A)
The AS-FE should exchange session information with the UE-A. Therefore, the AS-FE sends the
re-INVITE (without SDP) request to the UE-A. The contact value includes AS-FE's SIP URI.

INVITE sip:192.100.200.51:5090 SIP/2.0

From: : <tel:+1-222-333-4444>;tag= asfe22222122
To : <sip:ue-a@orig_ngn.net>;tag=171828
Call-ID : ueacb03a0suea00234123
Contact: <sip:192.100.100.100:5070>
Cseq: 1 INVITE
...

S19 200 OK (UE-A toward AS-FE)

The UE-A responds to the re-INVITE (without SDP) request with 200 OK (with SDP A). The
contact value includes UE-A's SIP URI.

SIP/2.0 200 OK
From: : <tel:+1-222-333-4444>; tag= asfe22222122
To : <sip:ue-a@orig_ngn.net>;tag=171828
Call-ID : ueacb03a0suea00234123
Contact: <sip:192.100.200.51:5090>
CSeq: 1 INVITE
Content-Type: application/sdp
...

S20-21 Re-INVITE (AS-FE toward UE-B)

The AS-FE generates the re-INVITE request with the SDP of the UE-A. Then, the AS-FE sends the
re-INVITE request to the UE-B. The contact value includes AS-FE's SIP URI.

INVITE sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag= asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
Contact: <sip:192.100.100.100:5070>
CSeq: 2 INVITE
Content-Type: application/sdp
...

Rec. ITU-T Q.3610 (05/2009) 29

S22-23 200 OK (UE-B toward AS-FE)
The UE-B responds to the re-INVITE request with 200 OK (with SDP B). The contact value
includes UE-B's SIP URI.

SIP/2.0 200 OK
From: <sip:ue-a@orig_ngn.net>;tag= asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
Contact: < sip:192.100.200.52:5080>
Cseq: 2 INVITE
Content-Type: application/SDP
...

S24 ACK (AS-FE toward UE-A)

The AS-FE responds to the 200 OK (19) response with an ACK (with SDP B) request to the UE-A.

ACK sip:192.100.200.51:5090 SIP/2.0

From: : <tel:+1-222-333-4444>; tag= asfe22222122
To : <sip:ue-a@orig_ngn.net>;tag=171828
Call-ID : ueacb03a0suea00234123
Cseq: 1 INVITE
Content-Type: application/sdp
...

S25-26 ACK (AS-FE toward UE-B)

The AS-FE responds to the 200 OK (23) response with an ACK request to the UE-B.

ACK sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag= asfe171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : asfed03a0sasfe0234123
Cseq: 2 INVITE
...

30 Rec. ITU-T Q.3610 (05/2009)

I.3 CRBT service by application server model
Figure I.3 signalling flow shows a CRBT service provided by the application server model scenario:

Figure I.3 – CRBT service provided by application server model

The procedures of SIP signalling are as follows:

S1 INVITE (UE-A toward S-CSC-FE)
The INVITE request is sent from the UE-A to S-CSC-FE of the terminating side. The S-CSC-FE
evaluates the initial filter criteria and forwards the INVITE to the CRBT AS-FE. The contact value
includes UE-A's SIP URI that contains the IP address.

Rec. ITU-T Q.3610 (05/2009) 31

 INVITE sip:ue-b@term_ngn.net SIP/2.0
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>, <tel:+1-222-555-3333>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer, early-session, 100rel
Accept: application/sdp
Session-Expires: 3600;refresher=uac
Content-Type: application/sdp
...

S2 INVITE (AS-FE toward UE-B)

INVITE is sent toward the UE-B through network elements (AS-FE may be the Proxy server). The
contact value includes UE-A's SIP URI.

INVITE sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Supported: timer, early-session, 100rel
Contact: <sip:192.100.200.51:5090>
Content-Type: application/sdp
...

S3 180 (UE-B toward AS-FE)

180 (ringing) is sent toward the AS-FE through network elements. The contact value includes
UE-B's SIP URI.

SIP/2.0 180 Ringing

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

32 Rec. ITU-T Q.3610 (05/2009)

S4 183 (AS-FE toward UE-A)
The AS-FE inserts an early-session SDP within an 183 (Session Progress) provisional response. 183
is sent toward the UE-A through network elements.

SIP/2.0 183 Session Progress

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Require: early-session, 100rel
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: early-session
...

S5 PRACK (UE-A toward AS-FE)

PRACK is sent toward the AS-FE through network elements.

PRACK sip:ue-b@term_ngn.net SIP/2.0

From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.51:5090>
Content-Type: application/sdp
Content-Disposition: early-session
...

S6 200 (AS-FE toward UE-A)

200 (OK) is sent toward the UE-A through network elements. The contact value includes UE-B's
SIP URI.

SIP/2.0 200 OK
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.52:5080>
Content-Length: 0

S7 180 (AS-FE toward UE-A)

180 (ringing) is sent toward the UE-A through network elements. The contact value includes
UE-B's SIP URI.

Rec. ITU-T Q.3610 (05/2009) 33

 SIP/2.0 180 Ringing
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

S8-9 200 (UE-B toward UE-A)

200 (OK) is sent toward the UE-A through network elements. The contact value includes UE-B's
SIP URI.

SIP/2.0 200 OK
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: session
...

S10-11 ACK (UE-A toward UE-B)

UE-A responds to the 200 OK with an ACK request to the UE-B.

ACK sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Content-Length: 0

34 Rec. ITU-T Q.3610 (05/2009)

I.4 CRBT service by HTTP model (Originating IMS-UE case)
Figure I.4 signalling flow shows a CRBT service provided by the HTTP model scenario:

Originating Net. CRBT IconRingTone

P/S/I-CSC-FE UE-B
UE-A AS-FE Server

S1:INVITE(offer A)
S2:INVITE(offer A)
S3:INVITE(offer A)
S4:180
S5:180
Alerting
H6:GET(with URI)
H7:200OK(URL)
S8:18X (call-info / alert-info)
H9:GET(File URL)
H10:200OK(with File)
file download with TCP

CRBT play

Answer
S11:200OK(answer B)
S12:200OK(answer B)
S13:200OK(answer B)
S14:ACK
CRBT stop S15:ACK
S16:ACK
A-B with RTP

Figure I.4 – CRBT service by HTTP model (Originating IMS-UE case)

The procedures of SIP signalling are as follows:

S1 INVITE (UE-A toward S-CSC-FE)
The INVITE request is sent from the UE-A to the S-CSC-FE of the terminating side. The
S-CSC-FE evaluates the initial filter criteria and forwards the INVITE to the CRBT AS-FE. The
contact value includes UE-A's SIP URI that contains the IP address.

Rec. ITU-T Q.3610 (05/2009) 35

 INVITE sip:ue-b@term_ngn.net SIP/2.0
Route: <sip:crbt@as-fe.term_ngn.net; lr>, <sip:1.23.233143.23@s-csc-fe.term_ngn.net;lr>
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>, <tel:+1-222-555-3333>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer, early-session
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, MESSAGE, INFO, REFER, NOTIFY, SUBSCRIBE
Accept: application/sdp
Session-Expires: 3600;refresher=uac
Content-Type: application/sdp
...

S2-3 INVITE (AS-FE toward UE-B)

INVITE is sent toward the UE-B through network elements (AS-FE may be the Proxy server). The
contact value includes UE-A's SIP URI.

INVITE sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.51:5090>
Content-Type: application/sdp
...

S4-5 180 (UE to AS-FE)

180 (ringing) is sent toward the AS-FE through network elements. The contact value includes
UE-B's SIP URI.

SIP/2.0 180 Ringing

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

H6-7 HTTP or SOAP (between CRBT AS-FE and CRBT HTTP server).
The AS-FE gets the URL of the CRBT from the HTTP server using any TCP-based protocol.

36 Rec. ITU-T Q.3610 (05/2009)

S8 18x (AS-FE toward UE-A)
The AS-FE inserts Call-Info header or Alert-Info header within the provisional response bearing a
code 18x. 18x is sent toward the UE-A through network elements.

SIP/2.0 18x
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Call-Info : <http://crbt_as.ngn.com/mmcid/bimg20001000000001731.gif>; purpose=icon,
<http://crbt_as.ngn.com/mmcid/user_info_0251148012.xml>; purpose=info
Alert-Info : http://crbt_as.ngn.com/mmcid/bimg20001000000001731.wav
...

H9-10. HTTP GET and File downloading (between CRBT AS-FE and CRBT HTTP server).
The UE-B requests HTTP GET Message with URL. Then, the UE-B downloads and plays the
CRBT media file.
S11-13 200 OK (UE-B toward UE-A)
When the called party answers, the UE-B sends a 200 OK (with SDP B) final response to the
INVITE request. Then, the UE-B stops the CRBT media. The contact value includes UE-B's SIP
URI.

SIP/2.0 200 OK
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
...

S14-16 ACK (UE-A toward UE-B)

The UE-A responds to the 200 OK with an ACK request to the UE-B.

ACK sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
...

I.5 CRBT service by gateway model (Originating PSTN/ISDN interworking case)

Figure I.5 signalling flow shows a CRBT service provided by the gateway model scenario in
interworking with the originating PSTN/ISDN case:
NOTE 1 – Messages from M1 ~ M8 are shown as examples and are based on [ITU-T H.248.1].
NOTE 2 – This signalling flow shows the case of regular session establishment with re-INVITE.

Rec. ITU-T Q.3610 (05/2009) 37

 SG-FE/
MGC-FE/ CRBT P-CSC-FE/
PSTN/ISDN TMG-FE S-CSC-FE MRC/P-FE
I-CSC-FE AS-FE UE-B

I1:IAM
M1:ADD
M2:ADD_REPLY
S1:INVITE(offer A)
S2:INVITE(offer A)
S3:INVITE(offer A)
S4:180
S5:180
Connection &
Acquire CRBT sdp

S8:183(CRBT answer)
M3:MODIFY
I2:ACM Media control
M4:MODIFY_REPLY

Play CRBT with RTP

Answer
CRBT play S12:200OK(answer B)
S13:200OK(answer B)

Disconnection

S16:200OK
S17:ACK
S17:ACK
S17:ACK
S18:RE-INVITE(No SDP)
M5:MODIFY
M6:MODIFY_REPLY
S19:200 OK (offer A)
S20:RE-INVITE(offer A)
S21:RE-INVITE(offer A)
S22:200 OK (answer B)
S23:200 OK (answer B)
S24:ACK(answer B)
M7:MODIFY
S25:ACK
I3:ANM
S26:ACK
M8:MODIFY_REPLY

CRBT stop A-B with RTP

Figure I.5 – CRBT service by gateway model (Originating PSTN/ISDN interworking case)

The procedure of the SIP signalling is the same as the IMS-based gateway model, and the
significant messages of ISUP and H.248 signalling are shown as follows:
I1 IAM (PSTN/ISDN to SG-FE/MGC-FE)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
...

38 Rec. ITU-T Q.3610 (05/2009)

M1 ADD_REQUEST (MGC-FE to TMG-FE)
H.248/1[192.100.101.230]:2944..Transaction=79764497{..Context=${..Add=C2/21/1{..
Media{..Stream=1{..LocalControl{..Mode=ReceiveOnly..}..}..},..Events=79764497{..ctyp/dto
ne..}..},..Add=${..Media{..Stream=1{..LocalControl{..Mode=SendReceive..},..Local{..v=0..c
=IN IP4 $..m=audio $ RTP/AVP 8 0 4 18..}..}..}..}..}..}
M2 ADD_REPLY (TMG-FE to MGC-FE)
H.248/1 [192.100.101.240]:2944.Reply = 79764497 {.Context = 9578 {.Add = C2/21/1,.Add =
EPH1004 {..Media {..Local{..v=0..o=gw-vendor 1 208926965 1208926965 IN IP4
192.100.101.240..s=H.248 Call..c=IN IP4 192.100.101.240..t=0 0..m=audio 22008 RTP/AVP
8..a=ptime:10.. }.}.}.}.}.
M3 MODIFY_REQUEST (MGC-FE to TMG-FE)
H.248/1[192.100.101.230]:2944..Transaction=81861649{..Context=9578{..Modify=C2/21/1{.
.Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=81861649{..ctyp/dt
one..},..Signals{....}..},..Modify=EPH1004{..Media{..Stream=1{..LocalControl{..Mode=Send
Receive..},..Remote{..v=0..o =as-vendor 1079426802 1 IN IP4 192.100.100.200..s=media-
server..c=IN IP4 192.100.100.200..t=0 0..m=audio 49300 RTP/AVP 8....}..}..}..}..}..}
I2 ACM (SG-FE/MGC-FE to PSTN/ISDN)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
M4 MODIFY_REPLY (TMG-FE to MGC-FE)
H.248/1[192.100.101.240]:2944..Reply=81861649{..Context=9578{..Modify=C2/21/1,.Modif
y = EPH1004..}..}.
M5 MODIFY_REQUEST (MGC-FE to TMG-FE)
H.248/1[192.100.101.230]:2944..Transaction=163642882{..Context=9578{..Modify=C0/26{..
Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=163642882{..al/on,a
l/fl,ctyp/dtone..},..Signals{....}..},..Modify=
EPH1004{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..},..Local{..v=0..c=IN
IP4 $..m=audio $ RTP/AVP 8 0 4 18..}..}..}..}..}..}
M6 MODIFY _REPLY (TMG-FE to MGC-FE)
H.248/1 [192.100.101.240]:2944.Reply=163642882{..Context=9578 ...Modify=C0/26,
..Modify= EPH1004{....Media{.. Local{..v=0..o=gw-vendor 1 208926965 1208926965 IN IP4
192.100.101.240..s=H.248 Call..c=IN IP4 192.100.101.240..t=0 0..m=audio 22008 RTP/AVP
8..a=ptime:10.. }..}..}..}
M7 MODIFY_REQUEST (MGC-FE to TMG-FE)
H.248/1[192.100.101.230]:2944..Transaction=83958801{..Context=9578{..Modify=C2/21/1{.
.Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=83958801{..ctyp/dt
one..},..Signals{....}..},..Modify=EPH1004{..Media{..Stream=1{..LocalControl{..Mode=Send
Receive..},..Remote{..v=0..o=ip-phone-vendor 1208972718 0 IN IP4 192.100.200.52..s=ip-

Rec. ITU-T Q.3610 (05/2009) 39

 phone-vendor IP_CALL.. c=IN IP4 192.100.200.52..t=0 0..m=audio 10262 RTP/AVP
8..b=AS:96..a=rtpmap:8 PCMA/8000..a=sendrecv....}..}..}..}..}..}
I3 ANM (SG-FE/MGC-FE to PSTN/ISDN)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
M8 MODIFY _REPLY (TMG-FE to MGC-FE)
H.248/1[192.100.101.240]:2944.Reply=83958801{..Context=9578{..Modify=C2/21/1,.Modify
= EPH1004..}..}

I.6 CRBT service by gateway model (Originating POTS-UE case)

Figure I.6 signalling flow shows a IMS-based CRBT service by the gateway model scenario in the
POTS-UE originating case:
NOTE 1 – This signalling flow shows the case of regular session establishment with re-INVITE.
NOTE 2 – Messages from M1 ~ M14 are shown as examples and are based on [ITU-T H.248.1].

40 Rec. ITU-T Q.3610 (05/2009)

 AMG-FE/ CRBT
Call Server S/I-CSC-FE MRC/P-FE UE-B
Legacy Terminal AS-FE
Off-hook M1:NOTIFY(off-hook)
M2:NOTIFY_REPLY
M3:MODIFY
M4:MODIFY_REPLY

M5:NOTIFY(digit)
M6:MODIFY_REPLY
M7:ADD

M8:ADD_REPLY
S1:INVITE(offer A)

S2:INVITE(offer A)
S3:INVITE(offer A)
S4:180
S5:180

Connection
& Acquire CRBT sdp
S8:183(CRBT answer)
M9:MODIFY
M10:MODIFY_REPLY Media control

Play CRBT with RTP

Answer
CRBT play S12:200OK(answer B)
S13:200OK(answer B)

Disconnection
S16:200OK
S17:ACK
S17:ACK
S17:ACK
S18:RE-INVITE(No SDP)
M11:MODIFY
M12:MODIFY_REPLY
S19:200 OK (offer A)
S20:RE-INVITE(offer A)
S21:RE-INVITE(offer A)
S22:200 OK (answer B)
S23:200 OK (answer B)
S24:ACK(answer B)
M13:MODIFY S25:ACK
M14:MODIFY_REPLY S26:ACK

CRBT stop
A-B with RTP

Figure I.6 – IMS-based CRBT service by gateway model (Originating POTS-UE case)

The procedure of the SIP signalling is the same as the IMS-based gateway model.
The procedure of H.248 signalling is as follows and significant messages are shown in detail:
M1-M6 Collecting dialled digits based on provided digit maps
M7 ADD (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=146865666{..Context=${..Add=C0/26{..Media
{..Stream=1{..LocalControl{..Mode=ReceiveOnly..}..}..},..Events=146865666{..al/on,al/fl,dd/
ce { DigitMap = dialplan0}..},..EventBuffer{..dd/ce..},..DigitMap=dialplan0{..T:4,S:0,L:4,
([0-9EF])..}..},..Add=$ {..Media {..Stream=1
{..LocalControl{..Mode=SendReceive..},..Local{..v=0..c=IN IP4 $..m=audio $ RTP/AVP 8 0
4 18..}..}..}..}..}..}

Rec. ITU-T Q.3610 (05/2009) 41

M8 ADD_REPLY (AMG-FE to AGC-FE)
H.248/1 [192.100.101.220]:2944.Reply=146865666{..Context=134217744 {...Add=C0/26,
...Add=Eph100015{....Media{.. Local{..v=0..o=gw-vendor 1 208926965 1208926965 IN IP4
192.100.101.220..s=H.248 Call..c=IN IP4 192.100.101.220..t=0 0..m=audio 22008 RTP/AVP
8..a=ptime:10.. }...}...}..}.}.
M9 MODIFY (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=161545730{..Context=134217744{..Modify=C0
/26{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=161545730{..a
l/on,al/fl..},..Signals{....}..},..Modify=
Eph100015{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..},.. Remote{..v=0..o
=as-vendor 1079426802 1 IN IP4 192.100.100.200..s=media-server..c=IN IP4
192.100.100.200..t=0 0..m=audio 49302 RTP/AVP 8....}..}..}..}..}..}
M10 MODIFY _REPLY (AMG-FE to AGC-FE)
H.248/1[192.100.101.220]:2944.Reply=161545730{..Context=134217744{.Modify=
C0/26,.Modify = Eph100015..}..}
M11 MODIFY (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=163642882{..Context=134217744{..Modify=C0
/26{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=163642882{..a
l/on,al/fl..},..Signals{....}..},..Modify=
Eph100015{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..},..Local{..v=0..c=IN
IP4 $..m=audio $ RTP/AVP 8 0 4 18..}..}..}..}..}..}
M12 MODIFY _REPLY (AMG-FE to AGC-FE)
H.248/1 [192.100.101.220]:2944.Reply=163642882{..Context=134217744 ...Modify=C0/26,
..Modify= Eph100015{...Media{.. Local{..v=0..o=gw-vendor 1 208926965 1208926965 IN
IP4 192.100.101.220..s=H.248 Call..c=IN IP4 192.100.101.220..t=0 0..m=audio 22008
RTP/AVP 8..a=ptime:10.. }..}..}..}
M13 MODIFY (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=161545730{..Context=134217744{..Modify=C0
/26{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=161545730{..a
l/on,al/fl..},..Signals{....}..},..Modify=Eph100015{..Media{..Stream=1{..LocalControl{..Mode
=SendReceive..},.. Remote{.v=0..o=samsung 1234 0 IN IP4 192.100.200.52..s=-..c=IN IP4
192.100.200.52..t=0 0.. m=audio 4150 RTP/AVP 8 0 4 4 18..a=ptime:10..}..}..}..}..}..}
M14 MODIFY _REPLY (AMG-FE to AGC-FE)
H.248/1[192.100.101.220]:2944..Reply=161545730{..Context=134217744{.Modify=
C0/26,.Modify = Eph100015..}..}

I.7 Call server-based CRBT service by gateway model (Originating IMS-UE case)
Figure I.7 signalling flow shows a call server-based CRBT service by the gateway model scenario
in the IMS-UE Originating case:
NOTE – This signalling flow shows the case of regular session establishment with re-INVITE.

42 Rec. ITU-T Q.3610 (05/2009)

 CRBT AMG-FE/
UE-A P/S/I-CSC-FE MRC/P-FE Call Server
AS-FE Legacy Terminal

S1:INVITE(offer A)
S2:INVITE(offer A)
S3:INVITE(offer A)
M1:ADD
M2:ADD_REPLY
M3:MODIFY
M4:MODIFY_REPLY
S4:180
S5:180
Connection &
Acquire CRBT sdp
S8:183(CRBT answer)

Media control
CRBT play Answer
Play CRBT with RTP
M5:NOTIFY

M6:NOTIFY_REPLY
S12:200OK(answer B)
S13:200OK(answer B)

Disconnection

S16:200OK
S17:ACK
CRBT stop
S17:ACK
S17:ACK
S18:RE-INVITE(No SDP)
S19:200 OK (offer A)
S20:RE-INVITE(offer A)
S21:RE-INVITE(offer A)
M7:MODIFY
M8:MODIFY_REPLY
S22:200 OK (answer B)
S23:200 OK (answer B)
S24:ACK(answer B)
S25:ACK
S26:ACK
A-B with RTP

Figure I.7 – Call server-based CRBT service by gateway model (Originating IMS-UE case)

The procedure of the SIP signalling is the same as the IMS-based gateway model, and the procedure
of H.248 signalling is as follows:
M1 ADD_REQUEST (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=79721793{..Context=${..Add=C0/17{..Media{.
.Stream=1{..LocalControl{..Mode=ReceiveOnly..}..}..},..Events=79721793{..al/of..}..},..Add
=${..Media{..Stream=1{..LocalControl{.. Mode=ReceiveOnly..},..Local{..v=0..c=IN IP4
$..m=audio $ RTP/AVP 8 0 4 18..},..Remote{..v=0..o=LGE 1234 0 IN IP4
192.100.200.51..s=-..c=IN IP4 192.100.200.51..t=0 0..m=audio 23650 RTP/AVP 8 0 4
18..b=TIAS:64000..b=AS:96..a=fmtp: 4 annexa=no..a=fmtp:18 annexb=no....}..}..}..}..}..}
M2 ADD_REPLY (AMG-FE to AGC-FE)
H.248/1[192.100.101.220]:2944
..Reply=79721793{Context=240{Add=C0/17,Add=Eph179{Media{Stream=1{

Rec. ITU-T Q.3610 (05/2009) 43

 Local{..v=0..o=LGE 1234 0 IN IP4 192.100.101.220 ..s=-..c=IN IP4 192.100.101.220 ..t=0
0..m=audio 23838 RTP/AVP 8..b=TIAS:64000.. b=AS:96..a=ptime:10..}}}}}}
M3 MODIFY_REQUEST (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=81818945{..Context=240{..Modify=C0/17{..M
edia{..Stream=1{..LocalControl{..Mode=ReceiveOnly..}..}..},..Events=81818945{..al/of..},..
Signals{..al/ri..}..}..}..}
M4 MODIFY _REPLY (AMG-FE to AGC-FE)
H.248/1[192.100.101.220]:2944 ..Reply=81818945{Context=240{Modify=C0/17}}
M5 NOTIFY_REQUEST (AMG-FE to AGC-FE)
H.248/1[192.100.101.220]:2944
..Transaction=13662{Context=240{Notify=C0/17{ObservedEvents=81818945{al/of}}}}
M6 NOTIFY_REPLY (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Reply=13662{..Context=240{..Notify =C0/17..}..}
M7 MODIFY_REQUEST (AGC-FE to AMG-FE)
H.248/1[192.100.101.210]:2944..Transaction=163642882{..Context=240{..Modify=
C0/17{..Media{..Stream=1{..LocalControl{..Mode=SendReceive..}..}..},..Events=163642882
{..al/on,al/fl..},..Signals{....}..},..Modify=Eph179{..Media{..Stream=1{..LocalControl{..Mode
=SendReceive..},.. Local{..v=0..c=IN IP4 $ ..m=audio $ RTP/AVP 8 0 4 18..},..
Remote{..v=0..o=LGE 1234 0 IN IP4 192.100.200.51..s =-..c=IN IP4 192.100.200.51..t=0
0..m=audio 23650 RTP/AVP 8 0 4 18..b=TIAS:64000..b=AS:96..a=fmtp:4
annexa=no..a=fmtp:18 annexb=no....}..}..}..}..}..}
M8 MODIFY _REPLY (AMG-FE to AGC-FE)
H.248/1[192.100.101.220]:2944 ..Reply=163642882{..Context=240 {...Modify= C0/17,
...Modify=Eph179{....Media{. Local{..v=0..o=LGE 1234 0 IN IP4 192.100.101.220..s=-..c=IN
IP4 192.100.101.220..t=0 0..m=audio 23838 RTP/AVP
8..b=TIAS:64000..b=AS:96..a=ptime:10..}....}...}..}.}.

44 Rec. ITU-T Q.3610 (05/2009)

I.8 Originating CRBT service interacts with terminating CRBT service by AS model

Originating Net. Originating Originating Originating Terminating Terminating Terminating Terminating Net.
UE-A P/S/I-CSC-FE CRBT AS-FE MRC/P-FE P/S-CSC-FE CRBT AS-FE MRC/P-FE UE-B

S1:INVITE(offer A)
S2:INVITE(offer A)
S2:INVITE(offer A)
S2:INVITE(offer A)
S3:INVITE(offer A)
S3:INVITE(offer A)

S4:183
S4:183 Connection & acquire
CRBT sdp
S5:183(CRBT-T offer) S5:183(CRBT-T offer)

Connection & acquire

CRBT sdp
S6:183(CRBT-O offer)
S6:183(CRBT-O offer)

S7:PRACK
(CRBT-O answer) Media Control

Play CRBT
S8:PRACK
(CRBT-T answer)
CRBT play S8:PRACK(CRBT-T answer) S8:PRACK(CRBT-T answer)
Disconnection

S9:200OK(PRACK)
S9:200OK(PRACK)

S9:200OK(PRACK)
S10:200OK(PRACK)
S10:200OK(PRACK)

Answer
S11:200OK(answer B)

S11:200OK(answer B)

S12:200OK(answer B) S12:200OK(answer B)

S12:200OK(answer B)
Disconnection
S13:200OK(answer B)
S13:200OK(answer B)

CRBT stop

S14:ACK
S15:ACK
S15:ACK
S15:ACK

S16:ACK

A-B with RTP

Figure I.8 – Originating CRBT service interacts with terminating

CRBT service by AS model

The procedures of SIP signalling are as follows:

S1-3 INVITE (UE-A toward Originating S-CSC-FE)
The INVITE request is sent from the UE-A to the S-CSC-FE of the originating side. The originating
S-CSC-FE evaluates the initial filter criteria and forwards the INVITE to the originating CRBT
AS-FE, the originating CRBT AS-FE checks the CRBT priority setting, then the originating CRBT
AS-FE forwards the INVITE to the terminating S-CSC-FE, and the terminating S-CSC-FE
evaluates the initial filter criteria and forwards the INVITE to the terminating CRBT AS-FE.
Finally, the INVITE is forwarded to the UE-B. The contact value includes UE-A's SIP URI that
contains the IP address.

Rec. ITU-T Q.3610 (05/2009) 45

 INVITE sip:ue-b@term_ngn.net SIP/2.0
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>, <tel:+1-222-555-3333>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer, early-session, 100rel
Accept: application/sdp
Session-Expires: 3600;refresher=uac
Content-Type: application/sdp
...

S4 183 (UE-B toward terminating CRBT AS-FE)

The UE-B responds with "183 Session Process" towards the terminating CRBT AS-FE.

SIP/2.0 183 Session Process

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

46 Rec. ITU-T Q.3610 (05/2009)

S5 183 (terminating CRBT AS-FE toward originating CRBT AS-FE)
The terminating CRBT AS-FE adds CRBT-T offer SDP to an 183 response and forwards the
183 response to the originating CRBT AS-FE.

SIP/2.0 183 Session Process

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Require :100rel
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 eee:fff:aaa:bbb
s=-
c=IN IP4 ccc:aaa:bbb:acc
t=0 0
m=audio 3456 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

Rec. ITU-T Q.3610 (05/2009) 47

S6 183 (originating CRBT AS-FE toward UE-A)
Due to the fact that the originating CRBT has priority according to the priority setting, the
originating CRBT AS-FE adds CRBT-O offer SDP, instead of CRBT-T offer, in a 183 response and
forwards the 183 to the UE-A. The originating CRBT AS-FE plays the originating CRBT to UE-A.

SIP/2.0 183 Session Process

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Require :100rel
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 aaa:bbb:eee:fff
s=-
c=IN IP4 ccc:aaa:bbb:acc
t=0 0
m=audio 3456 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

48 Rec. ITU-T Q.3610 (05/2009)

S7 PRACK (UE-A toward originating CRBT AS-FE)
The UE-A completes the originating CRBT media negotiation and sends PRACK with CRBT-O
answer SDP to the originating CRBT AS-FE.

PRACK sip:ue-b@term_ngn.net SIP/2.0

From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.51:5090>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 aaa:bbb:ccc:ddd
s=-
c=IN IP4 aaa:bbb:ccc:ddd
t=0 0
m=audio 3466 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes...
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

Rec. ITU-T Q.3610 (05/2009) 49

S8 PRACK (originating CRBT AS-FE toward terminating CRBT AS-FE)
The originating CRBT AS-FE sends PRACK to the terminating CRBT AS-FE, which contains
CRBT-T answer SDP setting port to 0 to refuse the terminating CRBT media negotiation.

PRACK sip:ue-b@term_ngn.net SIP/2.0

From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.51:5090>
Content-Type: application/sdp
Content-Disposition: early-session
v=0
o=- 2987933616 2987933616 IN IP4 aaa:bbb:ccc:ddd
s=-
c=IN IP4 aaa:bbb:ccc:ddd
t=0 0
m=audio 0 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes...
m=video 0 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=inactive
a=rtpmap:98 H263
...

S9 200 (terminating CRBT AS-FE toward originating CRBT AS-FE)

200 (OK) is sent toward the originating CRBT AS-FE through network elements. The contact value
includes UE-B's SIP URI.
SIP/2.0 200 OK
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.52:5080>
Content-Length: 0

50 Rec. ITU-T Q.3610 (05/2009)

S10 200 (originating CRBT AS-FE toward UE-A)
200 (OK) is sent toward the UE-A through network elements. The contact value includes the
UE-B's SIP URI.

SIP/2.0 200 OK
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.52:5080>
Content-Length: 0

S11-13 200 (UE-B toward UE-A)

200 (OK) is sent toward the UE-A through network elements. The contact value includes UE-B's
SIP URI.

SIP/2.0 200 OK
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: session
...

S14-16 ACK (UE-A toward UE-B)

The UE-A responds to the 200 OK with an ACK request to the UE-B.

ACK sip:192.100.200.52:5080 SIP/2.0

From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Content-Length: 0

Rec. ITU-T Q.3610 (05/2009) 51

I.9 Providing circuit switched network CRBT to the originating UE in IMS domain

Figure I.9 – Providing circuit switched network CRBT to the

originating UE in IMS domain

The procedures of SIP signalling and the significant messages of ISUP and H.248 signalling are
shown as follows:
S1 INVITE (UE-A toward MGC-FE)
The UE-A sends "INVITE" to the MGC-FE. The INVITE includes the UE-A's SDP offer and early
session supported indication.

52 Rec. ITU-T Q.3610 (05/2009)

 INVITE tel:+1-222-333-4444 SIP/2.0
From: <sip:ue-a@orig_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>, <tel:+1-222-555-3333>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer, early-session, 100rel
Accept: application/sdp
Session-Expires: 3600;refresher=uac
Content-Type: application/sdp
...

S2 183 (MGC-FE toward UE-A)

The MGC-FE sends "183 session progress" to the UE-A with a MGC-FE SDP answer.

SIP/2.0 183 session progress

From: < sip:ue-a@orig_ngn.net >;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Require :100 rel
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
...

S3 PRACK (UE-A toward MGC-FE)

The UE-A sends PRACK to the MGC-FE.

PRACK sip:ue-b@term_ngn.net SIP/2.0

From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.51:5090>

Rec. ITU-T Q.3610 (05/2009) 53

S4 200 (MGC-FE toward UE-A)
200 (OK) is sent toward the UE-A through network elements.

SIP/2.0 200 OK
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.52:5080>
Content-Length: 0

I1 IAM (MGC-FE to PSTN/ISDN)

Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
...
I2 ACM (PSTN/ISDN to MGC-FE) with in-band information indicator
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
In-band information Indicator = 1
Transmission Medium Requirement
Calling Party Number = 2225553333
S5 180 (MGC-FE toward UE-A)
The MGC-FE checks that the UE-A supports early session, and sends "180 Ringing" to the UE-A,
which includes the MGC-FE CRBT early session offer.

54 Rec. ITU-T Q.3610 (05/2009)

 SIP/2.0 180 Ringing
From: < sip:ue-a@orig_ngn.net >;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Require :100 rel
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 :aaa:bbb:eee:fff
s=-
c=IN IP4 ccc:aaa:bbb:acc
t=0 0
m=audio 3456 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

S6 PRACK (UE-A toward MGC-FE)

The UE-A sends PRACK to the MGC-FE with a UE-A CRBT early session answer.

Rec. ITU-T Q.3610 (05/2009) 55

 PRACK sip:ue-b@term_ngn.net SIP/2.0
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.51:5090>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 aaa:bbb:ccc:ddd
s=-
c=IN IP4 aaa:bbb:ccc:ddd
t=0 0
m=audio 3466 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes...
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

S7 200 (MGC-FE toward UE-A)

200 (OK) is sent toward the UE-A through network elements.

SIP/2.0 200 OK
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.52:5080>
Content-Length: 0

56 Rec. ITU-T Q.3610 (05/2009)

I3 ANM (PSTN/ISDN to MGC-FE)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
S8 200 (MGC-FE toward UE-A)
200 (OK) is sent toward the UE-A through network elements.

SIP/2.0 200 OK
From: < sip:ue-a@orig_ngn.net >;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

S9 ACK (UE-A toward MGC-FE)

200 (OK) is sent toward the MGC-FE through network elements.

ACK sip:192.100.200.52:5080 SIP/2.0

From: < sip:ue-a@orig_ngn.net >;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Content-Length: 0

Rec. ITU-T Q.3610 (05/2009) 57

I.10 Providing IMS CRBT to the originating UE in circuit switched network domain

I4:

Figure I.10 – Providing IMS CRBT to the originating UE in

circuit switched network domain

The procedure of the SIP signalling and the significant messages of ISUP and H.248 signalling are
shown as follows:
I1 IAM (PSTN/ISDN to SG-FE/MGC-FE)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
...
S1-2 INVITE (MGC-FE toward UE-B)
The INVITE request is sent from the MGC-FE to S-CSC-FE of the terminating side, the terminating
S-CSC-FE evaluates the initial filter criteria and forwards the INVITE to the terminating CRBT
AS-FE. Finally, the INVITE is forwarded to the UE-B. The contact value includes MGC-FE's IP
address.

58 Rec. ITU-T Q.3610 (05/2009)

 INVITE sip:ue-b@term_ngn.net SIP/2.0
From: < tel:+1-222-555-3333>;tag=171828
To: <tel:+1-222-333-4444>
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
P-Preferred-Identity: <sip:ue-a@orig_ngn.net>
Privacy: none
Contact: <sip:192.100.200.51:5090>
Supported: timer, early-session, 100rel
Accept: application/sdp
Session-Expires: 3600;refresher=uac
Content-Type: application/sdp
...

S3 180 (UE-B toward terminating CRBT AS-FE)

The UE-B responds with "180 Ringing" towards the terminating CRBT AS-FE.

SIP/2.0 180 Ringing

From: < tel:+1-222-555-3333>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
...

S4 180 (terminating CRBT AS-FE toward MGC-FE)

The terminating CRBT AS-FE adds CRBT-T offer SDP to the 180 response and forwards the
180 response to the MGC-FE.

Rec. ITU-T Q.3610 (05/2009) 59

 SIP/2.0 180 Ringing
From: < tel:+1-222-555-3333>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Require :100rel
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 eee:fff:aaa:bbb
s=-
c=IN IP4 ccc:aaa:bbb:acc
t=0 0
m=audio 3456 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos mandatory remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

I2 The MGC-FE checks if the CRBT contains video according to the message from CRBT
AS-FE; if yes, then, it asks the MSC to connect the calling party using an ACM message
with in-band information indicator and holds an H.245 negotiation with the calling party.
ACM (SG-FE/MGC-FE to PSTN/ISDN)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
In-band information Indicator = 1
Transmission Medium Requirement
Calling Party Number = 2225553333

60 Rec. ITU-T Q.3610 (05/2009)

I3 If the ACM has already been sent, the MGC-FE sends CPG.
CPG (SG-FE/MGC-FE to PSTN/ISDN)
Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
In-band information Indicator = 1
Transmission Medium Requirement
Calling Party Number = 2225553333
S5 PRACK (MGC-FE toward CRBT AS-FE)
The MGC-FE completes the terminating CRBT media negotiation and sends PRACK with CRBT
answer SDP to the originating CRBT AS-FE.
PRACK sip:ue-b@term_ngn.net SIP/2.0
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.51:5090>
Content-Type: application/sdp
Content-Disposition: early-session
Content-Length: (...)

v=0
o=- 2987933616 2987933616 IN IP4 aaa:bbb:ccc:ddd
s=-
c=IN IP4 aaa:bbb:ccc:ddd
t=0 0
m=audio 3466 RTP/AVP 97
b=AS:25.4
a=curr:qos local sendrecv
a=curr:qos remote sendrecv
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:97 AMR
a=fmtp:97 mode-set=0,2,5,7; maxframes...
m=video 3400 RTP/AVP 98
b=AS:75
a=curr:qos local none
a=curr:qos remote none
a=des:qos mandatory local sendrecv
a=des:qos none remote sendrecv
a=rtpmap:98 H263

Rec. ITU-T Q.3610 (05/2009) 61

S6 200 (CRBT AS-FE toward MGC-FE)
200 (OK) is sent toward the MGC-FE through network elements. The contact value includes
UE-B's SIP URI.

SIP/2.0 200 OK
From: <sip:crbt@as-fe.term_ngn.net>;tag=171828
To: <tel:+1-222-333-4444>; tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 PRACK
Contact: <sip: 192.100.200.52:5080>
Content-Length: 0

S7-8 200 (UE-B toward MGC-FE)

200 (OK) is sent toward the MGC-FE through network elements. The contact value includes
UE-B's SIP URI.

SIP/2.0 200 OK
From: < tel:+1-222-555-3333>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Contact: <sip:192.100.200.52:5080>
Content-Type: application/sdp
Content-Disposition: session
...

I4 ANM (SG-FE/MGC-FE to PSTN/ISDN)

Called Party Number = 02223334444
Calling Party's Category
Nature of Connection Indicators
Forward Call Indicators
Transmission Medium Requirement
Calling Party Number = 2225553333
S9-10 ACK (MGC-FE toward UE-B)
The UE-A responds to the 200 OK with an ACK request to the UE-B.

ACK sip:192.100.200.52:5080 SIP/2.0

From: < tel:+1-222-555-3333>;tag=171828
To: <tel:+1-222-333-4444>;tag=22222122
Call-ID : ueacb03a0suea00234123
CSeq: 1 INVITE
Content-Length: 0

62 Rec. ITU-T Q.3610 (05/2009)

 Bibliography

[b-ITU-T E.212] Recommendation ITU-T E.212 (2008), The international

identification plan for public networks and subscriptions.
[b-ITU-T Q-Sup.55] ITU-T Q-series Recommendations – Supplement 55 (2007),
Signalling requirements at the interface between AS-FE and
S-CSC-FE.
[b-ITU-T Q.763] Recommendation ITU-T Q.763 (1999), Signalling System No. 7 –
ISDN User Part formats and codes.
[b-ITU-T Q.1912.5] Recommendation ITU-T Q.1912.5 (2004), Interworking between
Session Initiation Protocol (SIP) and Bearer Independent Call
Control protocol or ISDN User Part.
[b-ITU-T Q.3030] Recommendation ITU-T Q.3030 (2008), Signalling architecture for
the NGN service control plane.
[b-ITU-T Y.2021] Recommendation ITU-T Y.2021 (2006), IMS for Next Generation
Networks.
[b-ITU-T Y.2031] Recommendation ITU-T Y.2031 (2006), PSTN/ISDN emulation
architecture.
[b-ITU-T Y.2211] Recommendation ITU-T Y.2211 (2007), IMS-based real-time
conversational multimedia services over NGN.
[b-ITU-T Y.2214] Recommendation ITU-T Y.2214 (2009), Service requirements and
functional models for customized multimedia ring services.
[b-JFIF] JPEG File Interchange Format, Version 1.02, September 1, 1992.
[b-IETF RFC 2083] IETF RFC 2083 (1997), PNG (Portable Network Graphics)
Specification Version 1.0.
[b-IETF RFC 2246] IETF RFC 2246 (1999), The TLS Protocol Version 1.0.
[b-IETF RFC 2401] IETF RFC 2401 (1998), Security Architecture for the Internet
Protocol.
[b-IETF RFC 2633] IETF RFC 2633 (1999), S/MIME Version 3 Message Specification.
[b-IETF RFC 2976] IETF RFC 2976 (2000), The SIP INFO Method.
[b-IETF RFC 3264] IETF RFC 3264 (2002), An Offer/Answer Model with the Session
Description Protocol (SDP).
[b-IETF RFC 3398] IETF RFC 3398 (2002), Integrated Services Digital Network (ISDN)
User Part (ISUP) to Session Initiation Protocol (SIP) Mapping.
[b-IETF RFC 3515] IETF RFC 3515 (2003), The Session Initiation Protocol (SIP) Refer
Method.
[b-IETF RFC 3725] IETF RFC 3725 (2004), Best Current Practices for Third Party Call
Control (3pcc) in the Session Initiation Protocol (SIP).

Rec. ITU-T Q.3610 (05/2009) 63

[b-Unicode] The Unicode Consortium (1996), The Unicode Standard, Version 2.0,
Addison-Wesley Developers Press, ISBN 0-201-48345-9.
[b-GIF87a] CompuServe Incorporated (1987), GIF Graphics Interchange
Format: A Standard defining a mechanism for the storage and
transmission of raster-based graphics information.
[b-GIF89a] Compuserve Incorporated, Columbus, Ohio (1990), Graphics
Interchange Format (Version 89a).

64 Rec. ITU-T Q.3610 (05/2009)

 SERIES OF ITU-T RECOMMENDATIONS

Series A Organization of the work of ITU-T

Series D General tariff principles

Series E Overall network operation, telephone service, service operation and human factors

Series F Non-telephone telecommunication services

Series G Transmission systems and media, digital systems and networks

Series H Audiovisual and multimedia systems

Series I Integrated services digital network

Series J Cable networks and transmission of television, sound programme and other multimedia signals

Series K Protection against interference

Series L Construction, installation and protection of cables and other elements of outside plant

Series M Telecommunication management, including TMN and network maintenance

Series N Maintenance: international sound programme and television transmission circuits

Series O Specifications of measuring equipment

Series P Terminals and subjective and objective assessment methods

Series Q Switching and signalling

Series R Telegraph transmission

Series S Telegraph services terminal equipment

Series T Terminals for telematic services

Series U Telegraph switching

Series V Data communication over the telephone network

Series X Data networks, open system communications and security

Series Y Global information infrastructure, Internet protocol aspects and next-generation networks

Series Z Languages and general software aspects for telecommunication systems

Printed in Switzerland
Geneva, 2010