USSD CB Call Flow Recap & SR3511 Monitoring Guide

USSD Callback is a service supported by Ericssons RCS 4.5 service platform that allows a roaming
subscriber to request call setup to another mobile user via a USSD code. The request is handled
by a service control point in the subscribers home network which uses the resources of an
Intelligent Peripheral (IP) to make calls to the original subscriber and his desired called party. The
two calls are bridged in the IP. An optional announcement can be played to the calling subscriber
before the called party is contacted.

The Intelligent Peripheral is controlled by SR3511 messages and the service is implemented by
two play applications: Create Call and Create and Bridge Calls

CvAS
HLR
GMSC
Okeford
MSC
ISUP
Subscriber A
Subscriber B
SR-3511



1. Subscriber A sends USSD Request to CvAS via GMSC and HLR
2. CvAS establishes SR3511 dialog with the Okeford IP
3. CvAS invokes Create Call PlayApp on Okeford IP
4. Okeford IP makes an outbound call to Subscriber A; optionally plays announcement when
answered
5. CvAS invokes Create and Bridge Calls Play App on Okeford IP.
6. Okeford IP makes outbound call to Subscriber B and bridges the calls
7. CvAS ends SR3511 dialog with Okeford IP
8. Okeford IP maintains bridge until the call is complete.
9. CvAS applies real-time charging via MSC independent of Okeford IP (i.e. CvAS will instruct
MSC to end call on balance expiry rather than instruct Okeford to end the call).



SR3511 Virtual Circuit Status


The SR3511 connections are made over Ethernet. TTSL provided us with SR3511 destinations which
are provisioned in the GUI in the SR3511 section.
The IVR is the Server, so the destinations connect into the IVR over Ethernet. The connections can be
viewed in the Element Manager.
The far end initiates calls over the SR3511, so if a connection was down, it would need to route the
call over the other connection. This is not controlled by the IVR.
As per the requirements:
The OKEFORD shall provide two Ethernet ports for SR-3511 traffic. These ports shall be
separate from the OA&M interface.

The OKEFORD shall implement SR-3511 protocol.

The OKEFORD shall normally send responses to the CvAS on the same VC as the request was
received.

If the preferred VC is not operational, the response shall be sent to the same CP via the
alternate VC.

If the preferred CP is not contactable, the response shall be sent to another CP in the same
cluster. It is understood that the CvAS does not share USSD service context between CPs, so
it is possible that a response sent to another CP will be discarded. In this case, the OKEFORD
shall implement an inter-request timer. If this timer expires, the SR-3511 dialog is released at
the OKEFORD.

The status SR-3511 connection can be also verified in the EM, if any problem reported then you must
ensure the VCs are in service, if not then IP configuration should be checked, also if the IP is
reachable by ping and IP is active and accepting connections.



SR-3511 Dialogs

In order to invoke the USSD callback service, the CvAS must establish a dialog with the OKEFORD. On
receipt of a SendToResource message with ResourceType=StartIPDialogue and IPStayOnline=True,
the OKEFORD shall assign resources for the call and return SendToResourceResult indicating success.

The dialog is maintained until the OKEFORD sends a ResourceClear message (this may be as the
result of a termination request from the CvAS)

If resources cannot be assigned, the OKEFORD shall send SendToResourceResult indicating an error
and cause resourcesNotAvailable.

Successful Call with Announcement

CvAS OKEFORD
ExtendedInfoToResource
ExtendedIPOperation=PlayAppWithInfo
ApplicationID=101
TerminatingNumber=A
OriginatingNumber=B
RedirectingPartyID=C
GreetingAnnouncment=D
ExtendedInfoFromResource
ExtendedIPOperation=PlayAppWithInfo
ExtendedOperationStatus=Success
ApplicationID=101
CallLegID=1
MSC
IAM
CalledPartyNumber=A
CallingPartyNumber=B
RedirectingNumber=C
ACM
ANM
Play
Announcement
D





Element Manager

The status of E1s, links and CICs can be monitored in Element manager, all should be in service. The
failures could be due to layer 1 instability or links down/fluctuations, these could be check in EM to
verify that E1s and Links are stable and CICs are showing idle, there could be transmission issue that
can raise the problem.

USSD Calls will be routed to a specific Trunk Group so attention should be given to the status of the
trunks and circuits within the Trunk Group selected for outgoing calls.





Reporting a suspected Problem

If anything suspected to be wrong then it should be reported to Ericsson and logs provided before
any restart is done. Failure to do so could erase any chances of obtaining the root cause of any
outages.

Operating System Monitoring

The top command is an OS tool designed to provide data with regards to CPU and Memory usage. It
can be used to check if any process is utilising too much CPU resource. To output table can be sorted
by Memory or CPU use. The okeford process names all start with lininexe*.