|
mobileOriginatedCall |
A Mobile Originated Call item represents either tele or bearer service
usage originated by the mobile subscription.
In some cases the mobile itself may not be directly involved, e.g.
some call forwarding scenarios.
The Mobile Originated Call must contain the MO Basic Call Information,
Location Information and Basic Services Used.
Note: There must be only one
occurrence of the Basic Service Used group within this group even though the
physical syntax indicates that this may be a repeating group.
Where CAMEL services are supported and invoked then one occurrence of
CAMEL Service Used will be present for the invocation.
Where a supplementary service isused in conjunction with a call and
itis deemed necessary for transfer (see Annex A) then Supplementary Service
Code will be present . Third Party
Information may also be present.
Equipment Identifier will normally be transferred. The reason that it may not be present is
because the call did not originate from the equipment.
Operator Specific Information may also be present, this is optional
dependent on bilateral agreement.
Conditionality:
Mandatory within an
occurrence of group Call Event Details where none of the following are
present; Mobile Terminated Call,
Supplementary Service Event, Service Centre Usage, GPRS Call, Content
Transaction or Location Service .
|
Error Code |
Context |
Severity Level |
Validation Description |
|
30 31 32 35 |
MOC MOC MOC MOC |
Severe Severe Severe Severe |
Mandatory group MO Basic Call Information
missing within group. Mandatory group Location Information
missing within group. Mandatory group Basic Service Used
missing within group. More than one occurrence of group Basic
Service Used present within group. Note: Error codes 33 & 34 removed in TAP
release 3.11 (01 May 2005). |