https://ss7api.null.ro/index.php?feed=atom&namespace=0&title=Special%3ANewPages 2026-04-27T18:02:04Z From ss7api.null.ro MediaWiki 1.20.2 https://ss7api.null.ro/index.php/Cx/Dx 2022-03-10T13:47:39Z

<p>Oana: /* LocationInfo command */</p> <hr /> <div>== General ==<br /> <br /> This page shows as examples Diameter XMLs for the Cx/Dx interface&lt;br&gt;<br /> Application id: 16777216&lt;br&gt;<br /> Vendor id: 10415<br /> <br /> '''NOTES:''':<br /> * The examples below are not consistent with CSCF/HSS functionality. Their parameters are present here to be seen.<br /> * In the following examples a ''${str}'' means its value must be reflected from received message. E.g. ''${hhident}'' must be set from received message ''hhident'' parameter.&lt;br&gt;<br /> <br /> == UserAuthorization Command ==<br /> <br /> === Request ===<br /> <br /> General schema:<br /> <br /> &lt;UserAuthorizationRequest appid=&quot;16777216&quot; code=&quot;300&quot; shortName=&quot;UAR&quot; flags=&quot;request,proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationHost code=&quot;293&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationRealm code=&quot;283&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VisitedNetworkIdentifier vendor=&quot;10415&quot; code=&quot;600&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;UserAuthzType vendor=&quot;10415&quot; code=&quot;623&quot; format=&quot;enum&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=register 1=unregister 2=register-and-caps&lt;/dictionary&gt;<br /> &lt;/UserAuthzType&gt;<br /> &lt;UARFlags vendor=&quot;10415&quot; code=&quot;637&quot; format=&quot;flags32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary_bits&gt;0=emergency-register&lt;/dictionary_bits&gt;<br /> &lt;/UARFlags&gt;<br /> &lt;/UserAuthorizationRequest&gt;<br /> <br /> Example:<br /> <br /> &lt;UserAuthorizationRequest appid=&quot;16777216&quot; flags=&quot;request&quot;&gt;<br /> &lt;DestinationHost&gt;destination.ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;VisitedNetworkIdentifier vendor=&quot;10415&quot;&gt;6578616d706c652e636f6d&lt;/VisitedNetworkIdentifier&gt;<br /> &lt;UserAuthzType vendor=&quot;10415&quot;&gt;register&lt;/UserAuthzType&gt;<br /> &lt;UARFlags vendor=&quot;10415&quot;&gt;emergency-register&lt;/UARFlags&gt;<br /> &lt;/UserAuthorizationRequest&gt;<br /> <br /> === Answer ===<br /> <br /> General schema:<br /> <br /> &lt;UserAuthorizationAnswer appid=&quot;16777216&quot; code=&quot;300&quot; shortName=&quot;UAA&quot; flags=&quot;proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,need-result,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode code=&quot;268&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ExperimentalResult code=&quot;297&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ExperimentalResultCode code=&quot;298&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ServerCaps vendor=&quot;10415&quot; code=&quot;603&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;MandatoryCaps vendor=&quot;10415&quot; code=&quot;604&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;OptionalCaps vendor=&quot;10415&quot; code=&quot;605&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ServerCaps&gt;<br /> &lt;/UserAuthorizationAnswer&gt;<br /> <br /> Example:<br /> &lt;UserAuthorizationAnswer appid=&quot;16777216&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId flags=&quot;mandatory&quot;&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState flags=&quot;mandatory&quot;&gt;${session_state}&lt;/AuthSessionState&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;ServerCaps vendor=&quot;10415&quot;&gt;<br /> &lt;MandatoryCaps vendor=&quot;10415&quot;&gt;0&lt;/MandatoryCaps&gt;<br /> &lt;OptionalCaps vendor=&quot;10415&quot;&gt;0&lt;/OptionalCaps&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;/ServerCaps&gt;<br /> &lt;/UserAuthorizationAnswer&gt;<br /> <br /> <br /> == ServerAssignment Command ==<br /> <br /> === Request ===<br /> <br /> General schema:<br /> <br /> &lt;ServerAssignmentRequest appid=&quot;16777216&quot; code=&quot;301&quot; shortName=&quot;SAR&quot; flags=&quot;request,proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationHost code=&quot;293&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationRealm code=&quot;283&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;WildcardedPublicIdentity vendor=&quot;10415&quot; code=&quot;634&quot; format=&quot;str&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ServerAssignType vendor=&quot;10415&quot; code=&quot;614&quot; format=&quot;enum&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=none 1=register 2=re-register 3=unregistered-user 4=timeout-unregister 5=unregistered 6=timeout-unregister-store-server 7=unregistered-store-server 8=admin-unregister 9=noauth 10=auth-timeout 11=unregister-too-much-data 12=aaa-user-data-request 13=pgw-update 14=restoration&lt;/dictionary&gt;<br /> &lt;/ServerAssignType&gt;<br /> &lt;UserDataAlreadyAvailable vendor=&quot;10415&quot; code=&quot;624&quot; format=&quot;enum&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=no 1=yes&lt;/dictionary&gt;<br /> &lt;/UserDataAlreadyAvailable&gt;<br /> &lt;ScscfRestorationInfo vendor=&quot;10415&quot; code=&quot;639&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;RestorationInfo vendor=&quot;10415&quot; code=&quot;649&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Path vendor=&quot;10415&quot; code=&quot;640&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Contact vendor=&quot;10415&quot; code=&quot;641&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SubscriptionInfo vendor=&quot;10415&quot; code=&quot;642&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;CallIdSipHdr vendor=&quot;10415&quot; code=&quot;643&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FromSipHdr vendor=&quot;10415&quot; code=&quot;644&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ToSipHdr vendor=&quot;10415&quot; code=&quot;645&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;RecordRoute vendor=&quot;10415&quot; code=&quot;646&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Contact vendor=&quot;10415&quot; code=&quot;641&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SubscriptionInfo&gt;<br /> &lt;/RestorationInfo&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot; code=&quot;608&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/ScscfRestorationInfo&gt;<br /> &lt;MultipleReg vendor=&quot;10415&quot; code=&quot;648&quot; format=&quot;enum&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=no 1=yes&lt;/dictionary&gt;<br /> &lt;/MultipleReg&gt;<br /> &lt;SessionPriority vendor=&quot;10415&quot; code=&quot;650&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/ServerAssignmentRequest&gt;<br /> <br /> Example:<br /> &lt;ServerAssignmentRequest appid=&quot;16777216&quot; flags=&quot;request&quot;&gt;<br /> &lt;DestinationHost&gt;destination.ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;WildcardedPublicIdentity vendor=&quot;10415&quot;&gt;utf-8.string&lt;/WildcardedPublicIdentity&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;ServerAssignType vendor=&quot;10415&quot;&gt;register&lt;/ServerAssignType&gt;<br /> &lt;UserDataAlreadyAvailable vendor=&quot;10415&quot;&gt;true&lt;/UserDataAlreadyAvailable&gt;<br /> &lt;ScscfRestorationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;RestorationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;Path vendor=&quot;10415&quot;&gt;00554433aa&lt;/Path&gt;<br /> &lt;Contact vendor=&quot;10415&quot;&gt;00554433aa&lt;/Contact&gt;<br /> &lt;SubscriptionInfo vendor=&quot;10415&quot;&gt;<br /> &lt;CallIdSipHdr vendor=&quot;10415&quot;&gt;00554433aa&lt;/CallIdSipHdr&gt;<br /> &lt;FromSipHdr vendor=&quot;10415&quot;&gt;00554433aa&lt;/FromSipHdr&gt;<br /> &lt;ToSipHdr vendor=&quot;10415&quot;&gt;00554433aa&lt;/ToSipHdr&gt;<br /> &lt;RecordRoute vendor=&quot;10415&quot;&gt;00554433aa&lt;/RecordRoute&gt;<br /> &lt;Contact vendor=&quot;10415&quot;&gt;00554433aa&lt;/Contact&gt;<br /> &lt;/SubscriptionInfo&gt;<br /> &lt;/RestorationInfo&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot;&gt;utf-8.string&lt;/SipAuthScheme&gt;<br /> &lt;/ScscfRestorationInfo&gt;<br /> &lt;MultipleReg vendor=&quot;10415&quot;&gt;false&lt;/MultipleReg&gt;<br /> &lt;SessionPriority vendor=&quot;10415&quot;&gt;0&lt;/SessionPriority&gt;<br /> &lt;/ServerAssignmentRequest&gt;<br /> <br /> === Answer ===<br /> <br /> General schema:<br /> <br /> &lt;ServerAssignmentAnswer appid=&quot;16777216&quot; code=&quot;301&quot; shortName=&quot;SAA&quot; flags=&quot;proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,need-result,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode code=&quot;268&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ExperimentalResult code=&quot;297&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ExperimentalResultCode code=&quot;298&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;UserData vendor=&quot;10415&quot; code=&quot;606&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ChargingInfo vendor=&quot;10415&quot; code=&quot;618&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;PrimaryEventChargingFN vendor=&quot;10415&quot; code=&quot;619&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SecondaryEventChargingFN vendor=&quot;10415&quot; code=&quot;620&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;PrimaryChargingCollectionFN vendor=&quot;10415&quot; code=&quot;621&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SecondaryChargingCollectionFN vendor=&quot;10415&quot; code=&quot;622&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/ChargingInfo&gt;<br /> &lt;AssociatedIdentities vendor=&quot;10415&quot; code=&quot;632&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/AssociatedIdentities&gt;<br /> &lt;LooseRoute vendor=&quot;10415&quot; code=&quot;638&quot; format=&quot;enum&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=no 1=yes&lt;/dictionary&gt;<br /> &lt;/LooseRoute&gt;<br /> &lt;ScscfRestorationInfo vendor=&quot;10415&quot; code=&quot;639&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;RestorationInfo vendor=&quot;10415&quot; code=&quot;649&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Path vendor=&quot;10415&quot; code=&quot;640&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Contact vendor=&quot;10415&quot; code=&quot;641&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SubscriptionInfo vendor=&quot;10415&quot; code=&quot;642&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;CallIdSipHdr vendor=&quot;10415&quot; code=&quot;643&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FromSipHdr vendor=&quot;10415&quot; code=&quot;644&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ToSipHdr vendor=&quot;10415&quot; code=&quot;645&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;RecordRoute vendor=&quot;10415&quot; code=&quot;646&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Contact vendor=&quot;10415&quot; code=&quot;641&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SubscriptionInfo&gt;<br /> &lt;/RestorationInfo&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot; code=&quot;608&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/ScscfRestorationInfo&gt;<br /> &lt;AssociatedRegisteredIdentities vendor=&quot;10415&quot; code=&quot;647&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/AssociatedRegisteredIdentities&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;WildcardedPublicIdentity vendor=&quot;10415&quot; code=&quot;634&quot; format=&quot;str&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;PriviledgedSender vendor=&quot;10415&quot; code=&quot;652&quot; format=&quot;enum&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=no 1=yes&lt;/dictionary&gt;<br /> &lt;/PriviledgedSender&gt;<br /> &lt;/ServerAssignmentAnswer&gt;<br /> <br /> Example:<br /> &lt;ServerAssignmentAnswer appid=&quot;16777216&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId flags=&quot;mandatory&quot;&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState flags=&quot;mandatory&quot;&gt;${session_state}&lt;/AuthSessionState&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;UserData vendor=&quot;10415&quot;&gt;&lt;IMSSubscription/&gt;&lt;/UserData&gt;<br /> &lt;ChargingInfo vendor=&quot;10415&quot;&gt;<br /> &lt;PrimaryEventChargingFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/PrimaryEventChargingFN&gt;<br /> &lt;SecondaryEventChargingFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/SecondaryEventChargingFN&gt;<br /> &lt;PrimaryChargingCollectionFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/PrimaryChargingCollectionFN&gt;<br /> &lt;SecondaryChargingCollectionFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/SecondaryChargingCollectionFN&gt;<br /> &lt;/ChargingInfo&gt;<br /> &lt;AssociatedIdentities vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;/AssociatedIdentities&gt;<br /> &lt;LooseRoute vendor=&quot;10415&quot;&gt;true&lt;/LooseRoute&gt;<br /> &lt;ScscfRestorationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;RestorationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;Path vendor=&quot;10415&quot;&gt;00554433aa&lt;/Path&gt;<br /> &lt;Contact vendor=&quot;10415&quot;&gt;00554433aa&lt;/Contact&gt;<br /> &lt;SubscriptionInfo vendor=&quot;10415&quot;&gt;<br /> &lt;CallIdSipHdr vendor=&quot;10415&quot;&gt;00554433aa&lt;/CallIdSipHdr&gt;<br /> &lt;FromSipHdr vendor=&quot;10415&quot;&gt;00554433aa&lt;/FromSipHdr&gt;<br /> &lt;ToSipHdr vendor=&quot;10415&quot;&gt;00554433aa&lt;/ToSipHdr&gt;<br /> &lt;RecordRoute vendor=&quot;10415&quot;&gt;00554433aa&lt;/RecordRoute&gt;<br /> &lt;Contact vendor=&quot;10415&quot;&gt;00554433aa&lt;/Contact&gt;<br /> &lt;/SubscriptionInfo&gt;<br /> &lt;/RestorationInfo&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot;&gt;utf-8.string&lt;/SipAuthScheme&gt;<br /> &lt;/ScscfRestorationInfo&gt;<br /> &lt;AssociatedRegisteredIdentities vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;/AssociatedRegisteredIdentities&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;WildcardedPublicIdentity vendor=&quot;10415&quot;&gt;utf-8.string&lt;/WildcardedPublicIdentity&gt;<br /> &lt;PriviledgedSender vendor=&quot;10415&quot;&gt;true&lt;/PriviledgedSender&gt;<br /> &lt;/ServerAssignmentAnswer&gt;<br /> <br /> == LocationInfo Command ==<br /> <br /> === Request ===<br /> <br /> General schema:<br /> <br /> &lt;LocationInfoRequest appid=&quot;16777216&quot; code=&quot;302&quot; shortName=&quot;LIR&quot; flags=&quot;request,proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationHost code=&quot;293&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationRealm code=&quot;283&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginatingRequest vendor=&quot;10415&quot; code=&quot;633&quot; format=&quot;enum&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;UserAuthzType vendor=&quot;10415&quot; code=&quot;623&quot; format=&quot;enum&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=register 1=unregister 2=register-and-caps&lt;/dictionary&gt;<br /> &lt;/UserAuthzType&gt;<br /> &lt;SessionPriority vendor=&quot;10415&quot; code=&quot;650&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/LocationInfoRequest&gt;<br /> <br /> Example:<br /> <br /> &lt;LocationInfoRequest appid=&quot;16777216&quot; flags=&quot;request&quot;&gt;<br /> &lt;DestinationHost&gt;destination.ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationRealm&gt;<br /> &lt;OriginatingRequest vendor=&quot;10415&quot;&gt;0&lt;/OriginatingRequest&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;UserAuthzType vendor=&quot;10415&quot;&gt;unregister&lt;/UserAuthzType&gt;<br /> &lt;SessionPriority vendor=&quot;10415&quot;&gt;0&lt;/SessionPriority&gt;<br /> &lt;/LocationInfoRequest&gt;<br /> <br /> === Answer ===<br /> <br /> General schema:<br /> <br /> &lt;LocationInfoAnswer appid=&quot;16777216&quot; code=&quot;302&quot; shortName=&quot;LIA&quot; flags=&quot;proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,need-result,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode code=&quot;268&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ExperimentalResult code=&quot;297&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ExperimentalResultCode code=&quot;298&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ServerCaps vendor=&quot;10415&quot; code=&quot;603&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;MandatoryCaps vendor=&quot;10415&quot; code=&quot;604&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;OptionalCaps vendor=&quot;10415&quot; code=&quot;605&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ServerCaps&gt;<br /> &lt;WildcardedPublicIdentity vendor=&quot;10415&quot; code=&quot;634&quot; format=&quot;str&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;LIAFlags vendor=&quot;10415&quot; code=&quot;653&quot; format=&quot;flags32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary_bits&gt;0=psi-direct-routing&lt;/dictionary_bits&gt;<br /> &lt;/LIAFlags&gt;<br /> &lt;/LocationInfoAnswer&gt;<br /> <br /> <br /> Example:<br /> <br /> &lt;LocationInfoAnswer appid=&quot;16777216&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId flags=&quot;mandatory&quot;&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState flags=&quot;mandatory&quot;&gt;${session_state}&lt;/AuthSessionState&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;ServerCaps vendor=&quot;10415&quot;&gt;<br /> &lt;MandatoryCaps vendor=&quot;10415&quot;&gt;0&lt;/MandatoryCaps&gt;<br /> &lt;OptionalCaps vendor=&quot;10415&quot;&gt;0&lt;/OptionalCaps&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;/ServerCaps&gt;<br /> &lt;WildcardedPublicIdentity vendor=&quot;10415&quot;&gt;utf-8.string&lt;/WildcardedPublicIdentity&gt;<br /> &lt;LIAFlags vendor=&quot;10415&quot;&gt;psi-direct-routing&lt;/LIAFlags&gt;<br /> &lt;/LocationInfoAnswer&gt;<br /> <br /> == MultimediaAuth Command ==<br /> <br /> === Request ===<br /> <br /> General schema:<br /> <br /> &lt;MultimediaAuthRequest appid=&quot;16777216&quot; code=&quot;303&quot; shortName=&quot;MAR&quot; flags=&quot;request,proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationHost code=&quot;293&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationRealm code=&quot;283&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthDataItem vendor=&quot;10415&quot; code=&quot;612&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SipItemNumber vendor=&quot;10415&quot; code=&quot;613&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot; code=&quot;608&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthenticate vendor=&quot;10415&quot; code=&quot;609&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthorization vendor=&quot;10415&quot; code=&quot;610&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthContext vendor=&quot;10415&quot; code=&quot;611&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot; code=&quot;625&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot; code=&quot;626&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipDigestAuthenticate vendor=&quot;10415&quot; code=&quot;635&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;DigestRealm code=&quot;104&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestAlgorithm code=&quot;111&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestQop code=&quot;110&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestHA1 code=&quot;121&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SipDigestAuthenticate&gt;<br /> &lt;FramedIpAddr code=&quot;8&quot; format=&quot;ipv4&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FramedIPv6Prefix code=&quot;97&quot; format=&quot;raw&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FramedIfaceId code=&quot;96&quot; format=&quot;uint64&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;LineIdentifier vendor=&quot;13019&quot; code=&quot;500&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/SipAuthDataItem&gt;<br /> &lt;SipNumberAuthItems vendor=&quot;10415&quot; code=&quot;607&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ServerName vendor=&quot;10415&quot; code=&quot;602&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/MultimediaAuthRequest&gt;<br /> <br /> Example:<br /> <br /> &lt;MultimediaAuthRequest appid=&quot;16777216&quot; flags=&quot;request&quot;&gt;<br /> &lt;DestinationHost&gt;destination.ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;SipAuthDataItem vendor=&quot;10415&quot;&gt;<br /> &lt;SipItemNumber vendor=&quot;10415&quot;&gt;0&lt;/SipItemNumber&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot;&gt;utf-8.string&lt;/SipAuthScheme&gt;<br /> &lt;SipAuthenticate vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthenticate&gt;<br /> &lt;SipAuthorization vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthorization&gt;<br /> &lt;SipAuthContext vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthContext&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot;&gt;00554433aa&lt;/ConfidentialityKey&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot;&gt;00554433aa&lt;/IntegrityKey&gt;<br /> &lt;SipDigestAuthenticate vendor=&quot;10415&quot;&gt;<br /> &lt;DigestRealm&gt;utf-8.string&lt;/DigestRealm&gt;<br /> &lt;DigestAlgorithm&gt;utf-8.string&lt;/DigestAlgorithm&gt;<br /> &lt;DigestQop&gt;utf-8.string&lt;/DigestQop&gt;<br /> &lt;DigestHA1&gt;utf-8.string&lt;/DigestHA1&gt;<br /> &lt;/SipDigestAuthenticate&gt;<br /> &lt;FramedIpAddr&gt;1.2.3.4&lt;/FramedIpAddr&gt;<br /> &lt;FramedIPv6Prefix&gt;1122554433aa22&lt;/FramedIPv6Prefix&gt;<br /> &lt;FramedIfaceId&gt;0&lt;/FramedIfaceId&gt;<br /> &lt;LineIdentifier vendor=&quot;13019&quot;&gt;00554433aa&lt;/LineIdentifier&gt;<br /> &lt;/SipAuthDataItem&gt;<br /> &lt;SipNumberAuthItems vendor=&quot;10415&quot;&gt;0&lt;/SipNumberAuthItems&gt;<br /> &lt;ServerName vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ServerName&gt;<br /> &lt;/MultimediaAuthRequest&gt;<br /> <br /> === Answer ===<br /> <br /> General schema:<br /> <br /> &lt;MultimediaAuthAnswer appid=&quot;16777216&quot; code=&quot;303&quot; shortName=&quot;MAA&quot; flags=&quot;proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,need-result,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode code=&quot;268&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ExperimentalResult code=&quot;297&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ExperimentalResultCode code=&quot;298&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipNumberAuthItems vendor=&quot;10415&quot; code=&quot;607&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthDataItem vendor=&quot;10415&quot; code=&quot;612&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SipItemNumber vendor=&quot;10415&quot; code=&quot;613&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot; code=&quot;608&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthenticate vendor=&quot;10415&quot; code=&quot;609&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthorization vendor=&quot;10415&quot; code=&quot;610&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthContext vendor=&quot;10415&quot; code=&quot;611&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot; code=&quot;625&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot; code=&quot;626&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipDigestAuthenticate vendor=&quot;10415&quot; code=&quot;635&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;DigestRealm code=&quot;104&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestAlgorithm code=&quot;111&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestQop code=&quot;110&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestHA1 code=&quot;121&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SipDigestAuthenticate&gt;<br /> &lt;FramedIpAddr code=&quot;8&quot; format=&quot;ipv4&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FramedIPv6Prefix code=&quot;97&quot; format=&quot;raw&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FramedIfaceId code=&quot;96&quot; format=&quot;uint64&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;LineIdentifier vendor=&quot;13019&quot; code=&quot;500&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/SipAuthDataItem&gt;<br /> &lt;/MultimediaAuthAnswer&gt;<br /> <br /> Example:<br /> <br /> &lt;MultimediaAuthAnswer appid=&quot;16777216&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId flags=&quot;mandatory&quot;&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState flags=&quot;mandatory&quot;&gt;${session_state}&lt;/AuthSessionState&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;SipNumberAuthItems vendor=&quot;10415&quot;&gt;0&lt;/SipNumberAuthItems&gt;<br /> &lt;SipAuthDataItem vendor=&quot;10415&quot;&gt;<br /> &lt;SipItemNumber vendor=&quot;10415&quot;&gt;0&lt;/SipItemNumber&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot;&gt;utf-8.string&lt;/SipAuthScheme&gt;<br /> &lt;SipAuthenticate vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthenticate&gt;<br /> &lt;SipAuthorization vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthorization&gt;<br /> &lt;SipAuthContext vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthContext&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot;&gt;00554433aa&lt;/ConfidentialityKey&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot;&gt;00554433aa&lt;/IntegrityKey&gt;<br /> &lt;SipDigestAuthenticate vendor=&quot;10415&quot;&gt;<br /> &lt;DigestRealm&gt;utf-8.string&lt;/DigestRealm&gt;<br /> &lt;DigestAlgorithm&gt;utf-8.string&lt;/DigestAlgorithm&gt;<br /> &lt;DigestQop&gt;utf-8.string&lt;/DigestQop&gt;<br /> &lt;DigestHA1&gt;utf-8.string&lt;/DigestHA1&gt;<br /> &lt;/SipDigestAuthenticate&gt;<br /> &lt;FramedIpAddr&gt;1.2.3.4&lt;/FramedIpAddr&gt;<br /> &lt;FramedIPv6Prefix&gt;1122554433aa22&lt;/FramedIPv6Prefix&gt;<br /> &lt;FramedIfaceId&gt;0&lt;/FramedIfaceId&gt;<br /> &lt;LineIdentifier vendor=&quot;13019&quot;&gt;00554433aa&lt;/LineIdentifier&gt;<br /> &lt;/SipAuthDataItem&gt;<br /> &lt;/MultimediaAuthAnswer&gt;<br /> <br /> <br /> == RegistrationTermination Command ==<br /> <br /> === Request ===<br /> <br /> General schema:<br /> &lt;RegistrationTerminationRequest appid=&quot;16777216&quot; code=&quot;304&quot; shortName=&quot;RTR&quot; flags=&quot;request,proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationHost code=&quot;293&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationRealm code=&quot;283&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AssociatedIdentities vendor=&quot;10415&quot; code=&quot;632&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/AssociatedIdentities&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;DeregistrationReason vendor=&quot;10415&quot; code=&quot;615&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;ReasonCode vendor=&quot;10415&quot; code=&quot;616&quot; format=&quot;enum&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;&gt;<br /> &lt;dictionary&gt;0=permanent 1=new-server-assigned 2=server-change 3=remove-s-cscf&lt;/dictionary&gt;<br /> &lt;/ReasonCode&gt;<br /> &lt;ReasonInfo vendor=&quot;10415&quot; code=&quot;617&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/DeregistrationReason&gt;<br /> &lt;/RegistrationTerminationRequest&gt;<br /> <br /> Example:<br /> <br /> &lt;RegistrationTerminationRequest appid=&quot;16777216&quot; flags=&quot;request&quot;&gt;<br /> &lt;DestinationHost&gt;destination.ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;AssociatedIdentities vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;/AssociatedIdentities&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;DeregistrationReason vendor=&quot;10415&quot;&gt;<br /> &lt;ReasonCode vendor=&quot;10415&quot;&gt;server-change&lt;/ReasonCode&gt;<br /> &lt;ReasonInfo vendor=&quot;10415&quot;&gt;utf-8.string&lt;/ReasonInfo&gt;<br /> &lt;/DeregistrationReason&gt;<br /> &lt;/RegistrationTerminationRequest&gt;<br /> <br /> === Answer ===<br /> <br /> General schema: <br /> <br /> &lt;RegistrationTerminationAnswer appid=&quot;16777216&quot; code=&quot;304&quot; shortName=&quot;RTA&quot; flags=&quot;proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,need-result,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode code=&quot;268&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ExperimentalResult code=&quot;297&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ExperimentalResultCode code=&quot;298&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AssociatedIdentities vendor=&quot;10415&quot; code=&quot;632&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/AssociatedIdentities&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;IdentityWithEmergencyReg vendor=&quot;10415&quot; code=&quot;651&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot; code=&quot;601&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/IdentityWithEmergencyReg&gt;<br /> &lt;/RegistrationTerminationAnswer&gt;<br /> <br /> Example:<br /> <br /> &lt;RegistrationTerminationAnswer appid=&quot;16777216&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId flags=&quot;mandatory&quot;&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState flags=&quot;mandatory&quot;&gt;${session_state}&lt;/AuthSessionState&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;AssociatedIdentities vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;/AssociatedIdentities&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;IdentityWithEmergencyReg vendor=&quot;10415&quot;&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;PublicIdentity vendor=&quot;10415&quot;&gt;tel:+882800001&lt;/PublicIdentity&gt;<br /> &lt;/IdentityWithEmergencyReg&gt;<br /> &lt;/RegistrationTerminationAnswer&gt;<br /> <br /> <br /> == PushProfile Command ==<br /> <br /> === Request ===<br /> <br /> General schema:<br /> <br /> &lt;PushProfileRequest appid=&quot;16777216&quot; code=&quot;305&quot; shortName=&quot;PPR&quot; flags=&quot;request,proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationHost code=&quot;293&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DestinationRealm code=&quot;283&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;Username code=&quot;1&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;UserData vendor=&quot;10415&quot; code=&quot;606&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ChargingInfo vendor=&quot;10415&quot; code=&quot;618&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;PrimaryEventChargingFN vendor=&quot;10415&quot; code=&quot;619&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SecondaryEventChargingFN vendor=&quot;10415&quot; code=&quot;620&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;PrimaryChargingCollectionFN vendor=&quot;10415&quot; code=&quot;621&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SecondaryChargingCollectionFN vendor=&quot;10415&quot; code=&quot;622&quot; format=&quot;diamuri&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/ChargingInfo&gt;<br /> &lt;SipAuthDataItem vendor=&quot;10415&quot; code=&quot;612&quot; format=&quot;grouped&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SipItemNumber vendor=&quot;10415&quot; code=&quot;613&quot; format=&quot;uint32&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot; code=&quot;608&quot; format=&quot;str&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthenticate vendor=&quot;10415&quot; code=&quot;609&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthorization vendor=&quot;10415&quot; code=&quot;610&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipAuthContext vendor=&quot;10415&quot; code=&quot;611&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot; code=&quot;625&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot; code=&quot;626&quot; format=&quot;raw&quot; flags_must=&quot;vendor,mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SipDigestAuthenticate vendor=&quot;10415&quot; code=&quot;635&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;DigestRealm code=&quot;104&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestAlgorithm code=&quot;111&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestQop code=&quot;110&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;DigestHA1 code=&quot;121&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SipDigestAuthenticate&gt;<br /> &lt;FramedIpAddr code=&quot;8&quot; format=&quot;ipv4&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FramedIPv6Prefix code=&quot;97&quot; format=&quot;raw&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FramedIfaceId code=&quot;96&quot; format=&quot;uint64&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;LineIdentifier vendor=&quot;13019&quot; code=&quot;500&quot; format=&quot;raw&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/SipAuthDataItem&gt;<br /> &lt;/PushProfileRequest&gt;<br /> <br /> <br /> Example:<br /> <br /> &lt;PushProfileRequest appid=&quot;16777216&quot; flags=&quot;request&quot;&gt;<br /> &lt;DestinationHost&gt;destination.ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;ims.mnc001.mcc001.3gppnetwork.org&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;0010100000000001@ims.mnc001.mcc001.3gppnetwork.org&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;UserData vendor=&quot;10415&quot;&gt;&lt;IMSSubscription/&gt;&lt;/UserData&gt;<br /> &lt;ChargingInfo vendor=&quot;10415&quot;&gt;<br /> &lt;PrimaryEventChargingFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/PrimaryEventChargingFN&gt;<br /> &lt;SecondaryEventChargingFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/SecondaryEventChargingFN&gt;<br /> &lt;PrimaryChargingCollectionFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/PrimaryChargingCollectionFN&gt;<br /> &lt;SecondaryChargingCollectionFN vendor=&quot;10415&quot;&gt;aaa://host.example.com;transport=tcp&lt;/SecondaryChargingCollectionFN&gt;<br /> &lt;/ChargingInfo&gt;<br /> &lt;SipAuthDataItem vendor=&quot;10415&quot;&gt;<br /> &lt;SipItemNumber vendor=&quot;10415&quot;&gt;0&lt;/SipItemNumber&gt;<br /> &lt;SipAuthScheme vendor=&quot;10415&quot;&gt;utf-8.string&lt;/SipAuthScheme&gt;<br /> &lt;SipAuthenticate vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthenticate&gt;<br /> &lt;SipAuthorization vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthorization&gt;<br /> &lt;SipAuthContext vendor=&quot;10415&quot;&gt;00554433aa&lt;/SipAuthContext&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot;&gt;00554433aa&lt;/ConfidentialityKey&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot;&gt;00554433aa&lt;/IntegrityKey&gt;<br /> &lt;SipDigestAuthenticate vendor=&quot;10415&quot;&gt;<br /> &lt;DigestRealm&gt;utf-8.string&lt;/DigestRealm&gt;<br /> &lt;DigestAlgorithm&gt;utf-8.string&lt;/DigestAlgorithm&gt;<br /> &lt;DigestQop&gt;utf-8.string&lt;/DigestQop&gt;<br /> &lt;DigestHA1&gt;utf-8.string&lt;/DigestHA1&gt;<br /> &lt;/SipDigestAuthenticate&gt;<br /> &lt;FramedIpAddr&gt;1.2.3.4&lt;/FramedIpAddr&gt;<br /> &lt;FramedIPv6Prefix&gt;1122554433aa22&lt;/FramedIPv6Prefix&gt;<br /> &lt;FramedIfaceId&gt;0&lt;/FramedIfaceId&gt;<br /> &lt;LineIdentifier vendor=&quot;13019&quot;&gt;00554433aa&lt;/LineIdentifier&gt;<br /> &lt;/SipAuthDataItem&gt;<br /> &lt;/PushProfileRequest&gt;<br /> <br /> === Answer ===<br /> <br /> General schema:<br /> <br /> &lt;PushProfileAnswer appid=&quot;16777216&quot; code=&quot;305&quot; shortName=&quot;PPA&quot; flags=&quot;proxiable&quot; internal_flags=&quot;add-session-id,no-session-state,need-result,auth-app&quot; vendor=&quot;10415&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;SessionId code=&quot;263&quot; format=&quot;str&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;fixed,required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;VendorSpecificApplicationId code=&quot;260&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;AcctApplicationId code=&quot;259&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;AuthApplicationId code=&quot;258&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode code=&quot;268&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;ExperimentalResult code=&quot;297&quot; format=&quot;grouped&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;1&quot; have_unk_avps=&quot;false&quot;&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;ExperimentalResultCode code=&quot;298&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;4294967295&quot;/&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;AuthSessionState code=&quot;277&quot; format=&quot;enum&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginHost code=&quot;264&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;OriginRealm code=&quot;296&quot; format=&quot;diamident&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot; code=&quot;628&quot; format=&quot;grouped&quot; flags_must=&quot;vendor&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;4294967295&quot; have_unk_avps=&quot;true&quot;&gt;<br /> &lt;dictionary_bits&gt;<br /> &lt;list_id_1&gt;0=sifc 1=alias 2=ims-restoration&lt;/list_id_1&gt;<br /> &lt;/dictionary_bits&gt;<br /> &lt;VendorId code=&quot;266&quot; format=&quot;uint32&quot; flags_must=&quot;mandatory&quot; flags_must_not=&quot;vendor&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureListId vendor=&quot;10415&quot; code=&quot;629&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;FeatureList vendor=&quot;10415&quot; code=&quot;630&quot; format=&quot;uint32&quot; flags_must=&quot;vendor&quot; flags_must_not=&quot;mandatory&quot; occurence=&quot;required&quot; minOccurs=&quot;1&quot; maxOccurs=&quot;1&quot;/&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;/PushProfileAnswer&gt;<br /> <br /> Example:<br /> <br /> &lt;PushProfileAnswer appid=&quot;16777216&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId flags=&quot;mandatory&quot;&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState flags=&quot;mandatory&quot;&gt;${session_state}&lt;/AuthSessionState&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;sifc,alias,ims-restoration&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;/PushProfileAnswer&gt;</div>

Oana https://ss7api.null.ro/index.php/S6a/Sad 2016-09-09T14:44:08Z

<p>Oana: Created page with &quot;== General == This page shows as examples Diameter XMLs for the S6a/S6d interface (3GPP MME/SGSN to HSS interface)&lt;br&gt; Application id: 16777251&lt;br&gt; Vendor id: 10415 '''NOTES...&quot;</p> <hr /> <div>== General ==<br /> <br /> This page shows as examples Diameter XMLs for the S6a/S6d interface (3GPP MME/SGSN to HSS interface)&lt;br&gt;<br /> Application id: 16777251&lt;br&gt;<br /> Vendor id: 10415<br /> <br /> '''NOTES:''':<br /> * The examples below are not consistent with MME/SGSN/HSS functionality. Their parameters are present here to be seen.<br /> * In the following examples a ''${str}'' means its value must be reflected from received message. E.g. ''${hhident}'' must be set from received message ''hhident'' parameter.&lt;br&gt;<br /> <br /> == Update Location Command ==<br /> <br /> Direction: MME/SGSN -&gt; HSS&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;UpdateLocationRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;1&quot;&gt;0x03&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;2&quot;&gt;sms-in-mme&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;TerminalInfo vendor=&quot;10415&quot;&gt;<br /> &lt;IMEI vendor=&quot;10415&quot;&gt;1234567890&lt;/IMEI&gt;<br /> &lt;/TerminalInfo&gt;<br /> &lt;RATType vendor=&quot;10415&quot;&gt;e-utran&lt;/RATType&gt;<br /> &lt;ULRFlags vendor=&quot;10415&quot;&gt;s6a&lt;/ULRFlags&gt;<br /> &lt;UESRVCCCapability vendor=&quot;10415&quot;&gt;yes&lt;/UESRVCCCapability&gt;<br /> &lt;VisitedPlmnId vendor=&quot;10415&quot;&gt;040100&lt;/VisitedPlmnId&gt;<br /> &lt;SgsnNumber vendor=&quot;10415&quot;&gt;123&lt;/SgsnNumber&gt;<br /> &lt;HSoIMSVOPSS vendor=&quot;10415&quot;&gt;yes&lt;/HSoIMSVOPSS&gt;<br /> &lt;GMLCAddress vendor=&quot;10415&quot;&gt;192.168.168.12&lt;/GMLCAddress&gt;<br /> &lt;ActiveAPN vendor=&quot;10415&quot;&gt;<br /> &lt;MIP6AgentInfo&gt;<br /> &lt;MIPHomeAgentAddress&gt;fe80::2&lt;/MIPHomeAgentAddress&gt;<br /> &lt;MIP6HomeLinkPrefix&gt;001122&lt;/MIP6HomeLinkPrefix&gt;<br /> &lt;/MIP6AgentInfo&gt;<br /> &lt;ContextIdentifier vendor=&quot;10415&quot;&gt;100&lt;/ContextIdentifier&gt;<br /> &lt;ServiceSelection&gt;*&lt;/ServiceSelection&gt;<br /> &lt;VisitedNetworkIdentifier vendor=&quot;10415&quot;&gt;998877&lt;/VisitedNetworkIdentifier&gt;<br /> &lt;SpecificAPNInfo vendor=&quot;10415&quot;&gt;<br /> &lt;MIP6AgentInfo&gt;<br /> &lt;MIPHomeAgentAddress&gt;fe80::2&lt;/MIPHomeAgentAddress&gt;<br /> &lt;MIP6HomeLinkPrefix&gt;001122&lt;/MIP6HomeLinkPrefix&gt;<br /> &lt;/MIP6AgentInfo&gt;<br /> &lt;ServiceSelection&gt;*&lt;/ServiceSelection&gt;<br /> &lt;VisitedNetworkIdentifier vendor=&quot;10415&quot;&gt;001122&lt;/VisitedNetworkIdentifier&gt;<br /> &lt;/SpecificAPNInfo&gt;<br /> &lt;/ActiveAPN&gt;<br /> &lt;EquivalentPlmnList vendor=&quot;10415&quot;&gt;<br /> &lt;VisitedPlmnId vendor=&quot;10415&quot;&gt;004001&lt;/VisitedPlmnId&gt;<br /> &lt;VisitedPlmnId vendor=&quot;10415&quot;&gt;004002&lt;/VisitedPlmnId&gt;<br /> &lt;/EquivalentPlmnList&gt;<br /> &lt;MmeNumberForMTSms vendor=&quot;10415&quot;&gt;1000&lt;/MmeNumberForMTSms&gt;<br /> &lt;SMSRegisterRequest vendor=&quot;10415&quot;&gt;no-preferrence&lt;/SMSRegisterRequest&gt;<br /> &lt;/UpdateLocationRequest&gt;<br /> <br /> Answer, success:<br /> <br /> &lt;UpdateLocationAnswer appid=&quot;${appid}&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;ULAFlags vendor=&quot;10415&quot;&gt;mme-reg-mt-sms,64&lt;/ULAFlags&gt;<br /> &lt;ErrorDiagnostic vendor=&quot;10415&quot;&gt;odb-all-apn&lt;/ErrorDiagnostic&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;1&quot;&gt;boic,baoc,regsub&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;SubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;SubscriberStatus vendor=&quot;10415&quot;&gt;serviceGranted&lt;/SubscriberStatus&gt;<br /> &lt;MSISDN vendor=&quot;10415&quot;&gt;40700100100&lt;/MSISDN&gt;<br /> &lt;AMSISDN vendor=&quot;10415&quot;&gt;40700100101&lt;/AMSISDN&gt;<br /> &lt;STNSR vendor=&quot;10415&quot;&gt;40700100102&lt;/STNSR&gt;<br /> &lt;ICSIndicator vendor=&quot;10415&quot;&gt;yes&lt;/ICSIndicator&gt;<br /> &lt;NetworkAccessMode vendor=&quot;10415&quot;&gt;only-packet&lt;/NetworkAccessMode&gt;<br /> &lt;OperatorDeterminedBarring vendor=&quot;10415&quot;&gt;odb-all-apn,odb-intrn-og&lt;/OperatorDeterminedBarring&gt;<br /> &lt;HPlmnODB vendor=&quot;10415&quot;&gt;type1,type3&lt;/HPlmnODB&gt;<br /> &lt;RegionalSubscriptionZoneCode vendor=&quot;10415&quot;&gt;1122330101&lt;/RegionalSubscriptionZoneCode&gt;<br /> &lt;RegionalSubscriptionZoneCode vendor=&quot;10415&quot;&gt;1122330102&lt;/RegionalSubscriptionZoneCode&gt;<br /> &lt;AccessRestrictionData vendor=&quot;10415&quot;&gt;geran,gan,i-hspa-evolution,ho-to-non-3gpp&lt;/AccessRestrictionData&gt;<br /> &lt;APNOIReplacement vendor=&quot;10415&quot;&gt;apn.example.com&lt;/APNOIReplacement&gt;<br /> &lt;LCSInfo vendor=&quot;10415&quot;&gt;<br /> &lt;GMLCNumber vendor=&quot;10415&quot;&gt;40700100000&lt;/GMLCNumber&gt;<br /> &lt;GMLCNumber vendor=&quot;10415&quot;&gt;40700100001&lt;/GMLCNumber&gt;<br /> &lt;LCSPrivacyException vendor=&quot;10415&quot;&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allLineIdentificationSS&lt;/SSCode&gt;<br /> &lt;SSStatus vendor=&quot;10415&quot;&gt;active,registered&lt;/SSStatus&gt;<br /> &lt;NotificationToUEUser vendor=&quot;10415&quot;&gt;locationNotAllowed&lt;/NotificationToUEUser&gt;<br /> &lt;ExternalClient vendor=&quot;10415&quot;&gt;<br /> &lt;ClientIdentity vendor=&quot;10415&quot;&gt;40700200000&lt;/ClientIdentity&gt;<br /> &lt;GMLCRestriction vendor=&quot;10415&quot;&gt;home-Country&lt;/GMLCRestriction&gt;<br /> &lt;NotificationToUEUser vendor=&quot;10415&quot;&gt;notifyLocationAllowed&lt;/NotificationToUEUser&gt;<br /> &lt;/ExternalClient&gt;<br /> &lt;ExternalClient vendor=&quot;10415&quot;&gt;<br /> &lt;ClientIdentity vendor=&quot;10415&quot;&gt;40700300000&lt;/ClientIdentity&gt;<br /> &lt;/ExternalClient&gt;<br /> &lt;PlmnClient vendor=&quot;10415&quot;&gt;anonymousLocation&lt;/PlmnClient&gt;<br /> &lt;ServiceType vendor=&quot;10415&quot;&gt;<br /> &lt;ServiceTypeIdentity vendor=&quot;10415&quot;&gt;3&lt;/ServiceTypeIdentity&gt;<br /> &lt;GMLCRestriction vendor=&quot;10415&quot;&gt;home-Country&lt;/GMLCRestriction&gt;<br /> &lt;NotificationToUEUser vendor=&quot;10415&quot;&gt;notifyLocationAllowed&lt;/NotificationToUEUser&gt;<br /> &lt;/ServiceType&gt;<br /> &lt;ServiceType vendor=&quot;10415&quot;&gt;<br /> &lt;ServiceTypeIdentity vendor=&quot;10415&quot;&gt;4&lt;/ServiceTypeIdentity&gt;<br /> &lt;/ServiceType&gt;<br /> &lt;/LCSPrivacyException&gt;<br /> &lt;LCSPrivacyException vendor=&quot;10415&quot;&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allCallOfferingSS&lt;/SSCode&gt;<br /> &lt;SSStatus vendor=&quot;10415&quot;&gt;active,provisioned&lt;/SSStatus&gt;<br /> &lt;PlmnClient vendor=&quot;10415&quot;&gt;broadcastService&lt;/PlmnClient&gt;<br /> &lt;/LCSPrivacyException&gt;<br /> &lt;MOLR vendor=&quot;10415&quot;&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allLineIdentificationSS&lt;/SSCode&gt;<br /> &lt;SSStatus vendor=&quot;10415&quot;&gt;active,registered&lt;/SSStatus&gt;<br /> &lt;/MOLR&gt;<br /> &lt;/LCSInfo&gt;<br /> &lt;TeleserviceList vendor=&quot;10415&quot;&gt;<br /> &lt;TSCode vendor=&quot;10415&quot;&gt;allDataTeleservices&lt;/TSCode&gt;<br /> &lt;TSCode vendor=&quot;10415&quot;&gt;allSpeechTransmissionServices&lt;/TSCode&gt;<br /> &lt;TSCode vendor=&quot;10415&quot;&gt;voiceGroupCall&lt;/TSCode&gt;<br /> &lt;/TeleserviceList&gt;<br /> &lt;CallBarringInfo vendor=&quot;10415&quot;&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allLineIdentificationSS&lt;/SSCode&gt;<br /> &lt;SSStatus vendor=&quot;10415&quot;&gt;active,registered&lt;/SSStatus&gt;<br /> &lt;/CallBarringInfo&gt;<br /> &lt;CallBarringInfo vendor=&quot;10415&quot;&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allForwardingSS&lt;/SSCode&gt;<br /> &lt;SSStatus vendor=&quot;10415&quot;&gt;registered&lt;/SSStatus&gt;<br /> &lt;/CallBarringInfo&gt;<br /> &lt;ChargingCharacteristics vendor=&quot;10415&quot;&gt;xbcd&lt;/ChargingCharacteristics&gt;<br /> &lt;AMBR vendor=&quot;10415&quot;&gt;<br /> &lt;MaxRequestedBandwithUL vendor=&quot;10415&quot;&gt;20000&lt;/MaxRequestedBandwithUL&gt;<br /> &lt;MaxRequestedBandwithDL vendor=&quot;10415&quot;&gt;19000&lt;/MaxRequestedBandwithDL&gt;<br /> &lt;/AMBR&gt;<br /> &lt;APNConfigurationProfile vendor=&quot;10415&quot;&gt;<br /> &lt;ContextIdentifier vendor=&quot;10415&quot;&gt;1&lt;/ContextIdentifier&gt;<br /> &lt;AllAPNConfigIncluded vendor=&quot;10415&quot;&gt;yes&lt;/AllAPNConfigIncluded&gt;<br /> &lt;APNConfiguration vendor=&quot;10415&quot;&gt;<br /> &lt;ContextIdentifier vendor=&quot;10415&quot;&gt;555&lt;/ContextIdentifier&gt;<br /> &lt;ServedPartyIPAddr vendor=&quot;10415&quot;&gt;1.2.3.4&lt;/ServedPartyIPAddr&gt;<br /> &lt;ServedPartyIPAddr vendor=&quot;10415&quot;&gt;fe80::12:4&lt;/ServedPartyIPAddr&gt;<br /> &lt;PDNType vendor=&quot;10415&quot;&gt;ipv4v6&lt;/PDNType&gt;<br /> &lt;ServiceSelection&gt;*&lt;/ServiceSelection&gt;<br /> &lt;EpsSubscribedQosProfile vendor=&quot;10415&quot;&gt;<br /> &lt;QosClassIdentifier vendor=&quot;10415&quot;&gt;5&lt;/QosClassIdentifier&gt;<br /> &lt;AllocationRetentionPriority vendor=&quot;10415&quot;&gt;<br /> &lt;PriorityLevel vendor=&quot;10415&quot;&gt;2&lt;/PriorityLevel&gt;<br /> &lt;PreemptionCapability vendor=&quot;10415&quot;&gt;yes&lt;/PreemptionCapability&gt;<br /> &lt;PreemptionVulnerability vendor=&quot;10415&quot;&gt;no&lt;/PreemptionVulnerability&gt;<br /> &lt;/AllocationRetentionPriority&gt;<br /> &lt;/EpsSubscribedQosProfile&gt;<br /> &lt;VPlmnDynamicAddrAllowed vendor=&quot;10415&quot;&gt;yes&lt;/VPlmnDynamicAddrAllowed&gt;<br /> &lt;MIP6AgentInfo&gt;<br /> &lt;MIPHomeAgentAddress&gt;fe80::ad&lt;/MIPHomeAgentAddress&gt;<br /> &lt;/MIP6AgentInfo&gt;<br /> &lt;VisitedNetworkIdentifier vendor=&quot;10415&quot;&gt;1234567890&lt;/VisitedNetworkIdentifier&gt;<br /> &lt;PDNGWAllocationType vendor=&quot;10415&quot;&gt;static&lt;/PDNGWAllocationType&gt;<br /> &lt;ChargingCharacteristics vendor=&quot;10415&quot;&gt;gigi&lt;/ChargingCharacteristics&gt;<br /> &lt;AMBR vendor=&quot;10415&quot;&gt;<br /> &lt;MaxRequestedBandwithUL vendor=&quot;10415&quot;&gt;550000&lt;/MaxRequestedBandwithUL&gt;<br /> &lt;MaxRequestedBandwithDL vendor=&quot;10415&quot;&gt;519000&lt;/MaxRequestedBandwithDL&gt;<br /> &lt;/AMBR&gt;<br /> &lt;SIPTOPermission vendor=&quot;10415&quot;&gt;yes&lt;/SIPTOPermission&gt;<br /> &lt;LIPAPermission vendor=&quot;10415&quot;&gt;lipa-only&lt;/LIPAPermission&gt;<br /> &lt;RestorationPriority vendor=&quot;10415&quot;&gt;3&lt;/RestorationPriority&gt;<br /> &lt;/APNConfiguration&gt;<br /> &lt;/APNConfigurationProfile&gt;<br /> &lt;RATFreqSelPriorityID vendor=&quot;10415&quot;&gt;5&lt;/RATFreqSelPriorityID&gt;<br /> &lt;TraceData vendor=&quot;10415&quot;&gt;<br /> &lt;TraceReference vendor=&quot;10415&quot;&gt;004011998877&lt;/TraceReference&gt;<br /> &lt;TraceDepth vendor=&quot;10415&quot;&gt;medium&lt;/TraceDepth&gt;<br /> &lt;TraceNEList vendor=&quot;10415&quot;&gt;eNB,sgw&lt;/TraceNEList&gt;<br /> &lt;TraceInterfaceList vendor=&quot;10415&quot;&gt;<br /> &lt;mme&gt;s13,s1-mme&lt;/mme&gt;<br /> &lt;eir&gt;s13&lt;/eir&gt;<br /> &lt;/TraceInterfaceList&gt;<br /> &lt;TraceEventList vendor=&quot;10415&quot;&gt;<br /> &lt;sgw&gt;pdn-connectionCreation&lt;/sgw&gt;<br /> &lt;pgw&gt;pdn-connectionTermination&lt;/pgw&gt;<br /> &lt;mme&gt;handover&lt;/mme&gt;<br /> &lt;/TraceEventList&gt;<br /> &lt;OMCId vendor=&quot;10415&quot;&gt;001122&lt;/OMCId&gt;<br /> &lt;TraceCollectionEntity vendor=&quot;10415&quot;&gt;192.168.168.1&lt;/TraceCollectionEntity&gt;<br /> &lt;MDTConfiguration vendor=&quot;10415&quot;&gt;<br /> &lt;JobType vendor=&quot;10415&quot;&gt;rlf-reports-only&lt;/JobType&gt;<br /> &lt;AreaScope vendor=&quot;10415&quot;&gt;<br /> &lt;CellGlobalIdentity vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;12345&lt;/PlmnIdentity&gt;<br /> &lt;LAC&gt;1122&lt;/LAC&gt;<br /> &lt;CI&gt;123&lt;/CI&gt;<br /> &lt;/CellGlobalIdentity&gt;<br /> &lt;EutranCellGlobalIdentity vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;123456&lt;/PlmnIdentity&gt;<br /> &lt;CellIdentity&gt;1234567&lt;/CellIdentity&gt;<br /> &lt;/EutranCellGlobalIdentity&gt;<br /> &lt;RAI vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;12345&lt;/PlmnIdentity&gt;<br /> &lt;LAC&gt;1122&lt;/LAC&gt;<br /> &lt;RAC&gt;99&lt;/RAC&gt;<br /> &lt;/RAI&gt;<br /> &lt;LAI vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;123456&lt;/PlmnIdentity&gt;<br /> &lt;LAC&gt;1122&lt;/LAC&gt;<br /> &lt;/LAI&gt;<br /> &lt;TAI vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;123456&lt;/PlmnIdentity&gt;<br /> &lt;TAC&gt;1122&lt;/TAC&gt;<br /> &lt;/TAI&gt;<br /> &lt;/AreaScope&gt;<br /> &lt;ListOfMeasurements vendor=&quot;10415&quot;&gt;<br /> &lt;lte&gt;m2&lt;/lte&gt;<br /> &lt;umts&gt;m7-for-ul,m3&lt;/umts&gt;<br /> &lt;/ListOfMeasurements&gt;<br /> &lt;ReportingTrigger vendor=&quot;10415&quot;&gt;periodical&lt;/ReportingTrigger&gt;<br /> &lt;ReportInterval vendor=&quot;10415&quot;&gt;6&lt;/ReportInterval&gt;<br /> &lt;ReportAmount vendor=&quot;10415&quot;&gt;7&lt;/ReportAmount&gt;<br /> &lt;ThresholdRSRP vendor=&quot;10415&quot;&gt;10&lt;/ThresholdRSRP&gt;<br /> &lt;ThresholdRSRQ vendor=&quot;10415&quot;&gt;10&lt;/ThresholdRSRQ&gt;<br /> &lt;LoggingInterval vendor=&quot;10415&quot;&gt;7&lt;/LoggingInterval&gt;<br /> &lt;LoggingDuration vendor=&quot;10415&quot;&gt;5&lt;/LoggingDuration&gt;<br /> &lt;MeasurementPeriodUMTS vendor=&quot;10415&quot;&gt;13&lt;/MeasurementPeriodUMTS&gt;<br /> &lt;MeasurementPeriodLTE vendor=&quot;10415&quot;&gt;6&lt;/MeasurementPeriodLTE&gt;<br /> &lt;CollectionPeriodRrmLTE vendor=&quot;10415&quot;&gt;5&lt;/CollectionPeriodRrmLTE&gt;<br /> &lt;CollectionPeriodRrmUMTS vendor=&quot;10415&quot;&gt;5&lt;/CollectionPeriodRrmUMTS&gt;<br /> &lt;PositioningMethod vendor=&quot;10415&quot;&gt;gnss,e-cell-id&lt;/PositioningMethod&gt;<br /> &lt;MeasurementQuantity vendor=&quot;10415&quot;&gt;pathloss&lt;/MeasurementQuantity&gt;<br /> &lt;EventThreshold1F vendor=&quot;10415&quot;&gt;0&lt;/EventThreshold1F&gt;<br /> &lt;EventThreshold1I vendor=&quot;10415&quot;&gt;-5&lt;/EventThreshold1I&gt;<br /> &lt;/MDTConfiguration&gt;<br /> &lt;/TraceData&gt;<br /> &lt;GPRSSubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;CompleteDataList vendor=&quot;10415&quot;&gt;yes&lt;/CompleteDataList&gt;<br /> &lt;PDPContext vendor=&quot;10415&quot;&gt;<br /> &lt;ContextIdentifier vendor=&quot;10415&quot;&gt;99&lt;/ContextIdentifier&gt;<br /> &lt;PDPType vendor=&quot;10415&quot;&gt;11223344&lt;/PDPType&gt;<br /> &lt;PDPAddress vendor=&quot;10415&quot;&gt;1.2.3.4&lt;/PDPAddress&gt;<br /> &lt;QosSubscribed vendor=&quot;10415&quot;&gt;998877&lt;/QosSubscribed&gt;<br /> &lt;ServiceSelection&gt;*.example.com&lt;/ServiceSelection&gt;<br /> &lt;ExtPDPType vendor=&quot;10415&quot;&gt;11223355&lt;/ExtPDPType&gt;<br /> &lt;ExtPDPAddress vendor=&quot;10415&quot;&gt;1.2.3.5&lt;/ExtPDPAddress&gt;<br /> &lt;/PDPContext&gt;<br /> &lt;PDPContext vendor=&quot;10415&quot;&gt;<br /> &lt;ContextIdentifier vendor=&quot;10415&quot;&gt;100&lt;/ContextIdentifier&gt;<br /> &lt;PDPType vendor=&quot;10415&quot;&gt;11223366&lt;/PDPType&gt;<br /> &lt;QosSubscribed vendor=&quot;10415&quot;&gt;998866&lt;/QosSubscribed&gt;<br /> &lt;ServiceSelection&gt;*.example.com&lt;/ServiceSelection&gt;<br /> &lt;/PDPContext&gt;<br /> &lt;/GPRSSubscriptionData&gt;<br /> &lt;CsgSubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;CsgId vendor=&quot;10415&quot;&gt;345&lt;/CsgId&gt;<br /> &lt;ExpirationDate vendor=&quot;10415&quot;&gt;1234567890&lt;/ExpirationDate&gt;<br /> &lt;ServiceSelection&gt;*&lt;/ServiceSelection&gt;<br /> &lt;VisitedPlmnId vendor=&quot;10415&quot;&gt;045500&lt;/VisitedPlmnId&gt;<br /> &lt;/CsgSubscriptionData&gt;<br /> &lt;RoamingRestrictUnsuppFeature vendor=&quot;10415&quot;/&gt;<br /> &lt;SubscribedPeriodicRAUTAUTimer vendor=&quot;10415&quot;&gt;120&lt;/SubscribedPeriodicRAUTAUTimer&gt;<br /> &lt;MPSPriority vendor=&quot;10415&quot;&gt;cs,eps&lt;/MPSPriority&gt;<br /> &lt;VPlmnLIPAAllowed vendor=&quot;10415&quot;&gt;yes&lt;/VPlmnLIPAAllowed&gt;<br /> &lt;RelayNodeIndicator vendor=&quot;10415&quot;&gt;no&lt;/RelayNodeIndicator&gt;<br /> &lt;MDTUserConsent vendor=&quot;10415&quot;&gt;yes&lt;/MDTUserConsent&gt;<br /> &lt;SubscribedVSRVCC vendor=&quot;10415&quot;/&gt;<br /> &lt;SubscriptionDataFlags vendor=&quot;10415&quot;&gt;ps-and-sms-only,sms-in-sgsn&lt;/SubscriptionDataFlags&gt;<br /> &lt;/SubscriptionData&gt;<br /> &lt;/UpdateLocationAnswer&gt;<br /> <br /> Answer, failure, unknown subscriber:<br /> <br /> &lt;UpdateLocationAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;ExperimentalResult&gt;<br /> &lt;value vendor=&quot;10415&quot;&gt;user-unknown&lt;/value&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;/UpdateLocationAnswer&gt; <br /> <br /> == Cancel Location Command ==<br /> <br /> Direction: HSS -&gt; MME/SGSN&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;CancelLocationRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;CancellationType vendor=&quot;10415&quot;&gt;subscription-withdrawal&lt;/CancellationType&gt;<br /> &lt;CLRFlags vendor=&quot;10415&quot;&gt;s6a&lt;/CLRFlags&gt;<br /> &lt;/CancelLocationRequest&gt;<br /> <br /> Answer:<br /> <br /> &lt;CancelLocationAnswer appid=&quot;16777251&quot; flags=&quot;proxiable&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;/CancelLocationAnswer&gt;<br /> <br /> == Insert Subscriber Data Command ==<br /> <br /> Direction: HSS -&gt; MME/SGSN&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;InsertSubscriberDataRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;MSISDN vendor=&quot;10415&quot;&gt;40700100100&lt;/MSISDN&gt;<br /> &lt;/SubscriptionData&gt;<br /> &lt;IDRFlags vendor=&quot;10415&quot;&gt;eps-user-state-req,eps-loc-info-req,local-tz-req,rat-type-req&lt;/IDRFlags&gt;<br /> &lt;/InsertSubscriberDataRequest&gt;<br /> <br /> Answer:<br /> <br /> &lt;InsertSubscriberDataAnswer appid=&quot;16777251&quot; flags=&quot;proxiable&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;IMSVOPSSS vendor=&quot;10415&quot;&gt;yes&lt;/IMSVOPSSS&gt;<br /> &lt;LastUEActivityTime vendor=&quot;10415&quot;&gt;12345678&lt;/LastUEActivityTime&gt;<br /> &lt;RATType vendor=&quot;10415&quot;&gt;e-utran&lt;/RATType&gt;<br /> &lt;IDAFlags vendor=&quot;10415&quot;&gt;network-node-area-restricted&lt;/IDAFlags&gt;<br /> &lt;EpsUserState vendor=&quot;10415&quot;&gt;<br /> &lt;MmeUserState vendor=&quot;10415&quot;&gt;<br /> &lt;UserState vendor=&quot;10415&quot;&gt;attached-reachable-for-paging&lt;/UserState&gt;<br /> &lt;/MmeUserState&gt;<br /> &lt;/EpsUserState&gt;<br /> &lt;EpsLocationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;MmeLocationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;EutranCellGlobalIdentity vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;123456&lt;/PlmnIdentity&gt;<br /> &lt;CellIdentity&gt;1234567&lt;/CellIdentity&gt;<br /> &lt;/EutranCellGlobalIdentity&gt;<br /> &lt;GeographicalInfo vendor=&quot;10415&quot;&gt;0001020304050607&lt;/GeographicalInfo&gt;<br /> &lt;GeodeticInfo vendor=&quot;10415&quot;&gt;00010203040506070809&lt;/GeodeticInfo&gt;<br /> &lt;CurrentLocationRetrieved vendor=&quot;10415&quot;&gt;active-loc-retrieval&lt;/CurrentLocationRetrieved&gt;<br /> &lt;AgeOfLocationInfo vendor=&quot;10415&quot;&gt;7&lt;/AgeOfLocationInfo&gt;<br /> &lt;UserCsgInfo vendor=&quot;10415&quot;&gt;<br /> &lt;CsgId vendor=&quot;10415&quot;&gt;345&lt;/CsgId&gt;<br /> &lt;CsgAccessMode vendor=&quot;10415&quot;&gt;closed&lt;/CsgAccessMode&gt;<br /> &lt;CsgMembershipInd vendor=&quot;10415&quot;&gt;yes&lt;/CsgMembershipInd&gt;<br /> &lt;/UserCsgInfo&gt;<br /> &lt;/MmeLocationInfo&gt;<br /> &lt;SgsnLocationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;SAI vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;12345&lt;/PlmnIdentity&gt;<br /> &lt;LAC&gt;1122&lt;/LAC&gt;<br /> &lt;SAC&gt;99&lt;/SAC&gt;<br /> &lt;/SAI&gt;<br /> &lt;/SgsnLocationInfo&gt;<br /> &lt;/EpsLocationInfo&gt;<br /> &lt;LocalTimeZone vendor=&quot;10415&quot;&gt;<br /> &lt;TimeZone vendor=&quot;10415&quot;&gt;+2&lt;/TimeZone&gt;<br /> &lt;DaylightSavingTime vendor=&quot;10415&quot;&gt;1&lt;/DaylightSavingTime&gt;<br /> &lt;/LocalTimeZone&gt;<br /> &lt;IDAFlags vendor=&quot;10415&quot;&gt;network-node-area-restricted&lt;/IDAFlags&gt;<br /> &lt;/InsertSubscriberDataAnswer&gt;<br /> <br /> == Delete Subscriber Data Command ==<br /> <br /> Direction: HSS -&gt; MME/SGSN&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;DeleteSubscriberDataRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;DSRFlags vendor=&quot;10415&quot;&gt;sms-withdrawal,trace-data-withdrawal&lt;/DSRFlags&gt;<br /> &lt;TraceReference vendor=&quot;10415&quot;&gt;004011998877&lt;/TraceReference&gt;<br /> &lt;TSCode vendor=&quot;10415&quot;&gt;allDataTeleservices&lt;/TSCode&gt;<br /> &lt;TSCode vendor=&quot;10415&quot;&gt;allSpeechTransmissionServices&lt;/TSCode&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allLineIdentificationSS&lt;/SSCode&gt;<br /> &lt;SSCode vendor=&quot;10415&quot;&gt;allCallOfferingSS&lt;/SSCode&gt;<br /> &lt;/DeleteSubscriberDataRequest&gt;<br /> <br /> Answer:<br /> <br /> &lt;DeleteSubscriberDataAnswer appid=&quot;16777251&quot; flags=&quot;proxiable&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;DSAFlags vendor=&quot;10415&quot;&gt;network-node-area-restricted&lt;/DSAFlags&gt;<br /> &lt;/DeleteSubscriberDataAnswer&gt;<br /> <br /> == Authentication Info Command ==<br /> <br /> Direction: MME/SGSN -&gt; HSS&lt;br&gt;<br /> <br /> Request:<br /> &lt;AuthenticationInfoRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;2&quot;&gt;sms-in-mme&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;RequestedEutranAuthInfo vendor=&quot;10415&quot;&gt;<br /> &lt;NumberOfRequestedVectors vendor=&quot;10415&quot;&gt;5&lt;/NumberOfRequestedVectors&gt;<br /> &lt;ImmediateResponsePreferred vendor=&quot;10415&quot;/&gt;<br /> &lt;ReSynchronisationInfo vendor=&quot;10415&quot;&gt;001122&lt;/ReSynchronisationInfo&gt;<br /> &lt;/RequestedEutranAuthInfo&gt;<br /> &lt;RequestedUtranGeranAuthInfo vendor=&quot;10415&quot;&gt;<br /> &lt;NumberOfRequestedVectors vendor=&quot;10415&quot;&gt;3&lt;/NumberOfRequestedVectors&gt;<br /> &lt;ReSynchronisationInfo vendor=&quot;10415&quot;&gt;001122&lt;/ReSynchronisationInfo&gt;<br /> &lt;/RequestedUtranGeranAuthInfo&gt;<br /> &lt;VisitedPlmnId vendor=&quot;10415&quot;&gt;040100&lt;/VisitedPlmnId&gt;<br /> &lt;/AuthenticationInfoRequest&gt;<br /> <br /> Answer, success:<br /> <br /> &lt;AuthenticationInfoAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;VendorSpecificApplicationId flags=&quot;mandatory&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; auth=&quot;true&quot;&gt;16777251&lt;/value&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode flags=&quot;mandatory&quot;&gt;2001&lt;/ResultCode&gt;<br /> &lt;ErrorDiagnostic flags=&quot;vendor&quot; vendor=&quot;10415&quot;&gt;odb-HPLMN-APN&lt;/ErrorDiagnostic&gt;<br /> &lt;SupportedFeatures flags=&quot;vendor&quot; vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;baoc,boic&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;AuthenticationInfo flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;<br /> &lt;EutranVector flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;<br /> &lt;ItemNumber flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;1&lt;/ItemNumber&gt;<br /> &lt;RAND flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;XRES flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;12345678&lt;/XRES&gt;<br /> &lt;AUTN flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;12345678&lt;/AUTN&gt;<br /> &lt;KASME flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;12345678&lt;/KASME&gt;<br /> &lt;/EutranVector&gt;<br /> &lt;EutranVector flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;<br /> &lt;ItemNumber flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;2&lt;/ItemNumber&gt;<br /> &lt;RAND flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;XRES flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;00345678&lt;/XRES&gt;<br /> &lt;AUTN flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;00345678&lt;/AUTN&gt;<br /> &lt;KASME flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;00345678&lt;/KASME&gt;<br /> &lt;/EutranVector&gt;<br /> &lt;UtranVector flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;<br /> &lt;RAND flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;XRES flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;22345678&lt;/XRES&gt;<br /> &lt;AUTN flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;22345678&lt;/AUTN&gt;<br /> &lt;ConfidentialityKey flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;22345678&lt;/ConfidentialityKey&gt;<br /> &lt;IntegrityKey flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;22345678&lt;/IntegrityKey&gt;<br /> &lt;/UtranVector&gt;<br /> &lt;GeranVector flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;<br /> &lt;RAND flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;SRES flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;34567811&lt;/SRES&gt;<br /> &lt;Kc flags=&quot;vendor,mandatory&quot; vendor=&quot;10415&quot;&gt;34567811&lt;/Kc&gt;<br /> &lt;/GeranVector&gt;<br /> &lt;/AuthenticationInfo&gt;<br /> &lt;/AuthenticationInfoAnswer&gt;<br /> <br /> Answer, failure, auth data not found:<br /> <br /> &lt;AuthenticationInfoAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;ExperimentalResult&gt;<br /> &lt;value vendor=&quot;10415&quot;&gt;auth-data-unavailable&lt;/value&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;/AuthenticationInfoAnswer&gt;<br /> <br /> == Purge UE Command ==<br /> <br /> Direction: MME/SGSN -&gt; HSS&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;PurgeUERequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;PURFlags vendor=&quot;10415&quot;&gt;ue-purged-in-mme,ue-purged-in-sgsn&lt;/PURFlags&gt;<br /> &lt;/PurgeUERequest&gt;<br /> <br /> Answer, success:<br /> <br /> &lt;PurgeUEAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;PUAFlags vendor=&quot;10415&quot;&gt;freeze-m-tmsi,freeze-p-tmsi&lt;/PUAFlags&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;1&quot;&gt;boic,baoc,regsub&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;/PurgeUEAnswer&gt;<br /> <br /> Answer, failure, requesting node is unknown:<br /> <br /> &lt;PurgeUEAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;ExperimentalResult&gt;<br /> &lt;value vendor=&quot;10415&quot;&gt;unknown-serving-node&lt;/value&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;/PurgeUEAnswer&gt;<br /> <br /> == Reset Command ==<br /> <br /> Direction: HSS -&gt; MME/SGSN&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;ResetRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;UserId vendor=&quot;10415&quot;&gt;004100&lt;/UserId&gt;<br /> &lt;/ResetRequest&gt;<br /> <br /> Answer:<br /> <br /> &lt;ResetAnswer appid=&quot;16777251&quot; flags=&quot;proxiable&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;/ResetAnswer&gt;<br /> <br /> == Notify Command ==<br /> <br /> Direction: MME/SGSN -&gt; HSS&lt;br&gt;<br /> <br /> Request:<br /> <br /> &lt;NotifyRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;2&quot;&gt;sms-in-mme&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;TerminalInfo vendor=&quot;10415&quot;&gt;<br /> &lt;IMEI vendor=&quot;10415&quot;&gt;1234567890&lt;/IMEI&gt;<br /> &lt;/TerminalInfo&gt;<br /> &lt;MIP6AgentInfo&gt;<br /> &lt;MIPHomeAgentAddress&gt;fe80::2&lt;/MIPHomeAgentAddress&gt;<br /> &lt;MIP6HomeLinkPrefix&gt;001122&lt;/MIP6HomeLinkPrefix&gt;<br /> &lt;/MIP6AgentInfo&gt;<br /> &lt;VisitedNetworkIdentifier vendor=&quot;10415&quot;&gt;998877&lt;/VisitedNetworkIdentifier&gt;<br /> &lt;ContextIdentifier vendor=&quot;10415&quot;&gt;100&lt;/ContextIdentifier&gt;<br /> &lt;ServiceSelection&gt;*&lt;/ServiceSelection&gt;<br /> &lt;AlertReason vendor=&quot;10415&quot;&gt;ue-memory-available&lt;/AlertReason&gt;<br /> &lt;UESRVCCCapability vendor=&quot;10415&quot;&gt;yes&lt;/UESRVCCCapability&gt;<br /> &lt;NORFlags vendor=&quot;10415&quot;&gt;ue-reachable-from-mme,ready-sm-from-mme&lt;/NORFlags&gt;<br /> &lt;HSoIMSVOPSS vendor=&quot;10415&quot;&gt;yes&lt;/HSoIMSVOPSS&gt;<br /> &lt;/NotifyRequest&gt;<br /> <br /> Answer, success:<br /> <br /> &lt;NotifyAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;/NotifyAnswer&gt;<br /> <br /> Answer, failure, unknown node:<br /> <br /> &lt;NotifyAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot; flags=&quot;proxiable&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;ExperimentalResult&gt;<br /> &lt;value vendor=&quot;10415&quot;&gt;unknown-serving-node&lt;/value&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;/NotifyAnswer&gt;<br /> <br /> == References ==<br /> <br /> * RFC 3588 - Diameter Base Protocol<br /> * RFC 6733 - Diameter Base Protocol<br /> * RFC 5516 - Diameter Command Code Registration for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)<br /> * ETSI TS 129.272 - MME and SGSN related interfaces based on Diameter protocol (S6a/S6d, S7a/S7d, S13/S13')</div>

Oana https://ss7api.null.ro/index.php/Diameter_Latency_determination 2016-09-09T14:37:17Z

<p>Oana: Created page with &quot;The purpose of latency determination is to estimate how much time takes for a message to be processed by a Diameter application. The xml_tcp module computes average applicati...&quot;</p> <hr /> <div>The purpose of latency determination is to estimate how much time takes for a message to be processed by a Diameter application.<br /> <br /> The xml_tcp module computes average application processing latency by handling timestamps from messages exchanged on that connection.<br /> * Each message sent by the module can be timestamped with the server's current time<br /> * Application copies the timestamp from the received XML to the one it responds with<br /> * If the module receives a timestamp it will compute the difference from the current time and adjust average latency<br /> <br /> The timestamps need to be enabled in the xml_tcp.conf module. This can be done per Diameter listener<br /> <br /> <br /> [listener s6a]<br /> type=diameter<br /> ...<br /> add-timestamp=yes<br /> <br /> If enabled the timestamps are added in their own XML element named timestamp-send:<br /> &lt;m&gt;<br /> &lt;timestamp-send&gt;1377071763411706&lt;/timestamp-send&gt;<br /> ...<br /> &lt;/m&gt;<br /> <br /> The application is supposed to copy the received timestamp to the response in a timestamp-recv element:<br /> <br /> &lt;m&gt;<br /> &lt;timestamp-recv&gt;1377071763411706&lt;/timestamp-recv&gt;<br /> ...<br /> &lt;/m&gt;<br /> <br /> These are exposed through the status of the xml_tcp module.</div>

Oana https://ss7api.null.ro/index.php/Diameter_Commands 2016-09-09T13:40:10Z

<p>Oana: /* Parameters */</p> <hr /> <div>This is the main part of the message holding the data specific to each Diameter interface.<br /> <br /> The Diameter command is wrapped in a XML element marked by ''&lt;operation/&gt;'' to make it easy to find the information in the XML. The child of the ''&lt;operation/&gt;'' is an XML describing the Diameter command decoded/to be encoded. The tag of the child element is the name of the command.<br /> <br /> Each message can only contain a single Diameter command message.<br /> <br /> &lt;m&gt;<br /> .... <br /> &lt;operation&gt;<br /> &lt;InsertSubscriberDataRequest appid=&quot;16777251&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;MSISDN vendor=&quot;10415&quot;&gt;40700100100&lt;/MSISDN&gt;<br /> &lt;/SubscriptionData&gt;<br /> &lt;IDRFlags vendor=&quot;10415&quot;&gt;eps-user-state-req,eps-loc-info-req,local-tz-req,rat-type-req&lt;/IDRFlags&gt;<br /> &lt;/InsertSubscriberDataRequest&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> ==Parameters==<br /> <br /> For the XML child containing the command, the following parameters appear as attributes (bold - mandatory, italic - optional)<br /> * '''appid''': Numeric identifier of the interface to which this message belongs to<br /> * ''flags'' : Diameter flags for the message. For messages on direction TCP aplication -&gt; Diameter translator, flags are optional in requests/answers(they will be added automatically by Diameter), but if they are added, they must be correctly correlated with the tag. An error answer must set flags to error.<br /> * ''hhident'': Hop-to-hop identifier. Present in messages received by an application server. When an application sends a request, the Diameter translator automatically adds it<br /> * ''eeident'': End-to-End identifier. Present in messages received by an application server. When an application sends a request, the Diameter translator automatically adds it<br /> <br /> For S6a messages, the application ID is 16777251. See [[S6a/Sad|S6a/S6d interface]].<br /> <br /> Non-base protocol Diameter AVPs must have '''vendor''' identifier set. For 3GPP AVPs this is 10415.<br /> <br /> ==Examples==<br /> <br /> * Request (HSS -&gt; MME &amp; TCP -&gt; Diameter):<br /> &lt;m&gt;<br /> &lt;timestamp-recv&gt;1470663005862835&lt;/timestamp-recv&gt;<br /> &lt;diameter&gt;<br /> &lt;timeout&gt;60000&lt;/timeout&gt;<br /> &lt;local_node&gt;example.com/hss.example.com&lt;/local_node&gt;<br /> &lt;trans_id&gt;hss/123456&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;InsertSubscriberDataRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;MSISDN vendor=&quot;10415&quot;&gt;40700100100&lt;/MSISDN&gt;<br /> &lt;/SubscriptionData&gt;<br /> &lt;IDRFlags vendor=&quot;10415&quot;&gt;eps-user-state-req,eps-loc-info-req,local-tz-req,rat-type-req&lt;/IDRFlags&gt;<br /> &lt;/InsertSubscriberDataRequest&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> * Answer (MME -&gt; HSS &amp; Diameter -&gt; TCP):<br /> &lt;m&gt;<br /> &lt;timestamp-send&gt;1470663005862835&lt;/timestamp-send&gt;<br /> &lt;diameter&gt;<br /> &lt;trans_id&gt;hss/123456&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;InsertSubscriberDataAnswer appid=&quot;16777251&quot; flags=&quot;proxiable&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;IMSVOPSSS vendor=&quot;10415&quot;&gt;yes&lt;/IMSVOPSSS&gt;<br /> &lt;LastUEActivityTime vendor=&quot;10415&quot;&gt;12345678&lt;/LastUEActivityTime&gt;<br /> &lt;RATType vendor=&quot;10415&quot;&gt;e-utran&lt;/RATType&gt;<br /> &lt;IDAFlags vendor=&quot;10415&quot;&gt;network-node-area-restricted&lt;/IDAFlags&gt;<br /> &lt;EpsUserState vendor=&quot;10415&quot;&gt;<br /> &lt;MmeUserState vendor=&quot;10415&quot;&gt;<br /> &lt;UserState vendor=&quot;10415&quot;&gt;attached-reachable-for-paging&lt;/UserState&gt;<br /> &lt;/MmeUserState&gt;<br /> &lt;/EpsUserState&gt;<br /> &lt;EpsLocationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;MmeLocationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;EutranCellGlobalIdentity vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;123456&lt;/PlmnIdentity&gt;<br /> &lt;CellIdentity&gt;1234567&lt;/CellIdentity&gt;<br /> &lt;/EutranCellGlobalIdentity&gt;<br /> &lt;GeographicalInfo vendor=&quot;10415&quot;&gt;0001020304050607&lt;/GeographicalInfo&gt;<br /> &lt;GeodeticInfo vendor=&quot;10415&quot;&gt;00010203040506070809&lt;/GeodeticInfo&gt;<br /> &lt;CurrentLocationRetrieved vendor=&quot;10415&quot;&gt;active-loc-retrieval&lt;/CurrentLocationRetrieved&gt;<br /> &lt;AgeOfLocationInfo vendor=&quot;10415&quot;&gt;7&lt;/AgeOfLocationInfo&gt;<br /> &lt;UserCsgInfo vendor=&quot;10415&quot;&gt;<br /> &lt;CsgId vendor=&quot;10415&quot;&gt;345&lt;/CsgId&gt;<br /> &lt;CsgAccessMode vendor=&quot;10415&quot;&gt;closed&lt;/CsgAccessMode&gt;<br /> &lt;CsgMembershipInd vendor=&quot;10415&quot;&gt;yes&lt;/CsgMembershipInd&gt;<br /> &lt;/UserCsgInfo&gt;<br /> &lt;/MmeLocationInfo&gt;<br /> &lt;SgsnLocationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;SAI vendor=&quot;10415&quot;&gt;<br /> &lt;PlmnIdentity&gt;12345&lt;/PlmnIdentity&gt;<br /> &lt;LAC&gt;1122&lt;/LAC&gt;<br /> &lt;SAC&gt;99&lt;/SAC&gt;<br /> &lt;/SAI&gt;<br /> &lt;/SgsnLocationInfo&gt;<br /> &lt;/EpsLocationInfo&gt;<br /> &lt;LocalTimeZone vendor=&quot;10415&quot;&gt;<br /> &lt;TimeZone vendor=&quot;10415&quot;&gt;+2&lt;/TimeZone&gt;<br /> &lt;DaylightSavingTime vendor=&quot;10415&quot;&gt;1&lt;/DaylightSavingTime&gt;<br /> &lt;/LocalTimeZone&gt;<br /> &lt;IDAFlags vendor=&quot;10415&quot;&gt;network-node-area-restricted&lt;/IDAFlags&gt;<br /> &lt;/InsertSubscriberDataAnswer&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> * Error (local host -&gt; TCP application)<br /> <br /> &lt;m&gt;<br /> &lt;timestamp-send&gt;1470663005862835&lt;/timestamp-send&gt;<br /> &lt;diameter&gt;<br /> &lt;trans_id&gt;hss/123456&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;InsertSubscriberDataAnswer appid=&quot;16777251&quot; flags=&quot;error&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&gt;<br /> &lt;OriginHost&gt;hss.example.com&lt;/OriginHost&gt;<br /> &lt;OriginRealm&gt;example.com&lt;/OriginRealm&gt;<br /> &lt;ResultCode&gt;3002&lt;/ResultCode&gt;<br /> &lt;ErrorMessage&gt;timeout&lt;/ErrorMessage&gt;<br /> &lt;/InsertSubscriberDataAnswer&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> <br /> * Request (MME -&gt; HSS &amp; Diameter -&gt; TCP)<br /> <br /> &lt;m&gt;<br /> &lt;timestamp-send&gt;1470663005862835&lt;/timestamp-send&gt;<br /> &lt;diameter&gt;<br /> &lt;trans_id&gt;diam/456789&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;AuthenticationInfoRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value id=&quot;2&quot;&gt;sms-in-mme&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;RequestedEutranAuthInfo vendor=&quot;10415&quot;&gt;<br /> &lt;NumberOfRequestedVectors vendor=&quot;10415&quot;&gt;5&lt;/NumberOfRequestedVectors&gt;<br /> &lt;ImmediateResponsePreferred vendor=&quot;10415&quot;/&gt;<br /> &lt;ReSynchronisationInfo vendor=&quot;10415&quot;&gt;001122&lt;/ReSynchronisationInfo&gt;<br /> &lt;/RequestedEutranAuthInfo&gt;<br /> &lt;RequestedUtranGeranAuthInfo vendor=&quot;10415&quot;&gt;<br /> &lt;NumberOfRequestedVectors vendor=&quot;10415&quot;&gt;3&lt;/NumberOfRequestedVectors&gt;<br /> &lt;ReSynchronisationInfo vendor=&quot;10415&quot;&gt;001122&lt;/ReSynchronisationInfo&gt;<br /> &lt;/RequestedUtranGeranAuthInfo&gt;<br /> &lt;VisitedPlmnId vendor=&quot;10415&quot;&gt;040100&lt;/VisitedPlmnId&gt;<br /> &lt;/AuthenticationInfoRequest&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> <br /> * Answer (HSS -&gt; MME &amp; TCP -&gt; Diameter):<br /> <br /> &lt;m&gt;<br /> &lt;timestamp-recv&gt;1470663005862835&lt;/timestamp-recv&gt;<br /> &lt;diameter&gt;<br /> &lt;trans_id&gt;diam/456789&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;AuthenticationInfoAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;VendorSpecificApplicationId&gt;<br /> &lt;value vendor=&quot;10415&quot; auth=&quot;true&quot;&gt;16777251&lt;/value&gt;<br /> &lt;/VendorSpecificApplicationId&gt;<br /> &lt;ResultCode&gt;2001&lt;/ResultCode&gt;<br /> &lt;ErrorDiagnostic vendor=&quot;10415&quot;&gt;odb-HPLMN-APN&lt;/ErrorDiagnostic&gt;<br /> &lt;SupportedFeatures vendor=&quot;10415&quot;&gt;<br /> &lt;value vendor=&quot;10415&quot; id=&quot;1&quot;&gt;baoc,boic&lt;/value&gt;<br /> &lt;/SupportedFeatures&gt;<br /> &lt;AuthenticationInfo vendor=&quot;10415&quot;&gt;<br /> &lt;EutranVector vendor=&quot;10415&quot;&gt;<br /> &lt;ItemNumber vendor=&quot;10415&quot;&gt;1&lt;/ItemNumber&gt;<br /> &lt;RAND vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;XRES vendor=&quot;10415&quot;&gt;12345678&lt;/XRES&gt;<br /> &lt;AUTN vendor=&quot;10415&quot;&gt;12345678&lt;/AUTN&gt;<br /> &lt;KASME vendor=&quot;10415&quot;&gt;12345678&lt;/KASME&gt;<br /> &lt;/EutranVector&gt;<br /> &lt;EutranVector vendor=&quot;10415&quot;&gt;<br /> &lt;ItemNumber vendor=&quot;10415&quot;&gt;2&lt;/ItemNumber&gt;<br /> &lt;RAND vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;XRES vendor=&quot;10415&quot;&gt;00345678&lt;/XRES&gt;<br /> &lt;AUTN vendor=&quot;10415&quot;&gt;00345678&lt;/AUTN&gt;<br /> &lt;KASME vendor=&quot;10415&quot;&gt;00345678&lt;/KASME&gt;<br /> &lt;/EutranVector&gt;<br /> &lt;UtranVector vendor=&quot;10415&quot;&gt;<br /> &lt;RAND vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;XRES vendor=&quot;10415&quot;&gt;22345678&lt;/XRES&gt;<br /> &lt;AUTN vendor=&quot;10415&quot;&gt;22345678&lt;/AUTN&gt;<br /> &lt;ConfidentialityKey vendor=&quot;10415&quot;&gt;22345678&lt;/ConfidentialityKey&gt;<br /> &lt;IntegrityKey vendor=&quot;10415&quot;&gt;22345678&lt;/IntegrityKey&gt;<br /> &lt;/UtranVector&gt;<br /> &lt;GeranVector vendor=&quot;10415&quot;&gt;<br /> &lt;RAND vendor=&quot;10415&quot;&gt;01020304111213142122232441424344&lt;/RAND&gt;<br /> &lt;SRES vendor=&quot;10415&quot;&gt;34567811&lt;/SRES&gt;<br /> &lt;Kc vendor=&quot;10415&quot;&gt;34567811&lt;/Kc&gt;<br /> &lt;/GeranVector&gt;<br /> &lt;/AuthenticationInfo&gt;<br /> &lt;/AuthenticationInfoAnswer&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> * Error (HSS -&gt; MME &amp; TCP -&gt; Diameter, failure, auth data not found):<br /> <br /> &lt;m&gt;<br /> &lt;timestamp-recv&gt;1470663005862835&lt;/timestamp-recv&gt;<br /> &lt;diameter&gt;<br /> &lt;trans_id&gt;diam/456789&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;AuthenticationInfoAnswer appid=&quot;16777251&quot; hhident=&quot;${hhident}&quot; eeident=&quot;${eeident}&quot;&gt;<br /> &lt;SessionId&gt;${session_id}&lt;/SessionId&gt;<br /> &lt;AuthSessionState&gt;1&lt;/AuthSessionState&gt;<br /> &lt;ExperimentalResult&gt;<br /> &lt;value vendor=&quot;10415&quot;&gt;auth-data-unavailable&lt;/value&gt;<br /> &lt;/ExperimentalResult&gt;<br /> &lt;/AuthenticationInfoAnswer&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;</div>

Oana https://ss7api.null.ro/index.php/Diameter_Transport 2016-09-09T11:27:20Z

<p>Oana: </p> <hr /> <div>The transport part of the message contains parameters related to identifying a message and controlling the transmission of a Diameter message. For requests from application serves, these parameters are combined with parameters from the Diameter command to configure the handling and routing of the message.<br /> <br /> This part of the message is marked by the '''&lt;diameter/&gt;''' tag and contains information related to sending/receiving messages, but are not part of the Diameter command. <br /> <br /> These are the parameters for sending a message (bold means mandatory, italic - optional):<br /> * '''trans_id''': Unique identifier per direction used to match requests and answers and identify a certain Diameter transaction. In Diameter -&gt; TCP application direction, this is set by the YATE Diameter level and it must be returned in the answer sent by the TCP application. In the TCP application -&gt; Diameter direction, the TCP application sets it in the request and the Diameter level will return in the answer. The identifier has no required format, must be only a uniquely generated string per Diameter transaction.<br /> * '''local_node''': Identifier of the local node (${realm}/${host}) to use for sending a request from the TCP application. If not present, one must be set in ''connection.'' configuration of the listener. The one present in XML will override the configured one. <br /> * ''timeout'': setting the timeout for a request in the TCP application -&gt; Diameter direction. This allows overriding the configured Diameter timeout setting (optional). It can also be set in ''connection.'' configuration or in diameter configuration. This is in milliseconds.<br /> <br /> <br /> Example:<br /> <br /> &lt;m&gt;<br /> ...<br /> &lt;diameter&gt;<br /> &lt;timeout&gt;60000&lt;/timeout&gt;<br /> &lt;local_node&gt;example.com/hss.example.com&lt;/local_node&gt;<br /> &lt;trans_id&gt;hss/123456&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> ....<br /> &lt;/m&gt;</div>

Oana https://ss7api.null.ro/index.php/Diameter_Common_features 2016-09-09T10:52:02Z

<p>Oana: Created page with &quot;Messages are represented hierarchically in XML format. There may be more parameters than described in this specification. Unknown parameters should be ignored. Each message c...&quot;</p> <hr /> <div>Messages are represented hierarchically in XML format. There may be more parameters than described in this specification. Unknown parameters should be ignored.<br /> <br /> Each message contains 3 major parts:<br /> <br /> * Latency related information<br /> * Diameter information regarding identification and transport<br /> * Diameter command<br /> <br /> In XML these map like in this example:<br /> <br /> &lt;m&gt;<br /> <br /> &lt;timestamp-recv&gt;1470663005862835&lt;/timestamp-recv&gt;<br /> &lt;diameter&gt;<br /> &lt;timeout&gt;60000&lt;/timeout&gt;<br /> &lt;local_node&gt;example.com/hss.example.com&lt;/local_node&gt;<br /> &lt;trans_id&gt;hss/123456&lt;/trans_id&gt;<br /> &lt;/diameter&gt;<br /> &lt;operation&gt;<br /> &lt;InsertSubscriberDataRequest appid=&quot;16777251&quot; flags=&quot;request,proxiable&quot;&gt;<br /> &lt;DestinationHost&gt;mme.example.com&lt;/DestinationHost&gt;<br /> &lt;DestinationRealm&gt;example.com&lt;/DestinationRealm&gt;<br /> &lt;Username&gt;004100123456789&lt;/Username&gt;<br /> &lt;SubscriptionData vendor=&quot;10415&quot;&gt;<br /> &lt;MSISDN vendor=&quot;10415&quot;&gt;40700100100&lt;/MSISDN&gt;<br /> &lt;/SubscriptionData&gt;<br /> &lt;IDRFlags vendor=&quot;10415&quot;&gt;eps-user-state-req,eps-loc-info-req,local-tz-req,rat-type-req&lt;/IDRFlags&gt;<br /> &lt;/InsertSubscriberDataRequest&gt;<br /> &lt;/operation&gt;<br /> &lt;/m&gt;<br /> <br /> <br /> In these examples the XML is nicely indented for readability. In practice any whitespace between XML elements may be omitted.</div>

Oana https://ss7api.null.ro/index.php/Diameter_Connection 2016-09-09T10:43:36Z

<p>Oana: /* Announcing capabilities */</p> <hr /> <div>The connection used for exchange of XML formatted messages is a TCP socket. As an option TLS can be used to protect the information. In that case the information on this page applies only to the unencrypted data, the certificate check and establishment of encryption are outside the scope of this page.<br /> <br /> ==Establishing the connection==<br /> <br /> A connection is established from the application to the Diameter translator. Each translator is associated with a TCP listener. Each TCP listener is associated with a certain Diameter interface. An application can establish multiple connections to the Diameter translator. Each connection is independent from the others. To establish the connection a TCP socket must be connected to the agreed listening port of the translator. Upon a successful connection XML messages exchange can start.<br /> <br /> The XML declaration &lt;?xml … ?&gt; must be present in the first exchanged message. On further messages the declaration may be omitted.<br /> <br /> All messages must have a root &lt;m&gt; element. The optional xmlns attribute must be &quot;http://yate.null.ro/xml/diameter/v1&quot; (note that the URL doesn't point to a valid location).<br /> <br /> The closing tag &lt;/m&gt; can be used to look up for the end of XML in the stream.<br /> <br /> ==Announcing capabilities==<br /> <br /> After connection on the TCP socket, the application will announce its capabilities. Otherwise, it will not be considered a valid connection for Diameter messages and it will be ignored.<br /> <br /> This initial XML message must have both an XML declaration and an xmlns in the root element indicating the correct version of the protocol is being spoken.<br /> <br /> Each supported capability will be announced in a &lt;c&gt; element placed in the root element.<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; ?&gt;<br /> &lt;m xmlns=&quot;http://yate.null.ro/xml/diameter/v1&quot;&gt;<br /> &lt;c&gt;HSSMobility&lt;/c&gt;<br /> &lt;c&gt;MMEMobility&lt;/c&gt;<br /> ...<br /> &lt;/m&gt;<br /> <br /> On success the translator will confirm and indicate the application is active (receives messages):<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; ?&gt;<br /> &lt;m xmlns=&quot;http://yate.null.ro/xml/diameter/v1&quot;&gt;<br /> &lt;state&gt;active&lt;/state&gt;<br /> &lt;/m&gt;<br /> <br /> <br /> On failure the converter may return an error text and will close the socket after that. In case of XML error or xmlns mismatch no error is returned.<br /> &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; ?&gt;<br /> &lt;m xmlns=&quot;http://yate.null.ro/xml/tcap/v1&quot;&gt;<br /> &lt;state&gt;inactive&lt;/state&gt;<br /> &lt;error&gt;Unsupported: Charging&lt;/error&gt;<br /> &lt;/m&gt;<br /> <br /> For S6a interface, the capabilities are organized by the entity that can handle the requests. Capability - operations associations are: <br /> * HSSMobility : UpdateLocationRequest, UpdateLocationAnswer, PurgeUERequest, PurgeUEAnswer, NotifyRequest, NotifyAnswer<br /> * MMEMobility :CancelLocationRequest, CancelLocationAnswer, InsertSubscriberDataRequest, InsertSubscriberDataAnswer, DeleteSubscriberDataRequest, DeleteSubscriberDataAnswer, ResetRequest, ResetAnswer<br /> * HSSAuthentication : AuthenticationInfoRequest, AuthenticationInfoAnswer<br /> <br /> ==Generating and processing Diameter messages==<br /> <br /> While in active state, the application will receive XML Diameter-specific formatted messages for handling. It can also send messages, either as an answer to a previous incoming request or to generate a new outbound request.<br /> <br /> ==Preparing shutdown==<br /> <br /> <br /> When an application wishes to stop processing it should indicate to the translator to stop delivering messages for new requests/sessions. Messages for currently running requests will still be delivered.<br /> <br /> This is done by indicating lack of all capabilities in an empty &lt;c/&gt; element:<br /> &lt;m&gt;<br /> &lt;c/&gt;<br /> &lt;/m&gt;<br /> <br /> The converter will not answer at once, instead it will continue to deliver messages for existing requests/sessions. Eventually these requests will dry up and the new state will be applied:<br /> &lt;m&gt;<br /> &lt;state&gt;inactive&lt;/state&gt;<br /> &lt;/m&gt;<br /> <br /> At this point it is safe to close the socket.</div>

Oana https://ss7api.null.ro/index.php/Diameter_Introduction 2016-09-09T09:11:28Z

<p>Oana: </p> <hr /> <div>{{DISPLAYTITLE:Introduction}}<br /> <br /> The purpose of this document is to describe the XML based protocol used to implement communication between the YATE Diameter implementation and the Diameter application servers for mobile services so that exchange of Diameter information between YATE and application servers can be done over TCP connections.<br /> <br /> Diameter is an authentication, authorization, and accounting protocol for computer networks. In LTE, several Diameter applications are defined and used. <br /> The primary aim is to allow applications servers to handle and send Diameter commands regarding the S6a interface (MME - HSS interface).<br /> <br /> The aim of the protocol is to map Diameter commands from the interface and any other relevant information needed for the transport of the command to XML messages as transparently as possible.</div>

Oana https://ss7api.null.ro/index.php/SIM_Cards 2014-03-05T15:05:53Z

<p>Andrei: /* Terminal */</p> <hr /> <div><br /> ===SIM Events===<br /> <br /> ====Call Related Events and Requests====<br /> The following events are received by the SIM card when a call is made.<br /> *Standard: Details can be found in standard TS 31.111<br /> *Terminal Class: This events should work in all terminals.<br /> *Status: Tests were made successfully for Mobile Originating Calls<br /> *Events:&lt;br&gt;The SIM is notified on the following events:<br /> **Mobile Originating Call Initiated<br /> **Mobile Originating SMS Initiated<br /> **Mobile Originating USSD Initiated<br /> **Mobile Originating SS Initiated&lt;br&gt;On the events above, the 'address' and 'subaddress' parameters can be altered.<br /> *Notifications:&lt;br&gt;We can receive notifications for the following events.&lt;br&gt;NOTE: We can not alter the event flow. Eg. We can not keep the call alive if we received call terminated event.<br /> **Call Connected<br /> **Call Terminated<br /> *Requests - We can make the following requests:<br /> **Set Up Call<br /> **Send DTMF<br /> *Parameters:&lt;br&gt;The following parameters can be provided, can be altered or are provided by the terminal.<br /> **Address&lt;br&gt;The called party address. Details on TS 31.111 chapter 8.1<br /> **Subaddress&lt;br&gt;The called party subaddress. Details on TS 31.111 chapter 8.3<br /> <br /> ====Browsing====<br /> Open a SIM provided URL in phone's default browser.<br /> *Standard: Details can be fond in TS 102 223.<br /> *Terminal: This should work in a class C terminal.<br /> *Status: Not Tested<br /> *Events:&lt;br&gt;We are notified when one of the following events occures:<br /> **Status&lt;br&gt;Received when the browser receives a distant error from the network.<br /> **Terminated&lt;br&gt;Received when the browser is terminated.<br /> *Requests:<br /> **Lunch Browser&lt;br&gt;Ask a terminal to open a browser with the provided URL.<br /> <br /> ====Access Technology====<br /> Notification sent from the phone to inform about the access technology 2g/3g<br /> *Standard Details can be found in TS 102 223<br /> *Status: Not Tested<br /> *Events:<br /> **Changed&lt;br&gt;The access technology has changed from 2g/3g.<br /> <br /> ====Card Reader====<br /> Get events and perform actions on an additional card reader, <br /> *Standard: Details can be found in TS 102 223<br /> *Terminal Class A is required<br /> *Status: Not Tested<br /> *Events:<br /> **Status&lt;br&gt;Notification that a card was inserted or removed; or a card reader is available or unavailable.<br /> *Requests:<br /> **Power ON Card&lt;br&gt;Start a session with an additional card.<br /> **Power OFF Card&lt;br&gt;Stop a session with an additional card.<br /> **Perform Card APDU&lt;br&gt;Send an APDU command to an additional card.<br /> **Get Reader Status&lt;br&gt;Request to the terminal to provide additional information about additional card readers.<br /> <br /> ====Data====<br /> The following events and requests are available for data exchange.<br /> *Standard: more documentation can be found in TS 102 223<br /> *Status: In testing but no compatible device found!<br /> *Terminal class E is required<br /> *Events:<br /> **Data available&lt;br&gt;Notification from the terminal that data has arrived from the network.<br /> **Channel Status&lt;br&gt;Notification from the terminal that the channel status is changed.<br /> *Requests<br /> **Open Channel&lt;br&gt;Request to open a channel.<br /> **Send Data&lt;br&gt;Request to send data on a open channel.<br /> **Receive Data&lt;br&gt;Request to receive data on a open channel.<br /> **Close Channel&lt;br&gt;Request to close a open channel.<br /> <br /> ====User Interface====<br /> The following events and request are related to user interface.<br /> *Standard details can be found in standard TS 102 223<br /> *Status: Most of them were tested.<br /> *Events:<br /> **Display Parameter Change&lt;br&gt;Notification from the terminal when the screen is resized.<br /> **Frames Information Changed&lt;br&gt;Notification from the terminal when the frames are resized.&lt;br&gt;Requires terminal class I.<br /> **Idle screen available&lt;br&gt;Notification from the terminal that the screen is idle.<br /> **User activity&lt;br&gt;Notification from the terminal when the the user is interacting with the terminal.&lt;br&gt;This event is received only once after it was requested.<br /> **Menu Selection&lt;br&gt;Notification from the terminal when the user has selected a menu item.<br /> **Menu Selection Help Request&lt;br&gt;Notification from the terminal when the user requested help information on a menu.<br /> *Requests:<br /> **Get Input&lt;br&gt;Prompt the user to insert a text.<br /> **Get InKey&lt;br&gt;Prompt the user to insert a key.<br /> **Display Text&lt;br&gt;Prompt a text to the user.<br /> **Set Up Menu&lt;br&gt;Prompt a menu to the user.<br /> **Select Item&lt;br&gt;Provide a list of options to the user and instruct him to select one.<br /> **Set Up Idle Mode Text&lt;br&gt;Instruct the terminal to show the provided text when it is in idle mode.<br /> **Set Frames&lt;br&gt;Set the number of frames in which the terminal should devide its screen.&lt;br&gt;Requires terminal class I<br /> **Get Frame Status&lt;br&gt;Get the parameters of a frame.&lt;br&gt;Requires terminal class I<br /> <br /> ====SMS====<br /> SMS related procedures.<br /> *Standard details can be found in standard TS 131 111<br /> *Status: Not tested yet<br /> *Events:&lt;br&gt; Only OTA SMS are sent by the terminal to the SIM. Mobile Terminated SMS can not be intercepted by the SIM card.<br /> **SMS-Point to Point Data Download unformatted<br /> **SMS-Point to Point Data Download formatted<br /> **SMS-Cell Broadcast Data Download formatted<br /> **SMS-Cell Broadcast Data Download unformatted<br /> *Requests:<br /> **Send Short Message&lt;br&gt;Send a short message to the network.<br /> *Parameters<br /> **Address&lt;br&gt;The destination address.<br /> **SMS TPDU<br /> <br /> ====SS====<br /> Supplementary Services events and requests. <br /> *Standard Details can be found in TS 131 111<br /> *Terminal class P is required for USSD Data Download. All other operations should work on any device.<br /> *Status: Send USSD tested.<br /> *Events:<br /> **USSD Data Download formatted&lt;br&gt;Requires class P<br /> **USSD Data Download unformatted&lt;br&gt;Requires class P<br /> *Requests:<br /> **Send SS&lt;br&gt;Send a Supplementary Service request to the network.<br /> **Send USSD&lt;br&gt;Send a USSD Request to the network. Only the last response arrives in the SIM card. If the USSD request requires a menu USSD session, the user interaction will me required.<br /> *Parameters<br /> **SS String<br /> **USSD String<br /> <br /> ====IMS====<br /> The following events are dedicated for IMS.<br /> *Standard: Details can be found in TS 131 111<br /> *Terminal class E + T<br /> *Events<br /> **Download IMS Registration.&lt;br&gt;Notification from the terminal to download the IMS registration message.<br /> **Download Incoming IMS Data.&lt;br&gt;Notification from the terminal to download the incomming IMS message.<br /> *Parameters<br /> **IARI<br /> **IMPU List<br /> **IMS status code<br /> <br /> ====Terminal====<br /> Terminal related events and requests.<br /> *Standard: details can be found in TS 102 223 and TS 131 111<br /> *Events<br /> **Location Status&lt;br&gt;Notification from the terminal that it has changed its location.&lt;br&gt;Status: tested&lt;br&gt;Parameters:<br /> ***Location Status: details can be found in TS 102.223 8.27<br /> ***Location Information: details can be found in TS 102.223 8.19<br /> **Language Selection&lt;br&gt;Notification from the terminal that the current used language has changed.<br /> **Network Reject&lt;br&gt;Notification from the terminal that the network has rejected a request.<br /> **Timer expiration&lt;br&gt;Notification from the terminal that a requested timer has expired.<br /> *Requests<br /> **Provide Local Information&lt;br&gt;Request to the terminal to provide location information.<br /> ***the mobile country code (MCC), mobile network code (MNC), location area code/tracking area code (LAC/TAC) and cell ID of the current serving cell;&lt;br&gt;NOTE: For UTRAN the cell ID returned in terminal response is the last known cell ID which may not be the current serving cell, when the ME is on a dedicated channel.<br /> ***the IMEI or IMEISV of the ME;<br /> ***the Network Measurement Results (and the BCCH channel list if connected to GERAN);<br /> ***the current date, time and time zone;<br /> ***the current ME language setting;<br /> ***the Timing Advance, suitable only for GERAN;<br /> ***the current access technology;<br /> ***the current network search mode;<br /> ***the charge state of the battery (if class &quot;g&quot; is supported);<br /> ***the WSID of the current I-WLAN connection;<br /> ***The CSG ID list and corresponding HNB names (if available in the broadcasted information to the ME) of detected CSG or Hybrid cells in the Allowed CSG list or the Operator CSG list (if class &quot;q&quot; is supported);<br /> ***The H(e)NB IP address. (if class &quot;v&quot; is supported);<br /> ***The list of location information for surrounding macrocells (if class &quot;w&quot; is supported).<br /> <br /> **Language Notification&lt;br&gt;Inform the terminal what language will be used in this session.<br /> **Geographical Location Request&lt;br&gt;Ask the terminal to provide advanced geographical location.&lt;br&gt;Terminal type N is required.<br /> **More Time&lt;br&gt;Request to terminal for more processing time. <br /> **Refresh&lt;br&gt;Request to terminal to reinitialize SIM card.<br /> **Timer Management&lt;br&gt;Request to the terminal to emit a timer event after the specified time interval.<br /> <br /> ====Service====<br /> Commands dedicated for terminal services.<br /> *Standard: details can be found in TS 102 223<br /> *Status: not tested<br /> *Terminal class F is required.<br /> *Requests:&lt;br&gt;The following requests are available:<br /> **Declare Service&lt;br&gt;Inform the terminal about a service supported by the SIM.<br /> **Search Service&lt;br&gt;Search for a specific service in terminal's database.<br /> **Get Service Information&lt;br&gt;Request to the terminal to provide information about a specific service.<br /> <br /> ====MMS====<br /> MMS Related requests.<br /> *Standard details can be found in TS 102 223<br /> *Status: not tested<br /> *Terminal class J required<br /> *Requests:<br /> **Retreive MMS&lt;br&gt;Request the terminal to retreive the MMS from the network with the given MMS message reference.<br /> **Submit MMS&lt;br&gt;Request to terminal to submit the specified MM to the network.<br /> **Display MMS&lt;br&gt;Request to terminal to display a MMS.<br /> <br /> ===Card File System===<br /> <br /> ====USIM File System====<br /> Extracted from standard TS 131.102.<br /> *Language Indication<br /> *IMSI<br /> *Ciphering and Integrity Keys<br /> *Ciphering and Integrity Keys for Packet Switched domain<br /> *User controlled PLMN selector with Access Technology<br /> *Higher Priority PLMN search period<br /> *ACM maximum value<br /> *USIM Service Table<br /> *Accumulated Call Meter<br /> *Group Identifier Level 1<br /> *Group Identifier Level 2<br /> *Service Provider Name<br /> *Price per Unit and Currency Table<br /> *Cell Broadcast Message identifier selection<br /> *Access Control Class<br /> *Forbidden PLMNs<br /> *Location Information<br /> *Administrative Data<br /> *Cell Broadcast Message Identifier for Data Download<br /> *Emergency Call Codes<br /> *Cell Broadcast Message Identifier Range selection<br /> *Packet Switched location information<br /> *Fixed Dialling Numbers<br /> *Short messages<br /> *MSISDN<br /> *Short message service parameters<br /> *SMS status<br /> *Service Dialling Numbers<br /> *Extension2<br /> *Extension3<br /> *Short message status reports<br /> *Incoming Call Information<br /> *Outgoing Call Information<br /> *Incoming Call Timer<br /> *Outgoing Call Timer<br /> *Extension5<br /> *Capability Configuration Parameters 2<br /> *enhanced Multi Level Precedence and Pre-emption<br /> *Automatic Answer for eMLPP Service<br /> *Key for hidden phone book entries<br /> *Barred Dialling Numbers<br /> *Extension4<br /> *Comparison Method Information<br /> *Enabled Services Table<br /> *Access Point Name Control List<br /> *Depersonalisation Control Keys<br /> *Co-operative Network List<br /> *Initialisation values for Hyperframe number<br /> *Maximum value of START<br /> *Operator controlled PLMN selector with Access Technology<br /> *HPLMN selector with Access Technology<br /> *Access Rule Reference<br /> *Network Parameters<br /> *PLMN Network Name<br /> *Operator PLMN List<br /> *Mailbox Dialling Numbers<br /> *Extension6<br /> *Mailbox Identifier<br /> *Message Waiting Indication Status<br /> *Call Forwarding Indication Status<br /> *Extension7<br /> *Service Provider Display Information<br /> *MMS Notification<br /> *Extension 8<br /> *MMS Issuer Connectivity Parameters<br /> *MMS User Preferences<br /> *MMS User Connectivity Parameters<br /> *Network's Indication of Alerting<br /> *Voice Group Call Service<br /> *Voice Group Call Service Status<br /> *Voice Broadcast Service<br /> *Voice Broadcast Service Status<br /> <br /> ===Terminal profile===<br /> ====Description====<br /> The terminal can be interrogated about which functions it supports.<br /> #First byte (Download):<br /> ##Profile download<br /> ##SMS-PP data download<br /> ##Cell Broadcast data download)<br /> ##Menu selection<br /> ##SMS-PP data download<br /> ##Timer expiration<br /> ##USSD string data object support in Call Control by USIM<br /> ##Call Control by NAA<br /> #Second byte (Other):<br /> ##Command result<br /> ##Call Control by NAA<br /> ##Call Control by NAA <br /> ##MO short message control support<br /> ##Call Control by NAA<br /> ##UCS2 Entry supported<br /> ##UCS2 Display supported<br /> ##Display Text<br /> #Third byte (Proactive UICC):<br /> ##DISPLAY TEXT<br /> ##GET INKEY<br /> ##GET INPUT<br /> ##MORE TIME<br /> ##PLAY TONE<br /> ##POLL INTERVAL<br /> ##POLLING OFF<br /> ##REFRESH<br /> #Fourth byte (Proactive UICC):<br /> ##Proactive UICC: SELECT ITEM<br /> ##Proactive UICC: SEND SHORT MESSAGE with 3GPP-SMS-TPDU<br /> ##Proactive UICC: SEND SS<br /> ##Proactive UICC:SEND USSD<br /> ##Proactive UICC: SET UP CALL<br /> ##Proactive UICC: SET UP MENU<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (MCC, MNC,LAC, Cell ID &amp; IMEI)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (NMR)<br /> #Fifth byte (Event driven information):<br /> ##Proactive UICC: SET UP EVENT LIST<br /> ##Event: MT call<br /> ##Event: Call connected<br /> ##Event: Call disconnected<br /> ##Event: Location status<br /> ##Event: User activity<br /> ##Event: Idle screen available<br /> ##Event: Card reader status<br /> #Sixth byte (Event driven information extensions):<br /> ##Language selection<br /> ##Browser Termination<br /> ##Data available<br /> ##Channel status<br /> ##Access Technology Change<br /> ##Display parameters changed<br /> ##Local Connection<br /> ##Network Search Mode Change<br /> #Seventh byte (Multiple card proactive commands) for class &quot;a&quot;:<br /> ##POWER ON CARD<br /> ##POWER OFF CARD<br /> ##PERFORM CARD APDU<br /> ##GET READER STATUS (Card reader status)<br /> ##GET READER STATUS (Card reader Identifier)<br /> ##RFU<br /> #Eighth byte (Proactive UICC):<br /> ##Proactive UICC: TIMER MANAGEMENT (start, stop)<br /> ##Proactive UICC: TIMER MANAGEMENT (get current value)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (date, time and time zone)<br /> ##GET INKEY<br /> ##SET UP IDLE MODE TEXT<br /> ##RUN AT COMMAND (i.e. class &quot;b&quot; is supported)<br /> ##SETUP CALL<br /> ##Call Control by NAA<br /> #Ninth byte:<br /> ##DISPLAY TEXT<br /> ##SEND DTMF command<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (language)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION, Timing Advance<br /> ##Proactive UICC: LANGUAGE NOTIFICATION<br /> ##Proactive UICC: LAUNCH BROWSER<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (Access Technology)<br /> #Tenth byte (Soft keys support) for class &quot;d&quot;:<br /> ##Soft keys support for SELECT ITEM<br /> ##Soft Keys support for SET UP MENU<br /> ##RFU<br /> #Eleventh byte (Soft keys information):<br /> ##Maximum number of soft keys available 'FF' value is reserved for future use<br /> #Twelfth byte:<br /> ##OPEN CHANNEL<br /> ##CLOSE CHANNEL<br /> ##RECEIVE DATA<br /> ##SEND DATA<br /> ##GET CHANNEL STATUS<br /> ##SERVICE SEARCH<br /> ##GET SERVICE INFORMATION<br /> ##DECLARE SERVICE<br /> #Thirteenth byte:<br /> ##CSD<br /> ##GPRS<br /> ##Bluetooth<br /> ##IrDA<br /> ##RS232<br /> ##b6,b7,b8 - Number of channels supported by terminal<br /> #Fourteenth byte (Screen height):<br /> ##b1 - b4 - Number of characters supported down the terminal display as defined in clause 5.3.1<br /> ##No display capability (i.e class &quot;ND&quot; is indicated)<br /> ##No keypad available (i.e. class &quot;NK&quot; is indicated)<br /> ##Screen Sizing Parameters supported as defined inclause 5.3<br /> #Fifteenth byte (Screen width):<br /> ##b1-b7 - Number of characters supported across the terminal display as defined in clause 5.3.2<br /> ##Variable size fonts<br /> #Sixteenth byte (Screen effects):<br /> ##Display can be resized as defined in clause 5.3.3<br /> ##Text Wrapping supported as defined in clause 5.3.4<br /> ##Text Scrolling supported as defined in clause 5.3.5<br /> ##Text Attributes supported as defined in clause 5.3.7<br /> ##b5 - RFU<br /> ##b6 - b8 - Width reduction when in a menu as defined in clause 5.3.6<br /> #Seventeenth byte:<br /> ##TCP, UICC in client mode, remote connection<br /> ##UDP, UICC in client mode, remote connection<br /> ##TCP, UICC in server mode<br /> ##TCP, UICC in client mode, local connection (i.e. class &quot;k&quot; is supported)<br /> ##UDP, UICC in client mode, local connection (i.e. class &quot;k&quot; is supported)<br /> ##RFU, bit = 0<br /> ##E-UTRAN (if class &quot;e&quot; issupported))<br /> ##HSDPA (if class &quot;e&quot; is supported))<br /> #Eighteenth byte:<br /> ##Proactive UICC: DISPLAY TEXT (Variable Time out)<br /> ##Proactive UICC: GET INKEY (help is supported while waiting for immediate response or variable timeout)<br /> ##USB<br /> ##Proactive UICC: GET INKEY (Variable Timeout)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (ESN)<br /> ##Call control on GPRS<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (IMEISV)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (Search Mode change)<br /> #Nineteenth byte (reserved for TIA/EIA-136-C facilities [25]):<br /> ##Reserved by TIA/EIA-136 [25] (Protocol Version support)<br /> ##RFU, bit = 0<br /> #Twentieth byte (reserved for TIA/EIA/IS-820-A facilities [17]):<br /> ##Reserved by TIA/EIA/IS-820 [17]<br /> #Twenty-first byte (Extended Launch Browser Capability) for class &quot;c&quot;:<br /> ##WML<br /> ##XHTML<br /> ##HTML<br /> ##CHTML<br /> ##RFU, bit = 0<br /> #Twenty-second byte:<br /> ##Support of UTRAN PS with extended parameters<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION(battery state), (i.e. class &quot;g&quot; is supported)<br /> ##Proactive UICC: PLAY TONE (Melody tones and Themed tones supported)<br /> ##Multi-media Calls in SET UP CALL (if class h supported)<br /> ##Reserved by 3GPP (Toolkit-initiated GBA)<br /> ##Proactive UICC: RETRIEVE MULTIMEDIA MESSAGE (if class &quot;j&quot; is supported)<br /> ##Proactive UICC: SUBMIT MULTIMEDIA MESSAGE (if class &quot;j&quot; is supported)<br /> ##Proactive UICC: DISPLAY MULTIMEDIA MESSAGE (if class &quot;j&quot; is supported)<br /> #Twenty third byte:<br /> ##Proactive UICC: SET FRAMES (i.e. class &quot;i&quot; is supported)<br /> ##Proactive UICC: GET FRAMES STATUS (i.e. class &quot;i&quot; is supported)<br /> ##MMS notification download (if class &quot;j&quot; is supported)<br /> ##Alpha Identifier in REFRESH command supported by terminal<br /> ##Geographical Location Reporting (if class &quot;n&quot; is supported)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (MEID)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (NMR(UTRAN))<br /> ##USSD Data download and application mode<br /> #Twenty fourth byte for class &quot;i&quot;:<br /> ##b1-b4 - Maximum number of frames supported (including frames created in existing frames)<br /> ##RFU, bit = 0<br /> #Twenty-fifth byte (Event driven information extensions):<br /> ##Event: Browsing status<br /> ##Event: MMS Transfer status (if class &quot;j&quot; is supported)<br /> ##Event: Frame Parameters changed (i.e. class &quot;i&quot; is supported)<br /> ##Event: I-WLAN Access status (if class &quot;e&quot; is supported)<br /> ##Event Network Rejection<br /> ##Event: HCI connectivity event (i.e. class &quot;m&quot; is supported)<br /> ##Reserved by 3GPP (E-UTRAN support in Event Network Rejection)<br /> ##Multiple access technologies supported in Event<br /> ##Access Technology Change and PROVIDE LOCAL INFORMATION &lt;br&gt;If bit &quot;Multiple access technologies supported&quot; is set to 1, it applies to the Event Access Technology Change if supported and all relevant modes of proactive command PROVIDE LOCAL INFORMATION that are supported.<br /> #Twenty-sixth byte (Event driven information extensions):<br /> ##RFU, bit = 0 (for future event indication)<br /> #Twenty-seventh byte (Event driven information extensions):<br /> ##RFU, bit = 0 (for future event indication)<br /> #Twenty-eighth byte (Text attributes):<br /> ##Alignment left supported by Terminal<br /> ##Alignment centre supported by Terminal<br /> ##Alignment right supported by Terminal<br /> ##Font size normal supported by Terminal<br /> ##Font size large supported by Terminal<br /> ##Font size small supported by Terminal<br /> ##RFU, bit = 0<br /> #Twenty-ninth byte (Text attributes):<br /> ##Style normal supported by Terminal<br /> ##Style bold supported by Terminal<br /> ##Style italic supported by Terminal<br /> ##Style underlined supported by Terminal<br /> ##Style strikethrough supported by Terminal<br /> ##Style text foreground colour supported by Terminal<br /> ##Style text background colour supported by Terminal<br /> ##RFU, bit = 0<br /> #Thirtieth byte:<br /> ##I-WLAN bearer support (if class &quot;e&quot; is supported)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (WSID of the current I-WLAN connection)<br /> ##TERMINAL APPLICATIONS (i.e. class &quot;k&quot; is supported)<br /> ##Steering of Roaming REFRESH support<br /> ##Proactive UICC: ACTIVATE (i.e class &quot;l&quot; is supported)<br /> ##Proactive UICC: GEOGRAPHICAL LOCATION REQUEST (if class &quot;n&quot; is supported)<br /> ##Proactive UICC: PROVIDE LOCAL INFORMATION (Broadcast Network Information) (i.e. class &quot;o&quot; is supported)<br /> ##Steering of Roaming for I-WLAN REFRESH support<br /> <br /> ====Values====<br /> {| class=&quot;wikitable&quot; style=&quot;text-align: center;&quot;<br /> |Phone Type||B1||B2||B3||B4||B5||B6||B7||B8||B9||B10||B11||B12||B13||B14||B15||B16||B17||B18||B19||B20||B21||B22||B23||B24||B25||B26||B27||B28||B29||B30<br /> |-<br /> |Samsung Galaxy Express||ff||ff||ff||ff||7f||9d||00||df||bf||00||00||1f||e2||00||00||00||c3||6b||00||07||00||00||40||00||50||00||00||00||00||08<br /> |-<br /> |Samsung Galaxy Note 3||ff||ff||ff||ff||7f||9d||00||df||bf||00||00||1f||e2||00||00||00||c3||6b||00||07||00||00||40||00||50||00||00||00||00||08<br /> |-<br /> |HTC One X+||ff||ff||ff||ff||7f||1d||00||df||b7||03||02||1f||22||00||00||00||83||00||00||00||00||00||40||10||00||00||00||00||00||00<br /> |-<br /> |IPhone 4||ff||ff||ff||ff||7f||91||00||df||bf||00||00||00||00||00||00||00||00||f0||00||03||00||00||60||00||50||00||00||00||00||00<br /> |-<br /> |Nokia E72||ff||ff||ff||ff||7f||1d||00||df||bf||00||00||17||e2||05||0f||00||03||09||00||00||00||00||00||00||00||00||00||00||00||00<br /> |}</div>

Andrei https://ss7api.null.ro/index.php/USSD_GW 2013-11-06T10:36:26Z

<p>Oana: /* Keyword values */</p> <hr /> <div>This is an implementation an USSD gateway acting as a MAP Service Control Function (gsmSCF) and as a HLR at the same time. When communicating with a HLR or VLR, the YATE USSD GW acts as a gsmSCF. When communicating with a gsmSCF, the YATE USSDGW acts as a HLR.<br /> The functionality of the USSD GW allows:<br /> * redirecting of USSD requests arriving either from user side or gsmSCF side to a SMPP client where they can be altered.<br /> * acting as a proxy for requests that need not be handled by SMPP clients or when the SMPP handling fails<br /> <br /> <br /> == MAP USSD description ==<br /> <br /> In versions 2 and 3 of the GSM MAP protocol there are 3 operations used for USSD operations:<br /> * processUnstructedSS-Request<br /> * unstructuredSS-Request<br /> * unstrusturedSS-Notify<br /> <br /> The are 2 scenarios for USSD operations:<br /> * mobile initiated USSD requests<br /> * network initiated USSD requests<br /> <br /> A TCAP dialog used by USSD is always terminated by the network side.<br /> <br /> <br /> === Mobile initiated USSD requests ===<br /> <br /> <br /> Mobile initiated USSD requests are USSD requests started by the mobile subscriber. <br /> <br /> A USSD request is started when receiving a TCAP BEGIN message containing the ''processUnstructedSS-Request'' Invoke operation. The request can be handled by the VLR, HLR or a gsmSCF. If the VLR does not handle the request, it will transmit it to the HLR. The HLR can either handle it itself or it can transmit it to a gsmSCF for handling.<br /> <br /> At this point, the network can either send a response to the request immediately or request additional information. In the first case, the handler of the request will send a TCAP End with ''processUnstructuredSS-Request'' ResultLast containing the result for the request. <br /> In the latter case, the network will send a TCAP CONTINUE with ''unstructuredSS-Request'' Invoke operation. The response of the mobile subscriber to this request will be passed to the network in a TCAP CONTINUE with ''unstructuredSS-Request'' ResultLast component. At this point, if the network decides that it has enough information for providing the response to the user, it will send a TCAP END with ''processUnstructuredSS-Request'' ResultLast. Otherwise, it can request further information through another ''unstructuredSS-Request'' Invoke operation.<br /> <br /> === Network initiated USSD requests ===<br /> <br /> <br /> Network initiated USSD requests are USSD requests started by the network towards a certain subscriber.<br /> <br /> Requests made by the network can be of one of two types:<br /> * user interaction requests<br /> * network notification requests.<br /> <br /> User interaction requests are USSD requests that the network makes in which it requires some type of information back from the mobile subscriber. These are started by the network through a TCAP BEGIN containing an ''unstructuredSS-Request'' Invoke. The answer from the mobile subscriber will be received in a TCAP CONTINUE containing an ''unstructuredSS-Request'' ResultLast. If the network still wants to request further information from the user it can send another ''unstructuredSS-Request'' Invoke in a TCAP CONTINUE and wait for the answer. Once the network obtains all needed information, but wants (for user friendliness) to notify the user about the result of the operations, it can send: <br /> * a TCAP CONTINUE containing a ''unstructuredSS-Notify'' Invoke. When the user side respond with a TCAP CONTINUE containing an empty ''unstructuredSS-Notify'', the network can close the dialog through a TCAP END<br /> * if the network is not interested in the outcome of ''unstructuredSS-Notify'' Invoke operation, it can send a TCAP END containing ''unstructuredSS-Notify'' invoke.<br /> If there is nothing to notify to the user, the network can send a TCAP END to close the TCAP dialog.<br /> <br /> <br /> <br /> Network notification requests are USSD requests in which the network only sends a notification to the user. This is achieved by sending a TCAP BEGIN message containing a ''unstructuredSS-Notify'' Invoke. The mobile subscriber side will only respond with a TCAP CONTINUE containing an empty ''unstructuredSS-Notify'' in order to signal that the notification was received. The network will close the TCAP dialog through TCAP END.<br /> <br /> === MAP USSD parameters ===<br /> <br /> <br /> The following list describe common parameters used across all MAP USSD operations:<br /> * ''destinationReference'': this parameter will contain either an MSISDN or an IMSI. In the case of mobile originated USSD request, this will identify the user which made the request. In the case of network initiated requests, it will identify the mobile user to be contacted for this request.<br /> * ''ussd-String'': for ''processUnstructuredSS-Request'' Invoke it contains the dialed USSD code, for the result it would probably contain a message from the network detailing the result of the request. For ''unstructuredSS-Request'' Invoke it will contain a message asking for the user to choose some option and for the result it will contain the option chosen by the user. In the case of ''unstructuredSS-Notify'', this parameter will only be present in the Invoke.<br /> * ''ussd-DataCodingScheme'': this is a parameter which specifies in which way the ''ussd-String'' parameter is encoded and it is present whenever ''ussd-String'' is present. E.g., this parameter would indicate if the ''ussd-String'' is encoded using GSM7bit encoding or UCS2.<br /> <br /> == SMPP USSD description ==<br /> <br /> '''TO DO'''<br /> <br /> == System description ==<br /> <br /> <br /> === System design ===<br /> <br /> In order to provide the specified functionality, the system makes use of the following YATE components:<br /> * the SS7 stack present in YATE <br /> * the camel_map module which decodes/encodes MAP messages coming from the SS7 network to/from internal YATE messages containing MAP operations in XML form. Together with the SS7 layer this provides MAP connectivity with HLR/gsmSCF.<br /> * the ussd_map module which takes internal MAP messsages decoded by the camel_map moduled and translates them to internal USSD messages. This module acts as gsmSCF towards a HLR and as a HLR towards a gsmSCF.<br /> * the SMPP stack present in YATE (ysmpp module) which is able to catch internal USSD messages and transmit them over SMPP. It also translates SMPP messages into internal USSD messages.<br /> * requests for new USSD sessions will go through routing to decide who should handle the request.<br /> <br /> <br /> The following sections detail the behaviour of the system in the different USSD scenarios.<br /> <br /> <br /> ==== Mobile originated USSD handling ====<br /> <br /> <br /> A user initiated USSD session is handled according to the following schema:<br /> <br /> <br /> [[File:user_initiated_ussd.png]]<br /> <br /> <br /> # HLR sends a ''processUnstructuredSS-Request (Invoke)'' for code *100#. camel_map decodes the ''ussd-String'' into ''ussd-Text=*100#''.<br /> # the ussd_map module (gsmSCF side) processes the request received from the HLR and emits a ''call.route'' message with ''called=*100#''.<br /> # After ussd_map module successfully dispatched the call.route message, it generates a ''ussd.execute'' message with the ''callto'' parameter set to the value returned from routing. ussd_map dispatches the ''ussd.execute'' message.<br /> # The ysmpp module catches the ''ussd.execute'' message and if the ''callto'' param value starts with ''ysmppserver/'' and with it it builds a ''deliver_sm'' message that it will send it to the target specified in ''callto'' parameter after the module prefix ''ysmppserver/''.<br /> # The ysmpp module receives and process the received ''submit_sm'' message.<br /> # The ysmpp module will send a ''call.route'' message with the ''called=*100#''.<br /> # The ysmpp module emits a ''ussd.execute'' message with ''callto=retvalue from call.route'' message.<br /> # The ussd_map module (HLR part) processes the ussd.execute message and if it is the target of the message, meaning that ''callto'' starts with ''ussd_map/''. From that message it will build a map.message that it will send to the gsmSCF as a ''processUnstructuresSS-Request (Invoke)'' MAP message.&lt;br&gt;'''NOTE:''' From here on, the gsmSCF could handle the request in one of two distinguished cases: one where the gsmSCF requires interaction with the mobile subscriber and one where the gsmSCF just needs to respond to the user request. The following steps detail the former case.&lt;br&gt;<br /> # gsmSCF sends an ''unstructuredSS-Request (Invoke)'' to request further information.<br /> # The ussd_map module (HLR part) processes the ''unstructuredSS-Request (Invoke)'' message and emits an ''ussd.update'' message.<br /> # The ysmpp module receives the ''ussd.update'' message and confirms to the SMPP client that the message sent in step 5 was processed.<br /> # The SMPP client should confirm the processing of the SMPP message sent in step 4.<br /> # The ysmpp module sends a ''deliver_sm'' message to the SMPP client with the menu received in ''ussd.update'' message.<br /> # The SMPP client should send a ''submit_sm'' message with the received menu.<br /> # The ysmpp module receives the ''submit_sm'' message from SMPP client and emits a ''ussd.update'' message.<br /> # The ussd_map module (SCF part) process the ''ussd.update'' message and sends an ''unstructuredSS-Request (Invoke)'' towards the HLR.&lt;br&gt;The time in which the mobile subscribers responds can be quite long.&lt;br&gt;<br /> # The HLR sends ''unstructuredSS-Request (ResultLast)'' to USSD gateway when receiving the response from the mobile subscriber.<br /> # The ussd_map module (SCF part) processes the message and emits a ''ussd.update'' message.<br /> # ysmpp module processes the ''ussd.update'' message and sends ''submit_sm rsp'' to SMPP client to confirm the reception of the message sent on step 14.<br /> # The SMPP client should send a ''deliver_sm rsp'' to confirm the message received on step 13.<br /> # The ysmpp module will send a deliver_sm message to SMPP clients which will contain user's response.<br /> # The SMPP client should send a ''submit_sm'' message to SMPP server which will contain the message received on step 21.<br /> # The ysmpp module receives the ''submit_sm'' message and emits a ''ussd.update'' message.<br /> # The ussd_map module (HLR part) receives the ''ussd.update'' message and sends the ''unstructuredSS-Request (ResultLast)'' to gsmSCF.&lt;br&gt;'''NOTE:''' Steps between 9 and 24 can be repeated.&lt;br&gt;<br /> # The gsmSCF sends ''processUnstructuredSS-Request (ResultLast)'' for the initial user request.<br /> # The ussd_map module (HLR part) processes the ''processUnstructuredSS-Request (ResultLast)'' and sends a ''ussd.finalize'' message.<br /> # The ysmpp module receives the ''ussd.finalize'' message and sends a ''submit_sm rsp'' for the message received on point 22 or 5.<br /> # The SMPP client should send a ''deliver_sm rsp'' for the message received on point 21 or 4.<br /> # The ysmpp module sends a ''deliver sm + last message indication'' to SMPP client.<br /> # The SMPP client should send a ''submit sm + last message indication'' to SMPP server.<br /> # ysmpp module receives ''submit_sm'' message and sends a ''ussd.finalize'' message.<br /> # ysmpp module sends ''submit_sm rsp'' to confirm the message received on step 31.<br /> # SMPP client should send a ''deliver_sm rsp'' to confirm the message received on step 29.<br /> # The ussd_map module (SCF part) processes the ''ussd.finalize'' message and sends ''processUnstructuredSS-Request (ResultLast)''.<br /> <br /> ==== Network initiated USSD Request ====<br /> <br /> A network initiated USSD session is handled as described in the following figure:<br /> <br /> [[File:network_initiated_ussd.png]]<br /> <br /> # gsmSCF sends''unstructuredSS-Request (Invoke)'' to USSD Gateway (HLR part) to present a menu for MSISDN 0015559191.<br /> # The ussd_map module (HLR part) processes the ''unstructuredSS-Request (Invoke)'' message and emits a ''call.route'' message with called=0015559191. <br /> # After ussd_map module successfully dispatched the call.route message, it generates a ''ussd.execute'' message with ''callto'' set to the route returned in the return value of the ''call.route'' message and dispatches an ''ussd.execute'' message.<br /> # The ysmpp module catches the ''ussd.execute'' message and if the ''callto'' param value starts with ''ysmppserver/'' and with it it builds a ''deliver_sm'' message that it will then send to the target specified in the ''callto'&quot; parameter after the ''ysmppserver'' module prefix.<br /> # The SMPP client should send a ''submit_sm'' message towards SMPP server.<br /> # The SMPP server processes the received ''submit_sm'' message and dispatches a ''call.route'' message.<br /> # After successfully dispatching of ''call.route'' message the SMPP server will dispatch a ''call.execute'' message.<br /> # The ussd_map module (SCF part) process the ''ussd.execute'' message and sends an ''unstructuredSS-Request (Invoke)'' towards the HLR.&lt;br&gt;The time to receiving a response from the user after gsmSCF has requested user interaction could be possibly quite long.&lt;br&gt;<br /> # The HLR sends ''unstructuredSS-Request (ResultLast)'' to USSD gateway <br /> # The ussd_map module (SCF part) processes the message and emits a ''ussd.update'' message.<br /> # ysmpp module processes the ''ussd.update'' message and sends ''submit_sm rsp'' to SMPP client to confirm the reception of the message sent on step 5.<br /> # The SMPP client should send a ''deliver_sm rsp'' to confirm the message received on step 4.<br /> # The ysmpp module will send a deliver_sm message to SMPP clients which will contain user's response.<br /> # The SMPP client should send a ''submit_sm'' message to SMPP server which will contain the message received on step 13.<br /> # The ysmpp module receives the ''submit_sm'' message and emits a ''ussd.update'' message.<br /> # The ussd_map module (HLR part) receives the ''ussd.update'' message and sends the ''unstructuredSS-Request (ResultLast)'' to gsmSCF.&lt;br&gt;'''NOTE:''' Steps between 1 and 16 can be repeated.&lt;br&gt;<br /> # The gsmSCF sends ''TCAP END'' in order to finish the USSD session.<br /> # The ussd_map module (HLR part) processes the ''TCAP END'' and sends a ''ussd.finalize'' message.<br /> # The ysmpp module receives the ''ussd.finalize'' message and sends a ''submit_sm rsp'' for the message received on point 14.<br /> # The SMPP client should send a ''deliver_sm rsp'' for the message received on point 13.<br /> # The ysmpp module sends a ''deliver sm + last message indication'' to SMPP client.<br /> # The SMPP client should send a ''submit sm + last message indication'' to SMPP server.<br /> # ysmpp module sends ''submit_sm rsp'' to confirm the message received on step 22.<br /> # SMPP client should send a ''deliver_sm rsp'' to confirm the message received on step 21.<br /> # ysmpp module receives ''submit_sm'' message and sends a ''ussd.finalize'' message.<br /> # The ussd_map module (SCF part) processes the ''ussd.finalize'' message and sends ''END''.<br /> <br /> <br /> <br /> <br /> <br /> ==== Fallback/Proxy mode ====<br /> <br /> <br /> The following images detail scenarios where the USSD GW is instructed to do failover.<br /> <br /> <br /> <br /> [[File:user_initiated_failover.png]]<br /> <br /> The picture above details a failover scenario for when an HLR sends ''processUnstructuredSS-Request (Invoke)'' (1).<br /> <br /> '''NOTES:''' <br /> * The read circles in the above picture represent points in handling where a fallback decision can be made.<br /> * A fallback decision can be made only if in all previous fallback decision points the necessity for failover was determined to be false.<br /> * '''U1''' and '''U2''' represent SMPP message responses.<br /> <br /> <br /> Decision points where ''ussd_map'' will determine the need for failover:<br /> *'''E1''': Routing procedure does not return a valid route (''call.route'' returns with false or an error) or routing decision indicates a failover route (routing return a route starting with prefix ''ussd_map/'')<br /> *'''E2''': ''ussd.execute'' message fails to be processed (in this case by the ysmpp module)<br /> *'''E3''': SMPP server received an SMPP error for ''deliver_sm'' message. <br /> *'''E4''': SMPP client received an SMPP error for ''submit_sm'' message.<br /> *'''E5''': The ''call.route'' message emitted by ''ysmpp'' does not return a valid route (''call.route'' returns with false or an error).<br /> *'''E6''': ''ussd.execute'' message fails to be processed (in this case by the ussd_map module).<br /> <br /> <br /> <br /> Network initiated USSD session fallback.<br /> <br /> [[File:network_initiated_failover.png]]<br /> <br /> The picture above details a failover scenario for when a gsmSCF sends a &quot;unstructuredSS-Request/unstructuredSS-Notify (Invoke)'' (1).<br /> <br /> '''NOTES:'''<br /> * The read circles in the above picture represent points in handling where a fallback decision can be made.<br /> * A fallback decision can be made only if in all previous fallback decision points the necessity for failover was determined to be false.<br /> * '''U1''' and '''U2''' represent SMPP message responses.<br /> <br /> Decision points where ''ussd_map'' will determine the need for failover:<br /> *'''E1''': Routing procedure does not return a valid route (''call.route'' returns with false or an error) or routing decision indicates a failover route (routing return a route starting with prefix ''ussd_map/'')<br /> *'''E2''': ''ussd.execute'' message fails to be processed (in this case by the ysmpp module)<br /> *'''E3''': SMPP server received an SMPP error for ''deliver_sm'' message.<br /> *'''E4''': SMPP client received an SMPP error for ''submit_sm'' message.<br /> *'''E5''': The ''call.route'' message emitted by ''ysmpp'' does not return a valid route (''call.route'' returns with false or an error).<br /> *'''E6''': ''ussd.execute'' message fails to be processed (in this case by the ussd_map module).<br /> <br /> <br /> The SMPP USSD gateway will also be bypassed when the ''ussd_map'' module is configured to do failover for all requests.<br /> <br /> Any type of SMPP error received either in the result for the ''ussd.execute'' or in the first message back from SMPP that does not have a mapping on MAP will lead to the ''ussd_map'' module doing failover. Errors that would generate a failover are errors like timeout, session ended abnormally, unknown errors, congestion errors.<br /> <br /> <br /> Once ''ussd_map'' decides that failover should be done, it will use the original received message from the HLR (MO case)/gsmSCF (MT case) and it will only alter the called address to be the one of the gsmSCF/HLR set for the failover.. The calling address will remain the one received from HLR/gsmSCF, the idea being that for the first message we want to pretend that we are the original gsmSCF/HLR. When the receiving end of this message will want to respond, it will use the calling address from the message. Seeing that the ''ussd_map'' module set it to the original calller's address, further messages exchanged in that dialog between HLR and gsmSCF will not pass through USSD GW again.<br /> <br /> <br /> <br /> ==== Internal message API ====<br /> <br /> This section documents the YATE messages used internally by the USSD GW.<br /> <br /> ===== call.route =====<br /> <br /> <br /> This message is used by ussd_map and ysmpp module to determine a destination where a new USSD session should be sent for further processing.<br /> <br /> This message is sent by either ''ussd_map'' module or ''ysmpp'' module when receiving a request for a new USSD session on MAP for ''ussd_map'' or on SMPP for ''ysmpp''.<br /> ''ussd_map'' will only send this message if default routing is not enabled from configuration.<br /> <br /> <br /> <br /> Parameters:<br /> * id:<br /> ** type: string<br /> ** Identifier for the USSD session used by the dispatcher of the message.<br /> * called:<br /> ** type: string<br /> ** It specifies the value on which destination is determined. For a MO USSD session, this parameter will contain the decoded USSD string (USSD request code). For a MT USSD sessions, this parameter will contain the destination MSISDN.<br /> * callednumtype:<br /> ** type: keyword<br /> ** It specifies type (NAI) of the called parameter. It is used only when called is a MSISDN<br /> * callednumplan:<br /> ** type: keyword<br /> ** Numbering plan for the number specified by the called parameter. It is used only when called is a MSISDN.<br /> * caller:<br /> ** type: string:<br /> ** Identifies the caller in this USSD session. For MO USSD it can be the MSISDN (if present) . ''ussd_map'' will set the the calling party address GT in this parameter for MT case or if MSISDN is not specified for MO case.<br /> * callernumtype:<br /> ** type: keyword<br /> ** It specifies type (NAI) of the caller parameter.<br /> * callernumplan:<br /> ** type: keyword<br /> ** Numbering plan for the number specified by the caller parameter.<br /> * operation_type:<br /> ** type: keyword<br /> ** The type of USSD operation that fired this message.<br /> * text_encoding:<br /> ** type: hexified string<br /> ** The MAP USSD data coding scheme<br /> * text_encoded:<br /> ** type: hexified string<br /> ** The encoded USSD string<br /> * text:<br /> ** type: string<br /> ** The decoded USSD string conforming to the USSD data coding scheme.<br /> * text.encoding:<br /> ** type: keyword<br /> ** The USSD data coding scheme.<br /> * text.lang:<br /> ** type: keyword<br /> ** The language of the decoded text as obtained from the data coding scheme.<br /> * text.lang_indication:<br /> ** type: boolean<br /> ** True if the language was decoded from the USSD string and not from the data coding scheme.<br /> * imsi:<br /> ** type: string<br /> ** IMSI value if available.<br /> * hlr:<br /> ** type: string<br /> ** It specifies the HLR GTT if that information was available.<br /> * hlr.nature:<br /> ** type: keyword<br /> ** It specifies HLR GTT nature (NAI)<br /> * hlr.plan:<br /> ** type: keyword<br /> ** It specifies HLR GTT numbering plan<br /> * vlr:<br /> ** type: string<br /> ** It specifies the VLR GTT if that information was available.<br /> * vlr.nature:<br /> ** type: keyword<br /> ** It specifies VLR GTT nature (NAI)<br /> * vlr.plan:<br /> ** type: keyword<br /> ** It specifies VLR GTT numbering plan<br /> * gsmscf:<br /> ** type: string<br /> ** It specifies the gsmSCF GTT if that information was available.<br /> * gsmscf.nature:<br /> ** type: keyword<br /> ** It specifies gsmSCF GTT nature (NAI)<br /> * gsmscf.plan:<br /> ** type: keyword<br /> ** It specifies gsmSCF GTT numbering plan<br /> * destination_reference:<br /> ** type: string<br /> ** MSISDN or IMSI specified in the DestinationReference TCAP MAP parameter.<br /> * destination_reference.nature:<br /> ** type: keyword<br /> ** It specifies DestinationReference nature (NAI)<br /> * destination_reference.plan:<br /> ** type: keyword<br /> ** It specifies DestinationReference numbering plan<br /> * msisdn:<br /> ** type: string<br /> ** MSISDN <br /> * alert_pattern:<br /> ** type: string<br /> ** Alert Pattern parameter as received in the USSD MAP message.<br /> * module<br /> ** type: string <br /> ** Name of the module which requested routing<br /> * application<br /> ** type: string<br /> ** Name of the ussd_map application which sent this routing request<br /> * route_type<br /> ** type: keyword, value: ussd <br /> ** Specifies routing type, in this case it'll be USSD routing<br /> * smpp_session_id<br /> ** type: string<br /> ** TODO<br /> * smpp_system_id<br /> ** type: string<br /> ** TODO<br /> <br /> Note:<br /> * The hlr/vlr address represents:<br /> ** the address from which the message was received (if it can be determined) for MO USSD session.<br /> ** the address where the message should be sent for MT USSD session.<br /> <br /> Returned parameters:<br /> * if the message was processed, the return value of the message indicates the destination of the subsequent ''ussd.execute'' message.<br /> * if the message was not processed or it returned with error (signaled by the return value being either &quot;-&quot; or &quot;error&quot;)<br /> ** ''ussd_map'' will do failover<br /> ** ysmpp will close the SMPP session, indicating an error either set by the call.route or either set to the default unknown error indication.<br /> <br /> ===== ussd.execute =====<br /> <br /> This message is used to begin a new USSD session:<br /> * on SMPP, if the message is directed to the ''ysmpp'' module<br /> * on MAP if the message is directed to the ''ussd_map'' module<br /> <br /> This message is sent by either ''ussd_map'' module or ''ysmpp'' module after successful routing stage. In case of the ''ussd_map'' module, this is message is sent if the routing stage did not indicate failover necessity.<br /> <br /> <br /> <br /> Parameters:<br /> * callto: <br /> ** type : string<br /> ** It specifies the target module to process the message. The string should start with 'ysmppserver/' for the ''ysmpp&quot; module and with ''ussd_map/'' for the ''ussd_map'' module.<br /> * id:<br /> ** type: string<br /> ** Identifier for the USSD session used by the dispatcher of the message.<br /> * called:<br /> ** type: string<br /> ** It specifies the value on which destination is determined. For a MO USSD session, this parameter will contain the decoded USSD string (USSD request code). For a MT USSD sessions, this parameter will contain the destination MSISDN.<br /> * callednumtype:<br /> ** type: keyword<br /> ** It specifies type (NAI) of the called parameter. It is used only when called is a MSISDN<br /> * callednumplan:<br /> ** type: keyword<br /> ** Numbering plan for the number specified by the called parameter. It is used only when called is a MSISDN.<br /> * caller:<br /> ** type: string:<br /> ** Identifies the caller in this USSD session. For MO USSD it can be the MSISDN (if present) . ''ussd_map'' will set the the calling party address GT in this parameter for MT case or if MSISDN is not specified for MO case.<br /> * callernumtype:<br /> ** type: keyword<br /> ** It specifies type (NAI) of the caller parameter.<br /> * callernumplan:<br /> ** type: keyword<br /> ** Numbering plan for the number specified by the caller parameter.<br /> * operation_type:<br /> ** type: keyword<br /> ** The type of USSD operation that fired this message.<br /> * text_encoding:<br /> ** type: hexified string<br /> ** The MAP USSD data coding scheme<br /> * text_encoded:<br /> ** type: hexified string<br /> ** The encoded USSD string<br /> ** '''NOTE''': If YATE uses in the internal messages the decoded text, this parameter should not be set (it has higher priority in ussd_map).<br /> * text:<br /> ** type: string<br /> ** The decoded USSD string conforming to the USSD data coding scheme.<br /> * text.encoding:<br /> ** type: keyword<br /> ** The USSD data coding scheme.<br /> * text.lang:<br /> ** type: keyword<br /> ** The language of the decoded text as obtained from the data coding scheme on MAP or from language indicator on SMPP.<br /> * text.lang_indication:<br /> ** type: boolean<br /> ** True if the language was decoded from the USSD string and not from the data coding scheme or if should be encoded on MAP in the USSD string payload.<br /> ** Set to false for UCS2 encoding without language indication<br /> * imsi:<br /> ** type: string<br /> ** IMSI value if available.<br /> * hlr:<br /> ** type: string<br /> ** It specifies the HLR GTT if that information was available.<br /> * hlr.nature:<br /> ** type: keyword<br /> ** It specifies HLR GTT nature (NAI)<br /> * hlr.plan:<br /> ** type: keyword<br /> ** It specifies HLR GTT numbering plan<br /> * vlr:<br /> ** type: string<br /> ** It specifies the VLR GTT if that information was available.<br /> * vlr.nature:<br /> ** type: keyword<br /> ** It specifies VLR GTT nature (NAI)<br /> * vlr.plan:<br /> ** type: keyword<br /> ** It specifies VLR GTT numbering plan<br /> * gsmscf:<br /> ** type: string<br /> ** It specifies the gsmSCF GTT if that information was available.<br /> * gsmscf.nature:<br /> ** type: keyword<br /> ** It specifies gsmSCF GTT nature (NAI)<br /> * gsmscf.plan:<br /> ** type: keyword<br /> ** It specifies gsmSCF GTT numbering plan<br /> * destination_reference:<br /> ** type: string<br /> ** MSISDN or IMSI specified in the DestinationReference TCAP MAP parameter.<br /> * destination_reference.nature:<br /> ** type: keyword<br /> ** It specifies DestinationReference nature (NAI)<br /> * destination_reference.plan:<br /> ** type: keyword<br /> ** It specifies DestinationReference numbering plan<br /> * msisdn:<br /> ** type: string<br /> ** MSISDN <br /> * alert_pattern:<br /> ** type: string<br /> ** Alert Pattern parameter as received in the USSD MAP message.<br /> <br /> Note:<br /> * The hlr/vlr address represents:<br /> ** the address from which the message was received (if it can be determined) for MO USSD session.<br /> ** the address where the message should be sent for MT USSD session.<br /> <br /> Returned parameters:<br /> * peerid:<br /> ** type: string<br /> ** Identifier assigned for this USSD session by the entity that processed this message.<br /> * error:<br /> ** type: keyword<br /> ** Error returned if the message was not processed.<br /> <br /> Processing of this message will return failure:<br /> * if the message will not be processed<br /> * if the 'id' parameter is missing.<br /> * in case of processing error <br /> * in case of congestion<br /> <br /> ===== ussd.update =====<br /> <br /> <br /> This message is used for transmitting USSD messages during a USSD session. This type of message will be used after the initial stage of creating the session through ''ussd.execute'' has succeeded.<br /> <br /> When receiving this message:<br /> * the ''ussd_map'' module will generate a TCAP CONTINUE message <br /> * the ''ysmpp'' module will generate a SMPP ''deliver_sm'' if it acts as a server (as in the case of the USSD GW) or ''submit_sm'' if it acts as a SMPP client.<br /> <br /> <br /> Parameters:<br /> * id:<br /> ** type: string<br /> ** USSD session identifier of the sending side of the message<br /> * peerid:<br /> ** type: string<br /> ** USSD session identifier for the module that should process this message<br /> * operation_type:<br /> ** type: keyword<br /> ** The type of operation that fired this message. <br /> * text_encoding:<br /> ** type: hexified string<br /> ** The MAP USSD data coding scheme<br /> * text_encoded:<br /> ** type: hexified string<br /> ** The encoded USSD string<br /> ** '''NOTE''': If YATE uses in the internal messages the decoded text, this parameter should not be set (it has higher priority in ussd_map).<br /> * text:<br /> ** type: string<br /> ** The decoded USSD string conforming to the USSD data coding scheme.<br /> * text.encoding:<br /> ** type: keyword<br /> ** The USSD data coding scheme.<br /> * text.lang:<br /> ** type: keyword<br /> ** The language of the decoded text as obtained from the data coding scheme on MAP or from language indicator on SMPP.<br /> * text.lang_indication:<br /> ** type: boolean<br /> ** True if the language was decoded from the USSD string and not from the data coding scheme or if should be encoded on MAP in the USSD string payload.<br /> ** Set to false for UCS2 encoding without language indication<br /> * error:<br /> ** type: keyword<br /> ** Error received from one the USSD session endpoints. It might be a MAP error when HLR/gsmSCF/ failed to process a request or SMPP error when the SMPP client failed to process a request.<br /> <br /> Returned parameters:<br /> * error:<br /> ** type: keyword<br /> ** Error code if this message failed to be processed.<br /> <br /> Points of failure:<br /> * The USSD session specified by peerid parameter cannot be found by the processing side.<br /> * Processing of this message will be refused if it is received after a ''ussd.finalize'' message.<br /> * Processing of this message will return an error if there are mandatory parameters missing of if the parameters specify a values not allowed in the context of the USSD session (e.g., sending a ''processUnstructuredSS-Request inside a ''ussd.update'' message)<br /> <br /> ===== ussd.finalize =====<br /> <br /> This message is used to signal the termination of the USSD session. Successful processing of this message means that the USSD session was terminated and is no longer available. <br /> <br /> When receiving this message:<br /> * the ''ussd_map'' module will generate a TCAP END/ABORT message depending upon the parameters received. A message containing an error that does not map to a MAP error will generate a TCAP ABORT.<br /> * the ''ysmpp'' module will generate a SMPP ''deliver_sm'' if it acts as a server (as in the case of the USSD GW) or ''submit_sm'' if it acts as a SMPP client, a message that will usually contain a last message indication.<br /> <br /> Parameters:<br /> * id:<br /> ** type: string<br /> ** USSD session identifier of the sending side of the message<br /> * peerid:<br /> ** type: string<br /> ** USSD session identifier for the module that should process this message<br /> * operation_type:<br /> ** type: keyword<br /> ** The type of operation that fired this message. <br /> * text_encoding:<br /> ** type: hexified string<br /> ** The MAP USSD data coding scheme<br /> * text_encoded:<br /> ** type: hexified string<br /> ** '''NOTE''': If YATE uses in the internal messages the decoded text, this parameter should not be set (it has higher priority in ussd_map).<br /> ** The encoded USSD string<br /> * text:<br /> ** type: string<br /> ** The decoded USSD string conforming to the USSD data coding scheme.<br /> * text.encoding:<br /> ** type: keyword<br /> ** The USSD data coding scheme.<br /> * text.lang:<br /> ** type: keyword<br /> ** The language of the decoded text as obtained from the data coding scheme on MAP or from language indicator on SMPP.<br /> * text.lang_indication:<br /> ** type: boolean<br /> ** True if the language was decoded from the USSD string and not from the data coding scheme or if should be encoded on MAP in the USSD string payload.<br /> ** Set to false for UCS2 encoding without language indication<br /> * error:<br /> ** type: keyword<br /> ** Error received from one the USSD session endpoints. It might be a MAP error when HLR/gsmSCF/ failed to process a request or SMPP error when the SMPP client failed to process a request.<br /> <br /> Returned parameters:<br /> * error:<br /> ** type: keyword<br /> ** Error code if this message failed to be processed.<br /> <br /> Points of failure:<br /> * The USSD session specified by 'peerid parameter cannot be found by the processing side.<br /> * Processing of this message will return an error if there are mandatory parameters missing of if the parameters specify a value not allowed in the context of the USSD session<br /> <br /> ===== Keyword values =====<br /> <br /> This section details acceptable values for parameters listed as having type ''keyword''.<br /> <br /> * '''hlr.nature/vlr.nature/gsmscf.nature/destination_reference.nature'''<br /> ** unknown<br /> ** international<br /> ** national<br /> ** network-specific<br /> ** subscriber<br /> ** abbreviated<br /> <br /> * '''hlr.plan/vlr.plan/gsmscf.plan/destination_reference.plan'''<br /> ** unknown<br /> ** isdn<br /> ** data<br /> ** telex<br /> ** land-mobile<br /> ** national<br /> ** private<br /> <br /> * '''operation_type'''<br /> ** pssd: mapping of MAP v1 USSD operation ''processUnstructuredSS-Data'' and of SMPP operation ''PSSD''. <br /> ** pssr: mapping of MAP v2 USSD operation ''processUnstructuredSS-Request'' and of SMPP operation ''PSSR''.<br /> ** ussr: mapping of MAP v2 USSD operation ''unstructuredSS-Request'' and of SMPP operation ''USSR&quot;.<br /> ** ussn: mapping of MAP v2 USSD operation ''unstructuredSS-Notify'' and of SMPP operation ''USSN''.<br /> <br /> * '''error'''<br /> ** invalid_logic: error reported when required processing does not follow USSD rules (e.g., MT request starting with ''processUnstructuredSS-Requests'')<br /> ** system_failure: error mapping for MAP error ''systemFailure''.<br /> ** data_missing: error mapping for MAP error ''dataMissing''.<br /> ** unexpected_data: error mapping for MAP error ''unexpectedDataValue''.<br /> ** unknown_alphabet: error mapping for MAP error ''unknownAlphabet''.<br /> ** absent_subscriber: error mapping for MAP error ''absentSubscriber''.<br /> ** illegal_subscriber: error mapping for MAP error ''illegalSubscriber''.<br /> ** illegal_equipment: error mapping for MAP error ''illegalEquipment''.<br /> ** ussd_busy: error mapping for MAP error ''ussd-Busy''.<br /> ** call_barred: error mapping for MAP error ''callBarred''.<br /> ** network_failure: error signaling message transmission failure due to connectivity issues either on the SS7 side or SMPP side.<br /> ** timeout_expired: error signaling a request timeout occurrence.<br /> ** ussd_sess_end_abnormally: error signaling USSD session termination due to an unknown cause. Mapping for this error implies a TCAP Abort either being generated of received. <br /> ** unknown_error: error specified when there is no available mapping for an errror from SMPP to MAP or vice versa.<br /> ** throttling_error: error signaling that a message failed to be processed due to processing side being in congestion state.<br /> ** protocol_error: SMPP generic error. This error is put whenever there is a SMPP specific error that cannot be mapped into one of the other errors.<br /> <br /> * '''node'''<br /> ** MAP parameter for when error = system_failure <br /> ** maps to networkResource in the MAP Error.<br /> ** possible values are: plmn, hlr, vlr, pvlr, controllingMSC, vmsc, eir, rss. Defaults to plmn if not given<br /> <br /> * '''cause'''<br /> ** MAP parameter for when error = call_barred<br /> ** maps to callBarringCause in the MAP Error<br /> ** possible values are: barringServiceActive, operatorBarring. Defaults to operatorBarring if not given<br /> <br /> * '''text.encoding'''<br /> ** gsm7bit / GSM7Bit: text was encoded/is to be encoded GSM 7 Bit<br /> ** ucs2 / UCS2: text was encoded/is to be encoded UCS 2<br /> <br /> * '''text.lang'''<br /> ** two character string specifying a language according to ISO 639-1 or integer value if mapping is not provided.<br /> <br /> ==== SMPP custom parameters ====<br /> <br /> * 0x1502 =&gt; IMSI;<br /> * 0x1503 =&gt; VLR Type of Number;<br /> * 0x1504 =&gt; VLR Numbering Plan Indicator;<br /> * 0x1505 =&gt; VLR address;<br /> * 0x1506 =&gt; GSM SCF Type of Number;<br /> * 0x1507 =&gt; GSM SCF Numbering Plan Indicator;<br /> * 0x1508 =&gt; GSM_SCF address;<br /> * 0x1509 =&gt; Destination Reference Type of Number;<br /> * 0x150a =&gt; Destination Reference Numbering Plan Indicator;<br /> * 0x150b =&gt; Destination Reference;<br /> * 0x150c =&gt; MSISDN<br /> * 0x150d =&gt; Alerting Pattern<br /> * 0x1800 =&gt; HLR Type of Number;<br /> * 0x1801 =&gt; HLR Numbering Plan Indicator;<br /> * 0x1802 =&gt; HLR address.<br /> <br /> === Configuration ===<br /> <br /> ==== ysigchan module ====<br /> <br /> In order to have MAP connectivity, TCAP instances must be configured in ''ysigchan.conf'': <br /> <br /> ; Example of a SS7 Transaction Capabilities Application Part<br /> ; This component is created when encountering a section of this kind<br /> ;[ss7tcap]<br /> ; type: keyword: identifies the component as a SS7 Transfer Capabilities Application Part<br /> ; type = ss7-tcap-ansi for ANSI TCAP<br /> ; type = ss7-tcap-itu for ITU TCAP<br /> ;type=<br /> <br /> ; local_SSN: local SubSystem Number. Mandatory<br /> ;local_SSN=<br /> <br /> ; default_remote_SSN: remote SubSystem Number to provide to SCCP if the application does not provide one<br /> ;default_remote_SSN=<br /> <br /> ; default_remote_pointcode: remote Point Code to provide to SCCP if the application does not provide one<br /> ;default_remote_pointcode=<br /> <br /> ; pointcodetype: remote Point Code type. See above documentation for available types<br /> ;pointcodetype=<br /> <br /> ; sccp: Name of the SCCP component to create and be used by this TCAP<br /> ; A section with the name given here must exist in order to configure the SCCP level<br /> ;sccp=<br /> <br /> ; default_hopcounter: HopCounter provided to SCCP if the application does not provide one<br /> ; Values range 1-15, 0 or boolean false disables, boolean true sets to 15<br /> ; A non-zero value will force using XUDT or LUDT instead of UDT messages<br /> ;default_hopcounter=false<br /> <br /> ; transact_timeout: Time in seconds to timeout a TCAP transaction after no more activity was registered on it<br /> ; NOTE: Values below 15 seconds will be ignored and the timer will assume the default value.<br /> ; Defaults to 300 seconds<br /> ;transact_timeout=300<br /> <br /> ; max_timeout_checks: integer: Maximum number of timeout checks done on a transaction without starting the transaction<br /> ; timer before forcefully starting the transaction timer<br /> ; Defaults to 10<br /> ;max_timeout_checks=10 <br /> <br /> ; timeout_check: Time interval in milliseconds to check for timeouts.<br /> ; Default to 100 ms<br /> ;timeout_check=100 <br /> <br /> ; floodevents: int: How many queued incoming TCAP messages trigger a congestion warning and the drop mechanism<br /> ; for Unidirectional/Begin/QueryWithPermission/QueryWithoutPermission messages.<br /> ; Exit from congestion will take place when there are less the floodevents/4 messages in the queue<br /> ; NOTE! Setting this parameter to 0 will disable the congestion warning and protection. Setting it to one will <br /> ; be overriden and floodevents will be set to 2.<br /> ;floodevents=1000<br /> <br /> ;print-messages: Boolean to enable/disable printing of decoding/encoding of TCAP messages<br /> ; This option applies on reload<br /> ;print-messages=false<br /> <br /> ;extended-debug: Boolean to enable/disable printing of the step-by-step decoding/encoding of TCAP messages<br /> ; This option applies on reload. print-messages must be true.<br /> ;extended-debug=false<br /> <br /> ; hash_list_size: integer: Size of HashList used for keeping the list of current transactions<br /> ;hash_list_size=17<br /> <br /> <br /> '''Configuration Example'''<br /> <br /> [tcap-scf] <br /> ;enable=no <br /> type=ss7-tcap-itu <br /> sccp=sccp <br /> local_SSN=147 <br /> pointcodetype=ITU <br /> print-messages=false <br /> extended-debug=false <br /> transact_timeout=600 <br /> floodevents=1000 <br /> <br /> <br /> [tcap-hlr] <br /> ;enable=no <br /> type=ss7-tcap-itu <br /> sccp=sccp <br /> local_SSN=7 <br /> pointcodetype=ITU <br /> print-messages=false <br /> extended-debug=false <br /> transact_timeout=600 <br /> <br /> <br /> Further configuration for SS7 connectivity is required (SCCP, MTP3, etc.).<br /> <br /> ==== camel_map module ====<br /> <br /> '''NOTE''': As of SVN revision 1285, there is a new ''camelmap'' module. For compatibility reasons, the old module, ''camel_map'', was also kept. Both modules read the same configuration file, ''camel_map.conf''. In order to avoid issues, please make sure to only enable one of these modules in the ''[postload]'' section of ''yate.conf''.<br /> <br /> The new module is the one that offers USSD UCS2 encoding without language indication, but beware that TCP functionality has been removed from it. That functionality has been moved to the ''xml_tcp'' module. The module only uses messages to communicate with applications. ''ussd_map'' uses messages, so there should be no need for TCP functionality.<br /> <br /> <br /> Configuring of tracking IDs is done in the ''general'' section:<br /> <br /> [general]<br /> <br /> ;track_id: string: Shared engine variable name used to obtain a unique tracking ID for TCAP transactions<br /> ; If not set, the module will not set a tracking ID for the TCAP transaction<br /> ;track_id=<br /> <br /> ;track_id_base: string: Optional string with which to prefix the tracking ID<br /> ; This setting has no effect if track_id is not set<br /> ;track_id_base=<br /> <br /> In order to allow communication over MAP through SS7, sections configurating application should exist for each role of the ussd_map module (gsmSCF/HLR). A ''camel_map.conf'' section configuring an application looks like this:<br /> <br /> ;[local appName]<br /> ; This section configures a local application which transmits the XML messages as internal Yate messages<br /> <br /> ; translator: string: name of translator to be used by this application.<br /> ; Must be one one the [tcap ...] sections configured in the camel_map.conf file.<br /> ;translator=<br /> <br /> ; capabilities: string: List of capabilities separated by commas which this application supports<br /> ;capabilities=<br /> <br /> ; export_xml_as: string: Specify in which way the XML will be passed along into a Yate message<br /> ; Allowed values are:<br /> ; - string: pass the XML as a string<br /> ; - object: pass the XML as an object<br /> ; - both: pass the XML as a string and object<br /> ;export_xml_as=object<br /> <br /> ; enable: bool: Enable this application<br /> ;enable=yes<br /> <br /> The translator setting refers to a section of the type defined below which configures atachement to a TCAP instance<br /> <br /> ;[tcap map]<br /> ; This section configures a TCAP User MAP/CAMEL protocol translator<br /> <br /> ; enable: bool: Enable this translator<br /> ;enable=yes<br /> <br /> ; type: string: Type of TCAP User <br /> ; Allowed values are MAP or CAMEL<br /> ;type=MAP<br /> <br /> ; host: IP address: Address on which the TCP listener should bind on for XML communication<br /> ;host=127.0.0.1 <br /> <br /> ; port: integer: Port on which the TCP listener should bind on for XML communication<br /> ; Note: setting port to 0 will disable the listener, so it will not accept TCP applications<br /> ;port=5555<br /> <br /> ; tcap: string: Name of TCAP to which this TCAP user should attach itself to for the SS7 communication<br /> ;tcap=<br /> <br /> ; add-encoding: bool: Always add encoding attribute to XML elements for decoded parameters<br /> ;add-encoding=default from [general]<br /> <br /> ; add-timestamp: bool: Add to XML timestamps used for estimating application latency<br /> ;add-timestamp=default from [general] <br /> <br /> ; print-messages: bool: Debug option to print TCAP and XML messages. This option is applicable on reload.<br /> ;print-messages=false<br /> <br /> ; ussd-string: string: Specifies what the ussd-String parameter will contain as data<br /> ; Allowed values are:<br /> ; - octets: ussd-String will contain the octets as they were received<br /> ; - text: ussd-String will contain the GSM7Bit decoded text<br /> ; This can be overriden in application sections<br /> ;ussd-string=text<br /> <br /> ; ussd-decode: string: Specifies what ussd-String parameters should be decoded into text<br /> ; Allowed values are:<br /> ; - none: ussd-String parameters will never be decoded into text<br /> ; - first: ussd-String in a TCAP Begin message will be decoded into text<br /> ; - all: all ussd-String parameters will be decoded into text<br /> ; This can be overriden in application sections<br /> ;ussd-decode=all<br /> <br /> ; hash_list_size: integer: Size of HashList used for mapping of TCAP transactions to applications<br /> ;hash_list_size=17<br /> <br /> <br /> For load sharing (especially in cases of high loads), you can configure multiple applications using the same translator.<br /> <br /> <br /> '''Configuration Example'''<br /> <br /> The example below configures 2 applications acting as a gsmSCF, each one attached to the TCAP instance with gsmSCF SSN, and 2 applications as HLR, each one attached to the TCAP instance with HLR SSN 6:<br /> <br /> [general]<br /> track_id=ussdgw<br /> track_id_base=ussdgw/<br /> <br /> [tcap scf] <br /> ;enable=no <br /> tcap=tcap-scf <br /> host=0.0.0.0 <br /> port=0 <br /> type=MAP <br /> print-messages=false <br /> add-encoding=false <br /> <br /> [tcap hlr] <br /> ;enable=no <br /> tcap=tcap-hlr <br /> host=0.0.0.0 <br /> port=0 <br /> type=MAP <br /> print-messages=false <br /> add-encoding=false <br /> <br /> [local ussdscf1] <br /> translator=scf <br /> capabilities=USSD <br /> export_xml_as=object <br /> ussd-string=octets <br /> ussd-decode=all <br /> <br /> [local ussdscf2] <br /> translator=scf <br /> capabilities=USSD <br /> export_xml_as=object <br /> ussd-string=octets <br /> ussd-decode=all <br /> <br /> [local ussdhlr1]<br /> translator=hlr <br /> capabilities=USSD <br /> export_xml_as=object <br /> ussd-string=octets <br /> ussd-decode=all <br /> <br /> [local ussdhlr2] <br /> translator=hlr <br /> capabilities=USSD <br /> export_xml_as=object <br /> ussd-string=octets <br /> ussd-decode=all<br /> <br /> '''Note''' If SMPP is configured to expect decoded USSD texts (which is the default configuration), the ''ussd-decode'' configuration setting should be set to ''all''.<br /> <br /> ==== ussd_map module ====<br /> <br /> The module is configured through ''ussd_map.conf''. The configuration file sets timeout parameters and processing threads parameters in the ''general'' section:<br /> <br /> [general]<br /> <br /> ; hash_list_size: integer: Size of HashList for keeping dialogs<br /> ;hash_list_size=17<br /> <br /> ; component_ttl: integer: Component time to live in milliseconds<br /> ; Minimum allowed value is 1000<br /> ; Defaults to 600000 (10 minutes)<br /> ;component_ttl=600000<br /> <br /> ; dialog_idle_ttl: integer: Dialog idle (nothing sent/received) time to live in milliseconds<br /> ; Minimum allowed value is 1000<br /> ; It can be set to 0 to keep it alive until the remote party terminates the dialog<br /> ; Defaults to 86400000 (1 day)<br /> ;dialog_idle_ttl=86400000<br /> <br /> ; dialog_ended_ttl: integer: Ended dialog time to live in milliseconds<br /> ; Minimum allowed value is 1000.<br /> ; It can be set to 0 to remove the dialog after termination<br /> ; Defaults to 0<br /> ;dialog_ended_ttl=0<br /> <br /> ; dispatcher_maxthreads: integer: Maximum number of message dispatch threads to use<br /> ; Minimum value is 1 for use of dispatching threads.<br /> ; NOTE: if the value is set to 0, the module will enqueue the messages into YATE's engine.<br /> ;dispatcher_maxthreads=0<br /> <br /> ; dispatcher_minthreads: integer: Minimum number of message dispatch threads to use<br /> ; Minimum value is 1 for use of dispatching threads.<br /> ;dispatcher_minthreads=1<br /> <br /> ;dispatcher_priority: string: Default priority of message dispatch threads<br /> ;dispatcher_priority=normal<br /> <br /> ; floodevents: integer: Threshold for signaling congestion when the number of messages waiting to be dispatched exceeds it.<br /> ; When entering congestion, all new MAP dialogs and USSD sessions will be refused.<br /> ; 0 disables the mechanism<br /> ;floodevents=0<br /> <br /> ; congestion_exit_factor: double: Factor used to calculate the exit congestion threshold<br /> ; NOTE: if the factor results in a exit congestion threshold of 0 or greater than floodevents, <br /> ; the setting will be overriden and the exit congestion threshold will be set to 1.<br /> ;congestion_exit_factor=0.5<br /> <br /> <br /> Timeout settings should be correlated with timeout settings in TCAP and SMPP, each having its own timeout mechanism.<br /> <br /> <br /> Gateway applications which do the MAP &lt;-&gt; USSD translation are configured through section like the one below:<br /> <br /> [appName]<br /> ; section name is the name of the camel_map application, it must correspond to a [local appName] section in camel_map <br /> <br /> ; enable: boolean: Enable this application<br /> ; Defaults to yes<br /> ;enable=yes<br /> <br /> ; type: string: Type of MAP &lt;-&gt; USSD translator: <br /> ; - SCF means that is the part that receives new dialogs from the HLR (user initiated USSD)<br /> ; - HLR is the part that receives new dialogs from gsmSCF (network initiated USSD)<br /> ; This setting cannot be changed on reload.<br /> ;type=<br /> <br /> ; export_xml_as: string: Specify in which way the XML will be passed along into <br /> ;export_xml_as=object<br /> <br /> ; print_msg: boolean: Print sent/received messages to output<br /> ;print_msg=no<br /> <br /> ; print_xml: boolean: Print sent/received XML data to output<br /> ;print_xml=no<br /> <br /> ; local_addr. : prefix: Parameters prefixed with this set the local SCCP address of this application <br /> ; Meaningful values are:<br /> ; local_addr.CallingPartyAddress.route=<br /> ; local_addr.CallingPartyAddress.ssn=<br /> ; local_addr.CallingPartyAddress.pointcode=<br /> ; local_addr.CallingPartyAddress.gt=<br /> ; local_addr.CallingPartyAddress.gt.nature=<br /> ; local_addr.CallingPartyAddress.gt.plan=<br /> ; local_addr.CallingPartyAddress.gt.translation=<br /> ; local_addr.CallingPartyAddress.gt.encoding= <br /> <br /> ; default_routing: bool : Do routing to default address for all messages<br /> ; default_routing=no<br /> <br /> ; default_addr. : prefix: parameters prefixed with this will be used as the default SCCP called address<br /> ; Meaningful values are:<br /> ; default_addr.application=<br /> ; default_addr.CalledPartyAddress.route=<br /> ; default_addr.CalledPartyAddress.ssn=<br /> ; default_addr.CalledPartyAddress.pointcode=<br /> ; default_addr.CalledPartyAddress.gt=<br /> ; default_addr.CalledPartyAddress.gt.nature=<br /> ; default_addr.CalledPartyAddress.gt.translation=<br /> ; default_addr.CalledPartyAddress.gt.encoding=<br /> <br /> ; hlr_ssn: integer: The SSN expected in the calling address from a HLR.<br /> ; This setting has significance only for SCF type applications<br /> ;hlr_ssn=6<br /> <br /> ; vlr_ssn: integer: The SSN expected in the calling address from a VLR.<br /> ; This setting has significance only for SCF type applications<br /> ;vlr_ssn=7<br /> <br /> <br /> <br /> Each section should have its own equivalent in ''camel_map.conf''.<br /> In the USSD GW scenario, at least tho applications are needed, one acting as SCF, one as HLR. For load sharing multiple gsmSCF and HLR applications can be configured (see the configuration example below).<br /> <br /> <br /> <br /> '''Configuration Example'''<br /> <br /> The example below configures 2 gsmSCF applications and 2 HLR applications, each one corresponding with a application section in the ''camel_map.conf'' example:<br /> <br /> [general] <br /> <br /> component_ttl=600000 <br /> dialog_ended_ttl=0 <br /> dispatcher_maxthreads=10 <br /> dispatcher_minthreads=5 <br /> ;dispatcher_priority=normal <br /> floodevents=1000 <br /> <br /> [ussdscf1] <br /> ;enable=no <br /> type=SCF <br /> export_xml_as=object <br /> print_msg=no <br /> print_xml=no <br /> <br /> local_addr.CallingPartyAddress.route=gt <br /> local_addr.CallingPartyAddress.gt=8828723 <br /> local_addr.CallingPartyAddress.gt.nature=international <br /> local_addr.CallingPartyAddress.gt.plan=isdn <br /> local_addr.CallingPartyAddress.gt.translation=0 <br /> local_addr.CallingPartyAddress.gt.encoding=bcd <br /> <br /> default_routing=no <br /> default_addr.application=ussdHLR <br /> default_addr.CalledPartyAddress.route=gt <br /> default_addr.CalledPartyAddress.gt=8820723 <br /> default_addr.CalledPartyAddress.gt.nature=international <br /> default_addr.CalledPartyAddress.gt.plan=isdn <br /> default_addr.CalledPartyAddress.gt.translation=0 <br /> default_addr.CalledPartyAddress.gt.encoding=bcd <br /> <br /> [ussdscf2] <br /> ;enable=no <br /> type=SCF <br /> export_xml_as=object <br /> print_msg=no <br /> print_xml=no <br /> <br /> local_addr.CallingPartyAddress.route=gt <br /> local_addr.CallingPartyAddress.gt=8828723 <br /> local_addr.CallingPartyAddress.gt.nature=international <br /> local_addr.CallingPartyAddress.gt.plan=isdn <br /> local_addr.CallingPartyAddress.gt.translation=0 <br /> local_addr.CallingPartyAddress.gt.encoding=bcd <br /> <br /> default_routing=no <br /> default_addr.application=ussdHLR <br /> default_addr.CalledPartyAddress.route=gt <br /> default_addr.CalledPartyAddress.gt=8820723 <br /> default_addr.CalledPartyAddress.gt.nature=international <br /> default_addr.CalledPartyAddress.gt.plan=isdn <br /> default_addr.CalledPartyAddress.gt.translation=0 <br /> default_addr.CalledPartyAddress.gt.encoding=bcd <br /> <br /> [ussdhlr1] <br /> ;enable=no <br /> type=HLR <br /> print_msg=no <br /> print_xml=no <br /> export_xml_as=object <br /> <br /> local_addr.CallingPartyAddress.route=gt <br /> local_addr.CallingPartyAddress.gt=8828723 <br /> local_addr.CallingPartyAddress.gt.nature=international <br /> local_addr.CallingPartyAddress.gt.plan=isdn <br /> local_addr.CallingPartyAddress.gt.translation=0 <br /> local_addr.CallingPartyAddress.gt.encoding=bcd <br /> <br /> default_routing=no <br /> default_addr.application=ussdSCF <br /> default_addr.CalledPartyAddress.route=gt <br /> default_addr.CalledPartyAddress.gt=8820457 <br /> default_addr.CalledPartyAddress.gt.nature=international <br /> default_addr.CalledPartyAddress.gt.plan=isdn <br /> default_addr.CalledPartyAddress.gt.translation=0 <br /> default_addr.CalledPartyAddress.gt.encoding=bcd <br /> <br /> [ussdhlr2] <br /> ;enable=no <br /> type=HLR <br /> print_msg=no <br /> print_xml=no <br /> export_xml_as=object <br /> <br /> local_addr.CallingPartyAddress.route=gt <br /> local_addr.CallingPartyAddress.gt=8828723 <br /> local_addr.CallingPartyAddress.gt.nature=international <br /> local_addr.CallingPartyAddress.gt.plan=isdn <br /> local_addr.CallingPartyAddress.gt.translation=0 <br /> local_addr.CallingPartyAddress.gt.encoding=bcd <br /> <br /> default_routing=no <br /> default_addr.application=ussdSCF <br /> default_addr.CalledPartyAddress.route=gt <br /> default_addr.CalledPartyAddress.gt=8820457 <br /> default_addr.CalledPartyAddress.gt.nature=international <br /> default_addr.CalledPartyAddress.gt.plan=isdn <br /> default_addr.CalledPartyAddress.gt.translation=0 <br /> default_addr.CalledPartyAddress.gt.encoding=bcd<br /> <br /> ==== ysmpp module ====<br /> <br /> TODO - configuration explanations<br /> <br /> <br /> '''NOTE''' The module encodes text to ASCII for default encoding (configuration parameter ''default_encoding_type''). If you want to send GSM 7 Bit for SMPP default encoding, please see how the setting is set below.<br /> <br /> '''Configuration Example''''<br /> <br /> [general] <br /> server=smpp-server <br /> track_id=ussdgw <br /> track_id_base=ussdgw/ <br /> <br /> [smpp-server] <br /> enable=true <br /> session_responseinterval=600000 <br /> sessionset_process_max=1 <br /> codec_warndefaults=false <br /> print-messages=no <br /> <br /> [listenerserver server] <br /> ;enable=yes <br /> addr=0.0.0.0 <br /> port=12345<br /> ; use GSM 7 Bit for default SMPP encoding<br /> default_encoding_type=gsm7bit<br /> <br /> === Monitoring ===<br /> <br /> This section details comands through which the state of the USSD GW can be monitored.<br /> <br /> ==== ussd_map module ====<br /> <br /> * '''Congestion state monitoring'''<br /> <br /> The ''ussd_map'' module will generate an alarm when entering/exiting a congestion state. If SNMP support is enabled, this will generate a trap on SNMP.<br /> The congestion status is also reported in the ''state'' entry in the result of the module status command.<br /> <br /> * '''Module status'''<br /> <br /> The module reports its status through the following command in the YATE telnet console:<br /> <br /> status ussd_map<br /> <br /> The command will print the following information:<br /> <br /> workers=count_of_dispatching_threads,messages=count_msg,dialogs=count_of_dialogs,state=normal,count=count_of_applications;format=Type | CurrentDlgs| MAPCreated | UssdCreated |DefaultRouted | MAPSent | MapRecv | USSDSent | USSDRecv | MAPAbort | USSDAbort | BuiltAbort | MAPTimeouts | USSDTimeouts<br /> <br /> <br /> <br /> where:<br /> * workers: current number of used dispatching threads from the maximum configured pool (e.g., 3/10 means 3 threads are used of a pool of 10)<br /> * messages: count of messages waiting on the dispatching queue of the engine<br /> * dialogs: total number of USSD sessions currently handled by all applications<br /> * state of the engine: normal/congestion<br /> * count: number of applications acting either as gsmSCF, either as HLR<br /> * format: name of the application for which the following data is reported:<br /> ** Type: role of the application: SCF (communicates with real HLR), HLR (communicates with real gsmSCF)<br /> ** CurrentDlgs: number of current MAP dialogs handled by this application<br /> ** MAPCreated: number of sessions (dialogs) started by the MAP side<br /> ** UssdCreated: number of sessions (dialogs) started by the SMPP side<br /> ** DefaultRouted: number of dialogs for which failover took place<br /> ** MAPSent: number of MAP messages sent to gsmSCF/HLR. It doesn't count the ones sent via failover routing.<br /> ** MAPRecv: number of MAP messages received from gsmSCF/HLR<br /> ** USSDSent: number of sent ussd.execute/ussd.update/ussd.finalize messages towards the SMPP side.<br /> ** USSDRecv: number of received ussd.execute/ussd.update/usdd.notify messages from SMPP side.<br /> ** MAPAbort: number of dialog aborts generated by MAP side<br /> ** USSDAbort: number of dialog aborts generated by USSD side<br /> ** BuiltAbort: number of dialog aborts generated by the ussd_map module (e.g., not having a ussd.update message processed by anyone will cause ussd_map to generate session abort)<br /> ** MAPTimeouts: number of dialog timeouts generated by MAP side<br /> ** USSDTimeouts: number of timeouts reported by USSD side<br /> <br /> <br /> * '''Module control commands'''<br /> <br /> The module offers the following control commands through the telnet console:<br /> * ''control ussd_map appName print-msg [yes|no|verbose]'' : enable printing of received/sent map./ussd./messages.<br /> * ''control ussd_map appName print-xml [yes|no|verbose]'' : enable printing of received/sent XMLs.<br /> * ''control ussd_map appName export-xml-as [string|object|both]'' : change the way XML is set in the internal messages<br /> * ''control ussd_map start_stats'' : begin gathering data for statistics<br /> * ''control ussd_map stop_stats'' : stop gathering data for statistics<br /> * ''control usdd_map stats'' : print statistic data per engine and each application in part. Data contains number of MAP messages handled per second, number of USSD messages handled per second, maximum number of current dialogs, number of timeouts and number of aborts.<br /> <br /> ==== ysmpp module ====<br /> <br /> The ysmpp module provides the following options for status command:<br /> <br /> 'NOTE' the module_name can take the following values: smppserver or smppclient.<br /> <br /> * status module_name listeners<br /> Prints the module listeners status in format: Address|Status|Reason.<br /> <br /> * status module_name sessions<br /> Prints the status of the sessions in format: Id|State|BindMode|SystemId|IpAddress:Port|Congested|Incoming Queue|Outgoing Queue;<br /> <br /> ** Id: The ID of the SMPP session. Can be used for routing.<br /> ** State: The state of the SMPP session.<br /> ** BindMode: The mode in which the session was bound. (Send/Recv/SendRecv)<br /> ** SystemId: The id with which the session has been authenticated. Can be used in routing.<br /> ** IpAddress:Port: The Ip Address and port of the remote end of the session.<br /> ** Congested: True if this session is in congestion state.<br /> ** Incoming Queue: The number of messages not processed in the incoming queue.<br /> ** Outgoing Queue: The number of messages not processed in the outgoing queue.<br /> <br /> *status module_name ussd overview<br /> Prints the stats of the USSD sessions in format: Total|Active|Average Duration|Total Sent|Total Received|AverageTrafficPerSecond|EndedWithErrors|CongestionRefused<br /> <br /> ** Total: the number of USSD sessions created since the starting of the program.<br /> ** Active: the number of USSD sessions currently active.<br /> ** Average Duration: average duration of a ussd session.<br /> ** Total Sent: total number of SMPP messages sent for USSD sessions.<br /> ** Total Received: total number of SMPP messages received for USSD sessions.<br /> ** AverageTrafficPerSecond: average traffic per second for USSD sessions.<br /> ** EndedWithErrors: the number of USSD sessions that ended with error.<br /> ** CongestionRefused: the number of USSD sessions refused because the server was overloaded.<br /> <br /> == References ==<br /> <br /> * Mobile Application Part (MAP) specification: ETSI TE 129 002</div>

Oana https://ss7api.null.ro/index.php/MSC_simulator 2013-10-28T11:53:27Z

<p>Monica: /* call.execute handling */</p> <hr /> <div>This module simulates the call related features of a CAMEL capable MSC.<br /> <br /> In particular the module implements the Basic Call Machine State described by the CAMEL standards.<br /> <br /> The module does not store the CAMEL subscription, instead it expects any subscription information to be provided in the inbound call routing parameters.<br /> <br /> ==BCSM Module Configuration==<br /> The configuration file is '''camel_bcsm.conf'''.<br /> Sections:<br /> ===[general]===<br /> Unless explicitly specified, all parameters in this section are applied on reload for new calls only.&lt;br/&gt;<br /> Parameters:<br /> <br /> * '''application''': string: Application parameter in camel messages sent by the module&lt;br/&gt;<br /> This parameter is required&lt;br/&gt;<br /> This parameter can be overridden from routing for each call&lt;br/&gt;<br /> <br /> * '''camel_phase''': integer: CAMEL phase to use<br /> Allowed values: 1, 2, 3, 4&lt;br/&gt;<br /> Defaults to 4&lt;br/&gt;<br /> This parameter can be overridden from routing for each call&lt;br/&gt;<br /> <br /> * '''servicekey''': integer: CAMEL serviceKey parameter to be set in initialDP messages<br /> Allowed interval: 0..2147483647&lt;br/&gt;<br /> Defaults to 0&lt;br/&gt;<br /> This parameters can be overridden from routing for each statically armed DP (see [[#call.execute handling|call.execute handling]])&lt;br/&gt;<br /> <br /> * '''msc_address''': string: The mscAddress parameter to be set when sending initialDP<br /> * '''msc_address_plan''': string: MSC address numbering plan. Values: unknown, isdn, data, telex, land-mobile, isdn-mobile, national, private, extension-reserved<br /> * '''msc_address_nature''': string: MSC address number nature. Values: unknown, international, national, network-specific, subscriber, reserved, abbreviated, extension-reserved<br /> This parameters can be overridden from routing for each statically armed DP (see [[#call.execute handling|call.execute handlin]])<br /> <br /> * '''default_call_handling_continue''': boolean: Continue operation when an error occurs<br /> Defaults to enable&lt;br/&gt;<br /> This parameters can be overridden from routing for each statically armed DP (see [[#call.execute handling|call.execute handlin]])&lt;br/&gt;<br /> <br /> * '''tssf_timer''': integer: Application timer (milliseconds) for non user interaction&lt;br/&gt;<br /> This interval is used when call processing is suspended and no user interaction is expected, e.g. an event was notified to SCP and we are waiting for instructions&lt;br/&gt;<br /> Interval allowed: 1000..20000 (1..20s)&lt;br/&gt;<br /> Defaults to 3000 (3 seconds)&lt;br/&gt;<br /> <br /> * '''tssf_timer_user''': integer: Application timer (milliseconds) for user interaction&lt;br/&gt;<br /> This interval id used when call processing is suspended and user interaction is expected, e.g. a disconnectForwardConnection (disconnect a temporary leg) was received from SCP&lt;br/&gt;<br /> Interval allowed: 60000..1800000 (1..30min)&lt;br/&gt;<br /> Defaults to 180000 (3 minutes)&lt;br/&gt;<br /> <br /> * '''report_etc_failed_timer''': integer: The interval in milliseconds to report failure for temporary calls started on Establish Temporary Connection requests<br /> Failure will be reported if the SRF terminates the call within this interval&lt;br/&gt;<br /> If no failure is reported the controlling SCF (which has its own timer) will treat the request as succeeded&lt;br/&gt;<br /> This parameter can be overridden from routing&lt;br/&gt;<br /> Minimum allowed value is 1000&lt;br/&gt;<br /> Defaults to 3000.&lt;br/&gt;<br /> <br /> * '''dp_busy_reason''': regexp: Regexp to match termination reason when a called party terminates the call and we have the 'busy' DP armed&lt;br/&gt;<br /> If the reason matches dp_busy_reason the 'busy' DP will be notified to SCP&lt;br/&gt;<br /> Defaults to ^busy$&lt;br/&gt;<br /> <br /> * '''dp_noanswer_reason''': regexp: Regexp to match termination reason when a called party terminates the call and we have the 'no answer' DP armed&lt;br/&gt;<br /> If the reason matches dp_noanswer_reason the 'no answer' DP will be notified to SCP&lt;br/&gt;<br /> Defaults to ^noanswer$&lt;br/&gt;<br /> <br /> * '''export_xml_as''': string: Specify in which way the XML will be passed along into camel messages. Allowed values are:<br /> ** string: pass the XML as a string&lt;br/&gt;<br /> ** object: pass the XML as an object&lt;br/&gt;<br /> ** both: pass the XML as a string and object&lt;br/&gt;<br /> This parameter can be overridden from routing.&lt;br/&gt;<br /> Defaults to object&lt;br/&gt;<br /> <br /> * '''print_xml''': boolean/string: Instruct the module to print sent/received xml components. Allowed values are:<br /> ** boolean true: Print xml on single line<br /> ** boolean false: Don't print xml<br /> ** verbose: Print xml children on separate lines<br /> This parameter can be overridden from routing.&lt;br/&gt;<br /> Defaults to false&lt;br/&gt;<br /> <br /> * '''print_decoded''': boolean: Print decoded xml elements to output if debug is at level 10&lt;br/&gt;<br /> This parameter can be overridden from routing.&lt;br/&gt;<br /> Defaults to no&lt;br/&gt;<br /> <br /> ==BCSM Routing==<br /> <br /> ===call.execute handling===<br /> <br /> An incoming call is routed to this module by adding a '''bcsm/''' prefix to target.&lt;br/&gt;<br /> The prefix may be followed a call target to use when CAMEL SCF request to continue the call at initial DP, CAMEL SCF is not available (network failure) or initialDP fails:<br /> <br /> ^123$=bcsm/sig/123;trunk=trunk1<br /> <br /> The following parameters (See [[#BCSM Configuration|BCSM Configuration]] for details) can be added when routing:<br /> * servicekey<br /> * default_call_handling_continue<br /> <br /> Example:<br /> <br /> ^123$=bcsm/sig/123;trunk=trunk1;servicekey=2;default_call_handling_continue=false<br /> <br /> ===Starting outgoing calls===<br /> <br /> When need to start an outgoing call (received ETC, ICA/CWA, CWA, CONT) the module will send ''call.preroute'', ''call.route'' and ''call.execute'' messages.&lt;br/&gt;<br /> The ''call.preroute'' message is filled with initial ''call.execute'' message parameters and request parameters (the request may override initial parameters).&lt;br/&gt;<br /> &lt;br/&gt;<br /> The following parameters are always replaced in the initial message:<br /> * '''id''': Replaced by BCSM leg id<br /> * '''module''': Replaced by BCSM module name<br /> <br /> When the initial call is continued, e.g. the call must be continued to initial called number, the call is routed if no target was specified in ''call.execute'' message, e.g. the call was initially routed to ''bcsm/''.&lt;br/&gt;<br /> Otherwise, a ''call.execute'' message is sent with initial target in ''callto'' parameter.&lt;br/&gt;<br /> <br /> '''NOTES:'''<br /> * The preroute/route/execute messages are dispatched, e.g. the operation is done synchronously.<br /> * When ICA/CWA is processed, the initial message parameters are replaced from ICA first and then from CWA request.</div>

Monica https://ss7api.null.ro/index.php/CAMEL_proxy 2013-10-28T11:22:13Z

<p>Monica: /* General */</p> <hr /> <div>The ''camel_proxy.php'' module provides functionality that allows that a single gsmSSF CAMEL invocation be proxied to multiple SCFs. The aim of this module is to provide a way of providing multiple CAMEL services on a single CAMEL request.<br /> <br /> The main purpose is to be able to provide CRBT and PPS (PrePaid Service) facilities in parallel.<br /> <br /> The layout for such a scenario will look like this:<br /> <br /> [[File:CamelProxy.png]]<br /> <br /> What it basically does is that for one IDP invocation, the proxy will be able to translate it to multiple IDPs sent to multiple SCPs, either locally (like the CRBT one) or external.<br /> The proxy keeps an evidence of these multiple invocations and aggregates them into a single, valid dialogue with the invoking SSP.<br /> <br /> ==Camel Proxy Module Configuration==<br /> <br /> The configuration file is camel_bcsm_proxy.conf<br /> <br /> ===Module configuration===<br /> <br /> ===='general' section====<br /> <br /> '''application''': Application parameter in camel messages sent/handled for SSF dialogs.&lt;br/&gt;<br /> This parameter is required and is not applied on reload (can't be changed after module starts).&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''gt''': Global Title to be set in the first message sent in the SSF dialog.&lt;br/&gt;<br /> This parameter is applied on reload.&lt;br/&gt;<br /> TCAP address parameters to be set in the first message sent back to SSF can also be set using '''addr.''' prefix.&lt;br/&gt;<br /> E.g. GT can be set as '''addr.CallingPartyAddress.gt''' along with other parameters like number nature '''addr.CallingPartyAddress.nature'''.&lt;br/&gt;<br /> Setting the GT without other parameters is the same as:&lt;br/&gt;<br /> addr.CallingPartyAddress.gt=[GT set]&lt;br/&gt;<br /> addr.CallingPartyAddress.route=gt&lt;br/&gt;<br /> addr.CallingPartyAddress.gt.encoding=bcd&lt;br/&gt;<br /> addr.CallingPartyAddress.gt.translation=0&lt;br/&gt;<br /> addr.CallingPartyAddress.gt.plan=isdn&lt;br/&gt;<br /> addr.CallingPartyAddress.gt.nature=international&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''servicekey''': CAMEL serviceKey to check when in received initialDP and set when forwarding them to SCFs.&lt;br/&gt;<br /> Allowed interval: 0..2147483647.&lt;br/&gt;<br /> Defaults to 0 if missing or invalid.&lt;br/&gt;<br /> This parameter is applied on reload for new dialogs only.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''query_scf''': Boolean value indicating whether to query for proxied SCFs update when processing initialDP.&lt;br/&gt;<br /> Is enabled a 'scf.query' message will be enqueued and the module will wait for a 'scf.response' message to continue IDP processing.&lt;br/&gt;<br /> Defaults to no.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''print_msg''': boolean/string: Print sent/received messages to output if debug level is at least 9.&lt;br/&gt;<br /> Allowed values are boolean values or 'verbose' string.&lt;br/&gt;<br /> If verbose is specified, the message will be dumped on output.&lt;br/&gt;<br /> Defaults to no.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''print_xml''': boolean/string: Print sent/received XML data to output if debug level is at least 9.&lt;br/&gt;<br /> This parameter is ignored if print_msg is disabled.&lt;br/&gt;<br /> Allowed values are boolean values or 'verbose' string.&lt;br/&gt;<br /> If verbose is specified, XML elements' children, attributes or text will be shown on separate lines.&lt;br/&gt;<br /> Defaults to no.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''idp_calling_required''': boolean: Calling party number is required (non empty) in initialDP.&lt;br/&gt;<br /> Default to yes.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''idp_called_required''': boolean: Called party number is required (non empty) in initialDP.&lt;br/&gt;<br /> Default to yes.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''dispatcher_maxthreads''': integer: Maximum number of message dispatch threads to use.&lt;br/&gt;<br /> Set to 0 to enqueue messages using yate engine.&lt;br/&gt;<br /> Defaults to 0.&lt;br/&gt;<br /> When reloaded it can't be set to 0 (e.g. once set to a non 0 value it can be changed to non 0 values only).&lt;br/&gt;<br /> &lt;br/&gt;<br /> ====Proxied SCF section(s)====<br /> <br /> '''enable''': boolean: Enable the SCF.&lt;br/&gt;<br /> Defaults to yes.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''priority''': integer: Priority in handling messages from SSF.&lt;br/&gt;<br /> Defaults to 0.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''servicekey''': integer: Value with which the IDP serviceKey should be rewritten.&lt;br/&gt;<br /> Allowed interval: 0..2147483647.&lt;br/&gt;<br /> Defaults to SSF service key set in 'general' section.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''dp''': string: Comma separated list of detection points that should match the one received in IDP in order to contact this SCF.&lt;br/&gt;<br /> Items may be DP value or name.&lt;br/&gt;<br /> Defaults to termAttemptAuthorized if empty or all DPs are invalid.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''endfatal''': boolean: Indicate whether or not terminate the proxy dialog when this dialog ends.&lt;br/&gt;<br /> Defaults to no.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''errorfatal''': boolean: Indicate whether or not an error or reject component from the SCF should terminate the whole proxy dialog.&lt;br/&gt;<br /> Defaults to no.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''local''': boolean: The SCF is local (a local application) or external (it passes through the SS7 network to reach it).&lt;br/&gt;<br /> Defaults to no (external application).&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''instances''': integer: Number of local application instances.&lt;br/&gt;<br /> This parameter is ignored for non local SCFs.&lt;br/&gt;<br /> If non 0 it must be set to a value greater then 1.&lt;br/&gt;<br /> Defaults to 0.&lt;br/&gt;<br /> If non 0 the module will build the required number of SCFs and will pick them using a round-robin algorithm.&lt;br/&gt;<br /> Each application's name will be built from SCF application name concatenated with instance suffix startting from 1.&lt;br/&gt;<br /> E.g.:<br /> <br /> [proxy SCP]<br /> instances=2<br /> <br /> Will build 2 applications: SCP1 and SCP2.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''handles''': string: Comma separated list of operations received from the SSF accepted by this SCF.&lt;br/&gt;<br /> Except ERB (Event Report BCSM), which is sent to all SCFs that match the reported DP, all operations that are handled by a SCF should be listed, otherwise the proxy will report to the SSF an error.&lt;br/&gt;<br /> &lt;br/&gt;<br /> '''waittime''': integer: Time, in miliseconds, to wait for a result from a SCF while being in Waiting For Instructions state, after which the dialog is aborted.&lt;br/&gt;<br /> Defaults to 3000.&lt;br/&gt;<br /> Minimum allowed value is 1000.&lt;br/&gt;<br /> &lt;br/&gt;<br /> All other parameters starting with 'addr.' prefix will be put in dialog begin message sent for this SCF.&lt;br/&gt;<br /> They should be set for non local SCFs.&lt;br/&gt;<br /> Parameters:<br /> * '''addr.CalledPartyAddress.route''' - string. It can be set to values: gt/ssn. It specifies how the SCCP address should be routed.<br /> * '''addr.CalledPartyAddress.ssn''' - integer. It's the SSN number in case of SSN routing.<br /> * '''addr.CalledPartyAddress.gt''' - string. GTT number digits for the SCF.<br /> * '''addr.CalledPartyAddress.gt.encoding''' - string. It specifies the encoding for the GT digits. It is usually set to bcd.<br /> * '''addr.CalledPartyAddress.gt.tt''' - integer. It specifies the GT translation type. It is usually set to 0.<br /> * '''addr.CalledPartyAddress.gt.np''' - string. The GT numbering plan. It is usually set to isdn. It can be one of the following values: unknown, isdn, e164, generic, data, x121, telex, maritime-mobile, e210, e211, land-mobile, e212, isdn-mobile, e214, network-specific.<br /> * '''addr.CalledPartyAddress.gt.nature''' - string. It specifies the nature of the GT number. It is usually set to international.It can have one the following values: unknown, subscriber, national-reserved, national-significant, international.<br /> * '''addr.CallingPartyAddress.route'''<br /> * '''addr.CalledPartyAddress.ssn'''<br /> * '''addr.CallingPartyAddress.gt'''<br /> * '''addr.CallingPartyAddress.gt.encoding'''<br /> * '''addr.CallingPartyAddress.gt.tt'''<br /> * '''addr.CallingPartyAddress.gt.np'''<br /> * '''addr.CallingPartyAddress.gt.nature''' <br /> <br /> ====Example====<br /> <br /> [general]<br /> application=camelProxy<br /> servicekey=1<br /> gt=8820003<br /> <br /> [proxy crbt-scp]<br /> servicekey=2<br /> local=true<br /> <br /> [proxy pps-scp]<br /> servicekey=99<br /> priority=2<br /> errorfatal=true<br /> handles=applyChargingReport<br /> addr.CalledPartyAddress.gt=8820007<br /> addr.CalledPartyAddress.route=gt<br /> addr.CalledPartyAddress.gt.encoding=bcd<br /> addr.CalledPartyAddress.gt.tt=0<br /> addr.CalledPartyAddress.gt.np=isdn<br /> addr.CalledPartyAddress.gt.nature=international<br /> addr.CallingPartyAddress.gt=8820003<br /> addr.CallingPartyAddress.route=gt<br /> addr.CallingPartyAddress.gt.encoding=bcd<br /> addr.CallingPartyAddress.gt.tt=0<br /> addr.CallingPartyAddress.gt.np=isdn<br /> addr.CallingPartyAddress.gt.nature=international<br /> <br /> <br /> === camel_map configuration ===<br /> <br /> [local camelProxy]<br /> translator=scp_proxy<br /> capabilities=Camel<br /> <br /> [tcap scp_proxy]<br /> type=CAMEL<br /> tcap=tcap_msc<br /> port=0<br /> <br /> [local pps-scp]<br /> translator=scp_pps<br /> capabilities=Camel<br /> <br /> [tcap scp_pps]<br /> type=CAMEL<br /> tcap=tcap_pps<br /> port=0<br /> <br /> ===camel_bcsm_proxy.conf.sample===<br /> <br /> ; NOTE: This module is not loaded automatically, it needs a line in yate.conf:<br /> ; [postload]<br /> ; ${modulepath}/sig/camel_bcsm_proxy${modsuffix}=yes<br /> <br /> [general]<br /> ; Unless explicitly specified, all parameters are applied on reload for new<br /> ; dialogs only<br /> ; All parameters starting with 'addr.' prefix will be put in the first message sent to SSF<br /> <br /> ; application: string: Application parameter in camel messages sent by the module<br /> ; This parameter is required<br /> ; This parameter is not applied on reload<br /> ;application=<br /> <br /> ; gt: string: Global Title to be set in the first message sent in the SSF dialog<br /> ; This parameter is applied on reload for new dialogs only<br /> ; If non empty other calling party address parameters will be set to default values<br /> ; This parameter can be overriden by addr.CallingPartyAddress.gt parameter<br /> ;gt=<br /> <br /> ; servicekey: integer: CAMEL serviceKey to check in received initialDP messages and<br /> ; set when forwarding them to SCFs<br /> ; Allowed interval: 0..2147483647<br /> ; Defaults to 0 if missing or invalid<br /> ; This parameter is applied on reload for new dialogs only<br /> ;servicekey=0<br /> <br /> ; query_scf: boolean: Query for proxied SCFs update when processing initialDP<br /> ; Is enabled a 'scf.query' message will be enqueued and the module will wait<br /> ; for a 'scf.response' message to continue IDP processing<br /> ; The response must return the list of SCFs to proxy<br /> ; The list may be shorter then configured SCFs<br /> ; New SCFs, other then configured ones, will be ignored<br /> ; The following SCF parameters can be overridden: priority, servicekey, errorfatal,<br /> ; handles, waittime and all parameters starting with 'addr.' prefix<br /> ; Defaults to no<br /> ;query_scf=no<br /> <br /> ; component_ttl: integer: Component time to live in milliseconds<br /> ; Minimum allowed value is 1000<br /> ; Defaults to 15000<br /> ;component_ttl=15000<br /> <br /> ; dialog_idle_ttl: integer: Dialog idle (nothing sent/received) time to live in milliseconds<br /> ; Minimum allowed value is 1000<br /> ; It can be set to 0 to keep it alive until the remote party terminates the dialog<br /> ; Defaults to 5000<br /> ;dialog_idle_ttl=5000<br /> <br /> ; dialog_ended_ttl: integer: Ended dialog time to live in milliseconds<br /> ; Minimum allowed value is 1000.<br /> ; It can be set to 0 to remove the dialog after termination<br /> ; Defaults to 0<br /> ;dialog_ended_ttl=0<br /> <br /> ; export_xml_as: string: Specify in which way the XML will be passed along into<br /> ; Yate messages<br /> ; Allowed values are:<br /> ; - string: pass the XML as a string<br /> ; - object: pass the XML as an object<br /> ; - both: pass the XML as a string and object<br /> ; Defaults to object<br /> ;export_xml_as=object<br /> <br /> ; print_msg: boolean/string: Print sent/received messages to output if debug<br /> ; level is at least 9<br /> ; Allowed values are boolean values or 'verbose' string<br /> ; If verbose is specified, the message will be dumped on output<br /> ; Defaults to no<br /> ;print_msg=no<br /> <br /> ; print_xml: boolean/string: Print sent/received XML data to output if debug<br /> ; level is at least 9<br /> ; This parameter is ignored if print_msg is disabled<br /> ; Allowed values are boolean values or 'verbose' string<br /> ; If verbose is specified, XML elements' children, attributes or text will be<br /> ; shown on separate lines<br /> ; Defaults to no<br /> ;print_xml=no<br /> <br /> ; idp_calling_required: boolean: Calling party number is required (non empty) in initialDP<br /> ; Default to yes<br /> ;idp_calling_required=yes<br /> <br /> ; idp_called_required: boolean: Called party number is required (non empty) in initialDP<br /> ; Default to yes<br /> ;idp_called_required=yes<br /> <br /> ; dispatcher_maxthreads: integer: Maximum number of message dispatch threads to use<br /> ; Set to 0 to enqueue messages using yate engine<br /> ; Defaults to 0<br /> ; When reloaded it can't be set to 0 (e.g. once set to a non 0 value it can be changed to<br /> ; non 0 values only)<br /> ;dispatcher_maxthreads=0<br /> <br /> ;dispatcher_priority: string: Default priority of message dispatch threads<br /> ; Can be one of: lowest, low, normal, high, highest<br /> ; High priorities need superuser privileges on POSIX operating systems<br /> ; Low priorities are not recommended except for debugging<br /> ; Defaults to 'normal'<br /> ; This parameter is applied on reload for new threads only<br /> ;dispatcher_priority=normal<br /> <br /> <br /> ;[proxy appname]<br /> ; This section configures a proxied SCF<br /> ; 'appname' is the application name to be used for the SCF<br /> <br /> ; enable: boolean: Enable the SCF<br /> ; Defaults to yes<br /> ;enable=yes<br /> <br /> ; priority: integer: Priority in handling messages from SSF<br /> ; Defaults to 0<br /> ;priority=0<br /> <br /> ; servicekey: integer: Value with which the IDP serviceKey should be rewritten<br /> ; Allowed interval: 0..2147483647<br /> ; Defaults to SSF service key set in 'general' section<br /> ;servicekey=<br /> <br /> ; dp: string: Comma separated list of detection points that should match the one received in IDP<br /> ; in order to contact this SCF<br /> ; Items may be DP value or name<br /> ; Defaults to termAttemptAuthorized if empty or all DPs are invalid<br /> ;dp=termAttemptAuthorized<br /> <br /> ; endfatal: boolean: Indicate whether or not terminate the proxy dialog when this dialog ends<br /> ; Defaults to no<br /> ;endfatal=no<br /> <br /> ; errorfatal: boolean: Indicate whether or not an error or reject component from<br /> ; the SCF should terminate the whole proxy dialog<br /> ; Defaults to no<br /> ;errorfatal=no<br /> <br /> ; local: boolean: The SCF is local (a local application) or external (it passes<br /> ; through the SS7 network to reach it)<br /> ; Defaults to no (external application)<br /> ;local=no<br /> <br /> ; instances: integer: Number of local application instances<br /> ; If non 0 the module will build the required number of SCFs and will pick them using a<br /> ; round-robin algorithm<br /> ; Each application's name will be built from SCF application name concatenated with instance<br /> ; suffix startting from 1<br /> ; E.g.<br /> ; [proxy SCP]<br /> ; instances=2<br /> ; Will build 2 applications: SCP1 and SCP2<br /> ; This parameter is ignored for non local SCFs<br /> ; If non 0 it must be set to a value greater then 1<br /> ; Defaults to 0<br /> ;instance=<br /> <br /> ; handles: string: Comma separated list of operations received from the SSF<br /> ; accepted by this SCF<br /> ; NOTE: Except ERB (Event Report BCSM), which is sent to all SCFs that match the reported DP,<br /> ; all operations that are handled by a SCF should be listed, otherwise the<br /> ; proxy will report to the SSF an error<br /> ;handles=<br /> <br /> ; waittime: integer: Time, in miliseconds, to wait for a result from a SCF<br /> ; while being in Waiting For Instructions state, after which the dialog<br /> ; is aborted<br /> ; Defaults to 3000<br /> ; Minimum allowed value is 1000<br /> ;waittime=3000<br /> <br /> ; All other parameters starting with 'addr.' prefix will be put in dialog begin<br /> ; message sent for this SCF<br /> ; E.g. addr.CalledPartyAddress.route=gt will be put as CalledPartyAddress.route=gt<br /> <br /> ==Proxy Module Test==<br /> This chapter describes how the Camel Proxy module was tested.<br /> <br /> The purpose of the test was to check if the Camel BCSM Proxy module can handle 100CPS.<br /> <br /> The machine used was a Dual Intel Xeon E5620 (Quad Core with HT) = 16CPUs, 32GB RAM with CentOS 6.2<br /> <br /> The setup was:&lt;br/&gt;<br /> Yate1 - Call generator, sending calls to Yate3 using SIP&lt;br/&gt;<br /> Yate2 - Call generator, sending calls to Yate4 using SIP&lt;br/&gt;<br /> Yate3 - Call handling, send initialDP to Yate5 (Proxy)&lt;br/&gt;<br /> Yate4 - Call handling, send initialDP to Yate5 (Proxy)&lt;br/&gt;<br /> Yate5 - Camel BCSM Proxy&lt;br/&gt;<br /> Yate6 - CRBT script&lt;br/&gt;<br /> Yate7 - PPS script&lt;br/&gt;<br /> Yate8 - PPS script<br /> <br /> <br /> SIP M2PA link M2PA links<br /> Yate1 ---------&gt; Yate3 ------------| |-----------&gt; Yate6 (CRBT)<br /> | |<br /> |-&gt; Yate5 |-----------&gt; Yate7 (PPS)<br /> | |<br /> SIP M2PA link | |-----------&gt; Yate8 (PPS)<br /> Yate2 ---------&gt; Yate4 ------------| <br /> <br /> <br /> '''NOTES:'''<br /> * The sum of both call generators was 110CPS.<br /> * During test top reported ~250%CPU for Proxy.<br /> * All yate instances were running on the same machine.<br /> * The reason of using 2 PPS instances was the performance of PPS script: 1 script is not able to respond quick enough. The PPS SCFs were rotated using 'scf.query' message.<br /> <br /> How success was checked:<br /> * On call generators all calls were answered<br /> * On call handling instances (Yate3 and 4) there were no Tssf timeouts (this would indicate a timeout while waiting for instrunctions from SCP - after sending initialDP or eventReportBCSM with type='request')<br /> * On Proxy instance (Yate5) there were no timeouts (this would indicate a SCF is not responding withing default 3 seconds interval)<br /> <br /> ==Configuration==<br /> <br /> ===Script side===<br /> <br /> Configuration of the &quot;camel_proxy.php&quot; script is done through ''config_proxy.php''. This allows setting the following parameters:<br /> <br /> * 1 '''$myServiceKey''' - integer. The ID of the service provided by this gsmSCF application and which should come in IDP in order to accept the request.<br /> <br /> * 2. '''$proxyName''' - string. It represent the value of the ''application'' parameter set in the ''camel.message'' coming from and going to the SSF. This value is used to check that the message is indeed intented for this script.<br /> <br /> * 3. '''$mynum''' - string. GTT number assigned to this SCP. <br /> <br /> * 4. '''$transTimeout''' - integer. It sets the time for which the PHP TCAP library will keep alive a TCAP dialogue after remaining with no active components. A new TCAP message will reset the associated timer. If the timer runs out, the library will generate a TCAP End in order to terminate the dialog. For this application, this timer is set by default to 180 seconds.<br /> <br /> * 5. '''$scfs''' - array. This defines the list of configured proxied SCFs. Each entry in the array defines a SCF with its configuration parameters. The key set for the entry designates the name of the SCF and the value used for the ''aplication'' parameter set in the ''camel.message'' used to communicate between the proxy and the SCF. For each entry, the following parameters must be set:<br /> ** 5.1. '''serviceKey''' - integer. It represents the service key to be used when constructing an IDP for this SCF..<br /> ** 5.2. '''dp''' - string. It represent the detection point at which this SCF should be contacted. In order for the proxy to build an IDP for this SCF, the detection point received in the IDP from the SSF should match the one configured here.<br /> ** 5.3. '''priority''' - integer. It specifies the priority of this SCF when handling messages from SSF. According to priority,messages from the SSF will be passed by the proxy in priority order to the SCFs, first to the highest priority SCF (meaning the one with the lowest set value).<br /> ** 5.4. '''errorFatal''' - boolean. It specifies whether or not an error or reject component from this SCF should terminate the dialogue with the SSF and also with the other SCFs.<br /> ** 5.5. '''addr''' - array. It specifies SS7 network addressing parameters. They only need be set for external SCFs. Parameters are usually set here are:<br /> *** '''CalledPartyAddress.route''' - string. It can be set to values: gt/ssn. It specifies how the SCCP address should be routed.<br /> *** '''CalledPartyAddress.ssn''' - integer. It's the SSN number in case of SSN routing.<br /> *** '''CalledPartyAddress.gt''' - string. GTT number digits for the SCF.<br /> *** '''CalledPartyAddress.gt.encoding''' - string. It specifies the encoding for the GT digits. It is usually set to ''bcd''.<br /> *** '''CalledPartyAddress.gt.translation''' - integer. It specifies the GT translation type. It is usually set to ''0''. <br /> *** '''CalledPartyAddress.gt.plan''' - string. The GT numbering plan. It is usually set to ''isdn''. It can be one of the following values: unknown, isdn, e164, generic, data, x121, telex, maritime-mobile, e210, e211, land-mobile, e212, isdn-mobile, e214, network-specific.<br /> *** '''CalledPartyAddress.gt.nature'''- string. It specifies the nature of the GT number. It is usually set to ''international''.It can have one the following values: unknown, subscriber, national-reserved, national-significant, international.<br /> *** '''CallingPartyAddress.route'''<br /> *** '''CalledPartyAddress.ssn'''<br /> *** '''CallingPartyAddress.gt'''<br /> *** '''CallingPartyAddress.gt.encoding'''<br /> *** '''CallingPartyAddress.gt.translation'''<br /> *** '''CallingPartyAddress.gt.plan'''<br /> *** '''CallingPartyAddress.gt.nature''' <br /> ** 5.6. '''local''' - boolean. It specifies whether the SCF application is found locally, inside the same Yate instance. If not, communication with the SCF means messages on the SS7 network.<br /> ** 5.7. '''handles''' - array. It specifies a list of operations that are handled by this SCF. Besides IDP and ERBE which are sent to all SCFs that match the sending criteria, other operation must be listed here in order for that SCF to receive it.<br /> ** 5.8. '''context''' - integer. The application context to be used in the dialogue with this SCF. If not set, the one received in the IDP from the SSF will be used.<br /> ** 5.9. '''waitTime''' - integer. It set the time, in seconds, for the proxy to wait for a result from this SCF while being in Waiting For Instructions state, after which the dialogue with that SCF is aborted, and proxy continues processing. Setting it to 0 means that the proxy will wait indefinetely.<br /> <br /> A working configuration for ''camel_proxy.php'' looks like this:<br /> <br /> <br /> $myServiceKey = &quot;1&quot;; <br /> <br /> $proxyName = &quot;camelProxy&quot;; <br /> <br /> /** <br /> * GTT number of this SCP <br /> */ <br /> $mynum = &quot;8820003&quot;; <br /> <br /> /** <br /> * Transaction timeout after inactivity <br /> */ <br /> $transTimeout = 180; <br /> <br /> /** <br /> * List of configured proxied SCFs <br /> * The following parameters must be configured, all are mandatory: <br /> * serviceKey - value with which the IDP serviceKey should be rewritten <br /> * dp - detection point that should match the one received in IDP in order to contact this SCF <br /> * priority - priority in handling messages from SSF <br /> * errorFatal - whether or not an error or reject component from the SCF should terminate the whole proxy dialoque <br /> * addr - SS7 network addressing parameters. <br /> * local - whether the SCF is local (a local application) or external (it passes through the SS7 network to reach it) <br /> * handles - lists operation received from the SSF that are accepted by this SCF. <br /> * NOTE: Except ERBE, which is sent to all SCFs that match the reported DP, all operations that are handled by a <br /> * SCF should be listed, otherwise the proxy will report to the SSF an error. <br /> * context - if set, rewrites the application context for the dialog established with the SCF, otherwise leaves it as received <br /> * waitTime - time, in seconds, to wait for a result from a SCF while being in Waiting For Instructions state, after which the dialogue <br /> * is aborted. <br /> */ <br /> $scfs = array( <br /> &quot;crbt-scp&quot; =&gt; array( <br /> &quot;serviceKey&quot; =&gt; 2, <br /> &quot;dp&quot; =&gt; &quot;termAttemptAuthorized&quot;, <br /> &quot;priority&quot; =&gt; 1, <br /> &quot;errorFatal&quot; =&gt; false, <br /> &quot;addr&quot; =&gt; array(), <br /> &quot;local&quot; =&gt; true, <br /> &quot;handles&quot; =&gt; array(), <br /> &quot;context&quot; =&gt; &quot;&quot;, <br /> &quot;waitTime&quot; =&gt; 3, <br /> ),<br /> &quot;pps-scp&quot; =&gt; array( <br /> &quot;serviceKey&quot; =&gt; 99, <br /> &quot;dp&quot; =&gt; &quot;termAttemptAuthorized&quot;, <br /> &quot;priority&quot; =&gt; 2, <br /> &quot;errorFatal&quot; =&gt; true, <br /> &quot;addr&quot; =&gt; array(&quot;CalledPartyAddress.gt&quot; =&gt; &quot;8820007&quot;, <br /> &quot;CalledPartyAddress.route&quot; =&gt; &quot;gt&quot;, <br /> &quot;CalledPartyAddress.gt.encoding&quot; =&gt; &quot;bcd&quot;, <br /> &quot;CalledPartyAddress.gt.tt&quot; =&gt; &quot;0&quot;, <br /> &quot;CalledPartyAddress.gt.np&quot; =&gt; &quot;isdn&quot;, <br /> &quot;CalledPartyAddress.gt.nature&quot; =&gt; &quot;international&quot;, <br /> &quot;CallingPartyAddress.gt&quot; =&gt; &quot;8820003&quot;, <br /> &quot;CallingPartyAddress.route&quot; =&gt; &quot;gt&quot;, <br /> &quot;CallingPartyAddress.gt.encoding&quot; =&gt; &quot;bcd&quot;, <br /> &quot;CallingPartyAddress.gt.tt&quot; =&gt; &quot;0&quot;, <br /> &quot;CallingPartyAddress.gt.np&quot; =&gt; &quot;isdn&quot;, <br /> &quot;CallingPartyAddress.gt.nature&quot; =&gt; &quot;international&quot;, <br /> ), <br /> &quot;local&quot; =&gt; false, <br /> &quot;handles&quot; =&gt; array(&quot;applyChargingReport&quot;), <br /> &quot;context&quot; =&gt; &quot;&quot;, <br /> &quot;waitTime&quot; =&gt; 3, <br /> ), <br /> );<br /> <br /> ===Yate side===<br /> <br /> On the Yate side, the ''camel_map'' module must be configured through ''camel_map.conf''. <br /> <br /> In order for the module to ensure communication with the SSF, a section named &lt;tt&gt;[local name_of_proxy]&lt;/tt&gt; must be configured:<br /> <br /> [local proxyName] - what comes after ''local'' will be the name of the application<br /> ;enable=no -- enable this application<br /> translator=scp - which translator should be used. A section named [tcap translatorValue] should be present in the config file.<br /> capabilities=Camel - capabilities supported by this application. CAMEL translator has only one capability and that is ''Camel''.<br /> export_xml_as=both - how to export the XML part: string, object or both?<br /> <br /> A &lt;tt&gt;[tcap name]&lt;/tt&gt; section must be configured also. A section looks like this:<br /> <br /> [tcap scp] -- what comes after ''tcap'' will be the name of the translator<br /> ;enable=no -- enable this translator<br /> tcap=tcap-scp -- TCAP to be used by the translator for SS7 network communication, a section with that name should be configured in ''ysigchan.conf''<br /> host=0.0.0.0 -- address on which to listen for incoming applications<br /> port=0 -- port on which to listen for incoming applications. 0 means that will not build a listener, as the proxy works on messages.<br /> type=CAMEL -- type of translator (MAP/CAMEL). For the intended case, CAMEL should be set<br /> print-messages=true -- whether or not to print TCAP and XML messages in the logs<br /> add-encoding=false -- whether to add encoding attribute to data translated to XML<br /> <br /> <br /> For an external proxied SCF, additional &lt;tt&gt;[local scfName]&lt;/tt&gt; and &lt;tt&gt;[tcap name]&lt;/tt&gt; sections must be configured:<br /> <br /> [tcap msc]<br /> tcap=tcap-msc<br /> host=0.0.0.0<br /> port=0<br /> type=CAMEL<br /> print-messages=true<br /> add-encoding=false<br /> <br /> [local ext-scp]<br /> ;enable=no<br /> translator=msc<br /> capabilities=Camel<br /> export_xml_as=both<br /> <br /> <br /> '''NOTE!''' In a proxy scenario, please check that you won't have a valid &lt;tt&gt;[local crbt-scp]&lt;/tt&gt; section configured in camel_map.conf. If so, this will allow to the camel_map module to catch messages emitted by the CRBT SCP that should have been catched by the proxy instead.<br /> <br /> ==Proxy Behaviour==<br /> <br /> Bellow, the behaviour of the CAMEL proxy implemented in ''camel_proxy.php'' is described.<br /> <br /> ===General===<br /> <br /> The main purpose of the proxy is to act as a SCF on the SSF side and as a SSF on the proxied SCF side.<br /> <br /> The proxy sits between the SSF and and the SCFs. From the point of view of the SSF, it will act as a SCF, from the point of view of the proxied SCFs, it will act as a SSF.<br /> <br /> The main characteristics of the proxy behaviour are:<br /> <br /> * when receiving Invoke components from the SSF, the proxy will decide to which SCFs they should be passed along. The decision is taken by looking at the configuration of the SCF for what operation it specifically handles. The operation will be passed only to those SCFs that were configured to receive that specific information. If no SCF was configured to accept the incoming Invoke for an operation, the proxy will return an error to the SSF. InitialDP and EventReportBCSM operations are excluded from this kind of handling.<br /> <br /> * if for a Invoke component arrived from the SSF there are multiple SCFs that match it and to which it should be sent, the proxy will send it in order of SCF priority.<br /> <br /> * Invoke components from SCFs will be sent to the SSF and the proxy will keep track to which SCF each component belongs to.<br /> <br /> * Result and ReturnError components from the SSF will be passed by the proxy to the SCF that initially sent it.<br /> <br /> * sending of an Invoke component to multiple SCFs is done in a serialized fashion. It will send the message to the first SCF, then to the second. Depending on the state of the dialog with the SSF and of the state of the dialogs with the SCFs, the proxy first awaits or not a response from the SCF before sending the Invoke to the next SCF. If the received Invoke caused a SCF to change its state to ''WFI (Waiting For Instructions - from SCF)'', the proxy will first await a response containing a Continue or ContinueWithArgument operation (operation that moves the SCF into ''MON - Monitoring'' state) before sending the Invoke to the next SCF. This means that while a dialog with a SCF is in ''WFI'' state, it can exchange multiple messages with the SSF until the SCF goes into ''MON'' state, and just then the original Invoke will be sent to the next SCF. The message flow looks like this:<br /> <br /> SSF Proxy SCF 1 SCF 2<br /> |------- Invoke 1 -----------&gt;|WFI | | <br /> | |----- Invoke 1a ------&gt;|WFI | <br /> | |&lt;---- Invoke 2a -------|WFI |<br /> |&lt;------ Invoke 2a -----------|WFI | |<br /> |------- Result 2a ----------&gt;|WFI | |<br /> | |----- Result 2a ------&gt;|WFI |<br /> | |&lt;---- Invoke 3a CWA ---|MON |<br /> | |------------------------------ Invoke 1b ---------&gt;|WFI<br /> | |&lt;----------------------------- Invoke 2b ----------|WFI<br /> | |&lt;----------------------------- Invoke CONT 3b CONT-|MON<br /> |&lt;------ Invoke 2b -----------| | |<br /> |&lt;------ Invoke 3a CWA -------|MON | |<br /> | | | |<br /> | | | |<br /> |------- Invoke 4 -----------&gt;|MON | |<br /> | |------ Invoke 4a -----&gt;|MON |<br /> | |------------------------------ Invoke 4b ---------&gt;|MON<br /> <br /> * if the proxy received a error or reject component from a SCF, it will check whether an error on that dialog is fatal (this is part of the SCF configuration), and if so, the proxy will abort the dialog with the SSF and with all SCFs.<br /> * when sending a operation in a WFI state, the proxy will start a timer for how long it will wait a response from the SCF to which it had just sent the operation. If the timer expires, it will send an abort on the dialogue with that SCF. If an error is fatal on this dialog, the dialogs with the SSF and other SCFs are also aborted. If not, the proxy will try to pass the operation to the next SCF that should receive it.<br /> * if an TCAP End message is received from a SCF and there other SCFs that have active dialogues with the SSF, the proxy will terminate the dialogue with just that SCFs. If the TCAP End message contained components, the proxy will rewrite the TCAP END to TCAP CONTINUE and send it to the SSF.<br /> * the proxy will set the required SS7 addressing information if so configured for a SCF. '''NOTE!''' For external SCFs, the configuration parameter for addressing must not be empty. Refer to the the [[http://crbt-doc.lan/index.php?n=CRBT.ProxyConfiguration|configuration page]] for how to do this.<br /> <br /> ===InitialDP handling===<br /> <br /> The initialDP operation has special handling. Upon receiving this operation from the SSF, the proxy will take the following steps:<br /> * it will check for presence of the ''serviceKey'' parameter. If missing, it will reject the operation and end the dialogue with the SSF.<br /> * then it will compare the received serviceKey value with the one configured for the proxy. If they do not match, the proxy will return an error for the operation and end the dialogue with the SSF.<br /> * it will check for the presence of the ''eventTypeBCSM'' parameter. If missing, the proxy will return an error for the operation and end the dialogue with the SSF.<br /> * after passing these checks, the proxy will look for SCFs that match the BCSM event that triggered the IDP. If no SCFs match the detection point, the proxy will return an error for the operation and end the dialogue with the SSF. Otherwise, it will build dialogues towards every matched SCF and, build IDP operation for them and start processing.<br /> * if a matched SCF requires another service key value or another application context, the proxy will replace these values with the ones configured for the SCF. <br /> <br /> ===RequestReportBCSM and EventReportBCSM handling===<br /> <br /> <br /> The RequestReportBCSM and EventReportBCSM operation are specially handled as seeing that multiple SCFs can arm the same DP (detection point) with different event modes: ''interrupted, notify, transparent''. A subsequent arming request for a DP will override the previous arming mode and this can be a problem if one SCF first armed a DP in interrupted mode and another one puts it afterwards in notify or transparent mode. <br /> If a DP was rearmed to ''notify'' from ''interrupted'', this will mess up the handling for the first SCF as it probably armed it as ''interrupted'' as to not continue with call handling until it decided upon something. A ''notify'' means that the SSF continued with call handling without waiting anything from the SCF. ''transparent'' means that the SCF will not be notified about the event, which again messes up the handling of the first SCF.<br /> <br /> In order to prevent that, proxy does the following:<br /> * the proxy keeps track about how DPs were armed for the dialogue with the SSF, and also for the dialogues with the SCFs.<br /> * upon a RequestReportBCSM invocation from a SCF, it will check for all requested DPs if the DP wasn't already armed previously. If it wasn't already armed, the proxy will leave it as is. If it was already armed, it will check how was it armed and depending on the situation, will leave it as is or rewrite it. For example:<br /> ** if the DP was previously armed as ''transparent'' and now it is requested as ''notify'' or ''interrupted'', the proxy will leave it the invocation as is and update only the information about how was it armed.<br /> ** if the DP was previously armed as ''notify'' and now it is requested as ''interrupted'', , the proxy will leave it the invocation as is and update only the information about how was it armed.<br /> ** if the DP was previously armed as ''interrupted'' and now it is requested as ''notify'' or ''transparent, , the proxy will rewrite the arming mode in the invocation.<br /> ** if the DP was previously armed as ''notify'' and now it is requested as ''transparent, , the proxy will rewrite the arming mode in the invocation.<br /> * when receiving an EventReportBCSM invocation from the SSF, the proxy will send it to all SCFs that had previously armed the reported DP. The proxy will not rewrite the mode how this event is reported as it interferes with situations where the dialogue with the SCF that requested ''interrupted'' might have been terminated due to a exception. Rewriting it to a ''notify'' will not correspond with the SSF BCSM state.<br /> <br /> '''Question:''' It may turn that SCF requested ''notify'', but got ''interrupted'' EventReportBCSM, right? Is it OK? &lt;br/&gt;<br /> '''Answer:''' Yes, that's the behaviour right now, but it can be changed to report notify. This would mean adding a configuration parameter as to what to do when this situation occurs: either pass it to the SCF how it was received (what it does right now) or let the proxy generate a Continue if it could not send it with interrupted to anyone.<br /> <br /> '''Question:''' Does this mean, that every SCF, which received ''interrupted'' EventReportBCSM, is obliged to decide on it and issue CONT in the end, even if it didn't intend to receive such an event in ''interrupted'' mode?&lt;br/&gt;<br /> '''Answer:''' Yes.<br /> <br /> '''Question:''' Are CRBT scripts ready for this scenario?&lt;br/&gt;<br /> '''Answer:''' Yes, the CRBT script when handling DPs is prepared to handle such a situation.<br /> <br /> '''Question:''' It seems better to issue CONT by proxy and change ''interrupted'' to what was originally requested by certain SCF. Not sure.&lt;br/&gt;<br /> '''Answer:''' Yes, the proxy could decide to send a Continue to the SSF if none of the SCFs requested it in &quot;interrupted&quot; mode. If one of the SCFs requested &quot;interrupted&quot;, the proxy will expect the SCF to send the Continue.<br /> <br /> ===Multiple Continue/ContinueWithArgument handling===<br /> <br /> <br /> The proxy deals with the situation in which SCFs that were all in ''WFI'' state send each a Continue (CONT)/ ContinueWithArgument (CWA) invocation to get into ''MON'' state. The proxy gathers all their invocations in a single message to the SSF. Because sending multiple CONT/CWA in a single message to the SSF can alterate the BCSM processing - for example, a CONT will stop processing of subsequent operation invocation until the next interrupt - the proxy ensures that it sends a valid mesage to the SSF in order to process all the operations that were requested by the SCFs.<br /> For that, the proxy will do the following:<br /> * if from the view of the proxy, the dialogue with the SSF should result in a ''WFI'' state in the BCSM, it will remove from the message all CONT/CWAs.<br /> * if in the message there are only CONT invocations, only the last one is left, the other ones are removed before sending.<br /> * in in the message there are onle CWA invocations, they are all kept, but the last CWA is moved to also be the last invocation in the message.<br /> * if there is a mix of CWA and CONT invocations, all CONT invocations will be removed and the last CWA is moved to being the last invocation in the message.<br /> <br /> '''Question:''' how does SSF handle multiple CWA?&lt;br/&gt;<br /> '''Answer:''' A SSF should be able to handle multiple CWAs, as usually multiple CWA are sent with different parameters: one can only modify call parameters, one can specify a continue with changed parameters on a certain leg or segment.<br /> <br /> ===Leg ID and DP rewriting===<br /> <br /> In case of CAMEL phase 4 call party handling (what the CRBT SCF does), the proxy does special handling of leg IDs and DPs in order to deal with the fact that leg 2 is disconnected and leg 3 is created. The PPS SCF has no way to know that leg 2 doesn't exist anymore, so handling for dealing with the fact that from its point of view leg 2 still exists has been implemented:<br /> * for this, the proxy will keep track of what legs exist. When a successful InitiateCallAttempt operation has occurred, the proxy will consider it as a replacement for a previously disconnected leg, if that exists.<br /> * when the proxy receives an operation that request actions on a leg previously disconnected, the proxy will rewrite the leg ID towards the SSF to match with the one, that from it's point of view, replaced it. If an operation arrives from the SSF and must be transmitted to a SCF that doesn't not know that the leg it had requested no longes exists, it will rewrite it to its replacement.<br /> * in case of a RRBE operation, if the leg ID must be rewritten, the armed DPs will also be rewritten to matcht the BCSM state machine for the leg that is the replacement (leg 2 was a T-BSCM so PPS would arm T-BCSM DPs, but replacing the leg with leg 3, which is a result of an ICA, means arming DPs for O-BCSM events)<br /> * when a ERBE operation is received from the SSF, if required, the proxy will rewrite the leg ID and reported DP to the SCF that doesn't know that the leg was disconnected.<br /> * leg rewriting handling also aplies to ApplyCharging and ApplyChargingReport operations.<br /> <br /> In case of a SCF that had armed DPs on a leg that was subsequently disconnected, the proxy, in order to ensure that events will be reported to the SCF even after the leg was disconnected, will send to the SSF a RRBE operation to arm on the replacement leg all DPs that are equivalent with the ones that were armed for the disconnected leg.</div>

Monica https://ss7api.null.ro/index.php/CRBT_logic 2013-10-28T10:26:20Z

<p>Monica: /* Abnormal procedures */</p> <hr /> <div>The crbt_scp.php is an implementation for a CAMEL gsmSCP application which provides a Colourful Ring Back Tone service by interfacing with a CAMEL gsmSSF.<br /> <br /> Upon service invocation, this script implements the required actions in order to instruct the gsmSSF to provide the required ringback tone.<br /> <br /> ==Configuration==<br /> <br /> ===Script side===<br /> <br /> The CRBT script supports two ways of communicating with Yate:<br /> # One based on the XML protocol, communication being realized through a TCP socket.<br /> # The other one based done through Yate messages, using ''extmodule''.<br /> The way which the script will use is chosen according to configuration - in particular, through the ''$ioType'' setting.<br /> <br /> <br /> Configuration of this script is done through ''config.php''. This allows setting the following parameters:<br /> <br /> * 1. '''$appName'''- value of the ''application'' parameters set in the ''camel.message''. This value is used to check that the message is indeed intented for this script.<br /> <br /> * 2. '''$ioType''' - type of I/O to use to communicate with Yate. The script recognizes these two values:<br /> ** ''TCP'' - use the configured TCP socket to communicate with Yate.<br /> ** ''MSG'' - use messages through exmodule protocol for communication.<br /> <br /> * 3. '''$host''','''$port''' - host and port where the application should connect to in order to communicate with Yate if ''$ioType'' is set to ''TCP''.<br /> <br /> * 4. '''$transTimeout''' - integer. It sets the time for which the PHP TCAP library will keep alive a TCAP dialogue after remaining with no active components. A new TCAP message will reset the associated timer. If the timer runs out, the library will generate a TCAP End in order to terminate the dialog. For this application, this timer is set by default to 180 seconds.<br /> <br /> * 5. '''$findMelodyID''' - boolean. It specifies whether the gsmSCF should take the necessary steps in order to find out the required ringtone for the called user. Its default value is false, meaning that the gsmSCF will assume that all requests reaching it are requests for subscribers which have the service activated<br /> <br /> * 6. '''$httpRequest''' - string. It's the HTTP request to be made in order to find out the ringtone associated with the user.<br /> <br /> * 7. '''$myServiceKey''' - integer. The ID of the service provided by this gsmSCF application and which should come in IDP in order to accept the request.<br /> <br /> * 8. '''$myDP''' - string. The DP for which this SCP should be triggered and which should come in IDP in order to accept the request.<br /> <br /> * 9. '''$sendAll''' - bool. If true, it will send all response components batched in a single TCAP message, otherwise it will send them each with its own TCAP message. It is set by default to true.<br /> <br /> * 10. '''$buildSRFNum''' - string. It specifies how the address of the gsmSRF for the EstablishTemporaryConnection operation will be built. It can have of of the following values:<br /> ** ''prefix_called'' - build the gsmSRF address following this rule &lt;tt&gt;$srfNumber.$srfSeparator.$correlationID.$srfSeparator.$sfcID&lt;/tt&gt;.<br /> ** ''fixed_number'' - use ''$srfNumber'' as a fixed address for the gsmSRF address. Setting this means that correlationID and scfID for ETC wil be set separately.<br /> <br /> When instructing the SSF to establish a temporary connection to a SRF through an ETC operation, the SCF must provide addressing information to the SSF in regards to the SRF. This information requires:<br /> * the address of the SRF - a routable number<br /> * a correlation ID - that can mean whatever the operators want, but that, according to specification, can be used by the SRF if/when contacting the SCF in order to associate the SSF -&gt; SCF dialogue with the SRF -&gt;SCF dialogue.<br /> * a scfID - an ID for the contacting SCF. This could be used by the SRF to know where to contact the SCF.<br /> <br /> The script provides this information in an ETC operation in 2 ways:<br /> * providing all the above information in the assistingSSPIPAddress. This is done by concatenating the SRF number, correlation ID and scfID -according to an agreement between the SSF and SCF operators. The script simply concatenates these parameters, putting between them the configured separator.<br /> * providing the information in 3 separated parameters:<br /> ** assistingSSPIPAddress - the SRF Number<br /> ** correlationID - the script will set this parameter to either the melody ID or the called party number, encoded in hexified BCD form.<br /> ** scfID - the script will set this parameter to the hexified BCD form of the SCP's GT number.<br /> <br /> Listed bellow are the parameters that need to be configured for the gsmSRF number:<br /> <br /> * '''$srfNumber''' - string. It specifies a number at which the gsmSRF is found.<br /> <br /> * '''$srfSeparator''' - string. Digit(s) used as separator between SRF number, correlationID and sfcID when the assistingSSPIPAddress contains all of them.<br /> <br /> * '''$srfNumber_qualifier''' - string. It specifies the GenericNumber qualifier. It can be one of the following values:<br /> ** ''dialed-digits''<br /> ** ''called-additional''<br /> ** ''caller-failed''<br /> ** ''caller-not-screened''<br /> ** ''terminating''<br /> ** ''connected-additional''<br /> ** ''caller-additional''<br /> ** ''called-original''<br /> ** ''redirecting''<br /> ** ''redirection''<br /> <br /> * '''$srfNumber_complete''' - boolean. It specifies whether the called number is complete or not. It should be complete.<br /> <br /> * '''$srfNumber_nature''' - string. Nature of number. It can have one of the following values:<br /> ** ''unknown''<br /> ** ''international''<br /> ** ''national''<br /> ** ''network-specific''<br /> ** ''subscriber''<br /> ** ''reserved''<br /> ** ''abbreviated''<br /> ** ''extension-reserved''<br /> <br /> * '''$srfNumber_plan''' - string. It's the used numbering plan. It can have one of the following values:<br /> ** ''unknown''<br /> ** ''isdn''<br /> ** ''data''<br /> ** ''telex''<br /> ** ''land-mobile''<br /> ** ''isdn-mobile''<br /> ** ''national''<br /> ** ''private''<br /> ** ''extension-reserved''<br /> <br /> * '''$srfNumber_restrict''' - string. It specifies the presentation of the number. Possible values are:<br /> ** ''allowed''<br /> ** ''restricted''<br /> ** ''unavailable''<br /> ** ''no''<br /> ** ''false''<br /> ** ''yes''<br /> ** ''true''<br /> <br /> * '''$srfNumber_screened''' - string. It specifies the screening indicator for the number. Possible values are:<br /> ** ''user-provided''<br /> ** ''user-provided-passed''<br /> ** ''user-provided-failed''<br /> ** ''network-provided''<br /> ** ''no''<br /> ** ''false''<br /> ** ''yes''<br /> ** ''true''<br /> <br /> * 11. '''$shortTimer''', '''$mediumTimer''', '''$longTimer''' - integer. Timeout values for operations. Some operation have short timeouts, other medium or long times. These parameters configure their values. These default to 3,6 and 9 seconds respectively. In case of larger delays on the network, they should be increased.<br /> <br /> * 12. '''$maxPhase''' - integer.Represents the maximum CAMEL phase allowed for CAMEL interaction. If not set, it will default to 4, meaning that all supported CAMEL phases are allowed.<br /> <br /> * 13. '''$msStateNotAllowed''' - array. List of states received for the subscriber in IDP for which the SCP will abandon CRBT handling and will continue with the call. Recognized values are:<br /> ** ''assumedIdle''<br /> ** ''camelBusy''<br /> ** ''netDetNotReachable''<br /> ** ''notProvidedFromVLR''<br /> It has no default, meaning that it will do CRBT handling ignoring the subscriber state.<br /> <br /> * 14. '''$noAnswerTimer''' - integer. Timer value to be set when arming o/tNoAnswer. If not configured, this value will not be provided by RRBE. If set, the SSF should report a noAnswer DP after the timer value has expired and no other event was armed.<br /> <br /> * 15. '''$prearrangedEndOn''' - array. List of DP events reported as notifications that should determine a prearranged end situation. The listed events should match events listed for BCSMs in camel_map module (see s_eventTypeBCSM[] in camel_map.cpp). In no events are listed, basic termination will be assumed for all DPs that represent an end to the TCAP dialogue.<br /> <br /> '''Note''' - The following parameters need not be set usually:<br /> * ''$host'', ''$port'' - set only if you intend to use TCP communication.<br /> * ''$transTimeout''<br /> * ''$sendAll''<br /> * ''$shortTimer'', ''$mediumTimer'', ''$longTimer''<br /> * ''$maxPhase''<br /> * ''$msStateNotAllowed''<br /> * ''$prearrangedEndOn'' - if there is no prearranged end agreement between operator, this doesn't need to be configured.<br /> <br /> * 16. '''$mynum''' - string. GTT number assigned to this SCP.<br /> <br /> ===Yate side===<br /> <br /> On the Yate side, the ''camel_map'' module must be configured through ''camel_map.conf''. <br /> <br /> For functionality provided through a TCP socket, a &lt;tt&gt;[tcap name]&lt;/tt&gt; section should be configured. A section looks like this:<br /> <br /> [tcap camel] -- what comes after ''tcap'' will be the name of the translator<br /> ;enable=no -- enable this translator<br /> tcap=tcap-test-itu -- TCAP to be used by the translator for SS7 network communication, a section with that name should be configured in ''ysigchan.conf''<br /> host=0.0.0.0 -- address on which to listen for incoming applications<br /> port=16101 -- port on which to listen for incoming applications<br /> type=CAMEL -- type of translator (MAP/CAMEL). For the intended case, CAMEL should be set<br /> print-messages=true -- whether or not to print TCAP and XML messages in the logs<br /> add-encoding=false -- whether to add encoding attribute to data translated to XML<br /> <br /> <br /> For functionality through Yate messages, an additional section, named &lt;tt&gt;[local appName]&lt;/tt&gt; should be configured:<br /> <br /> [local camelLocal] - what comes after ''local'' will be the name of the application<br /> ;enable=no -- enable this application<br /> translator=camel - which translator should be used. A section named [tcap translatorValue] should be present in the config file.<br /> capabilities=Camel - capabilities supported by this application. CAMEL translator have only one capability and that is ''Camel''.<br /> export_xml_as=both - how to export the XML part: string, object or both?<br /> <br /> '''Note:'''<br /> * setting port to 0 will disable the support for TCP applications<br /> * the name of the local application should match the name set in ''$appName'' for the script<br /> <br /> <br /> ==Script behaviour==<br /> <br /> This is a global script that awaits dialog beginnings from SSFs and it is able to handle CAMEL phases 2, 3 and 4.<br /> The phase used for handling the call will be determined using the information provided in the InitialDP operation using the following rules:<br /> * first, an application context check will be done. As seeing that every phase has a different context assigned, phase will be first determined at this stage.<br /> * if the application context determined a phase 4 handling, in the handling of the InitialDP operation these additional checks will be made:<br /> ** the value for ''supportedCamelPhases'' will be checked. In this parameter, the MSC advertises the CAMEL phases that it can handle. From that list, the SCP will choose the highest phase advertised.<br /> ** the value for ''offeredCamel4Functionalities'' will be checked. SCP will verify that all the CAMEL 4 functionalities required for doing CRBT handling in phase 4 are supported. If that is not so, the SCP will downgrade the phase to phase 2 as seeing that the presence of this parameter implied phase 4 functionality and phase 4 functionality implies, by convention, prior phases support also.<br /> <br /> In case of phase 1 detection, the SCP will end the dialogue either with an Abort with application-context-not-supported, either with a Continue operation for CAMEL.<br /> <br /> An configuration parameter was added (''$maxPhase'') - mainly for testing purposes - in order to limit what phase the SCP will accept.<br /> <br /> <br /> Bellow there is detailed description of how the script will act in different scenarios.<br /> <br /> ===Behaviour CAMEL phase 4===<br /> <br /> <br /> ====Normal procedure for dialogue====<br /> <br /> In case of a normal, error free dialogue, things will proceed according to the describing flow below:<br /> <br /> SSF SCP<br /> 1. --------------------- IDP(serviceKey,termAttemptAuth) --------------------------------&gt;<br /> 2. &lt;-------------------- RRBE (tAbandon,leg1) --------------------------------------------<br /> 3. &lt;-------------------- DL (leg2) -------------------------------------------------------<br /> 4. --------------------- DL Result ------------------------------------------------------&gt;<br /> 5. &lt;-------------------- ICA (CS2,leg3) --------------------------------------------------<br /> 6. --------------------- ICA Result -----------------------------------------------------&gt;<br /> 7. &lt;-------------------- RRBE (oTermSeized,oBusy,oAnswer,oNoAnswer,routeFailure,leg3) ----<br /> 8. &lt;-------------------- CWA (leg3)-------------------------------------------------------<br /> 9. --------------------- ERBE (oTermSeized,leg3) ----------------------------------------&gt;<br /> 10. &lt;-------------------- CWA (leg3) ------------------------------------------------------<br /> 11. &lt;-------------------- ETC (CS1) -------------------------------------------------------<br /> 12. --------------------- ERBE (oAnswer,leg3) --------------------------------------------&gt;<br /> 13. &lt;-------------------- DFCWA (CS1) -----------------------------------------------------<br /> 14. &lt;-------------------- ML (leg3) -------------------------------------------------------<br /> 15. --------------------- ML Result ------------------------------------------------------&gt;<br /> 16. &lt;-------------------- CWA (leg3) ------------------------------------------------------<br /> 17. &lt;-------------------- CWA (CS1) -------------------------------------------------------<br /> <br /> In case of busy received from the called party, the call flow is:<br /> <br /> 1. --------------- ERBE (oCalledPartyBusy, leg3, cause) ----------------------&gt;<br /> 2. &lt;-------------- RC (cause received in ERBE/Busy) --------------------------<br /> <br /> ====Abnormal procedures====<br /> <br /> The following schematics will describe the behaviour of the script in certain scenarios. <br /> The numbers assigned above (in the normal dialogue schematic) designate states in the dialogue. These will be used to describe a starting state for when an error is detected.<br /> <br /> =====Initial DP ServiceKey mismatch / DP mismatch=====<br /> <br /> <br /> SSF SCP<br /> --------------------- IDP(serviceKey,oTermAttemptAuth) -------------------------------&gt;<br /> &lt;-------------------- ReturnError(unexpectedDataValue) --------------------------------<br /> <br /> =====Initial DP missing parameters=====<br /> <br /> <br /> SSF SCP<br /> --------------------- IDP(serviceKey,oTermAttemptAuth) -------------------------------&gt;<br /> &lt;-------------------- ReturnError(missingParameter) -----------------------------------<br /> <br /> =====Application context mismatch=====<br /> <br /> <br /> SSF SCP<br /> --------------------- IDP(serviceKey,oTermAttemptAuth) -------------------------------&gt;<br /> &lt;-------------------- U_Abort (user-application-context-name-not-supported) -----------<br /> <br /> =====Receiving an unsupported CAMEL phase=====<br /> <br /> This error can be detected upon receiving an InitialDP operation, or in the ReturnResult for InitiateCallAttempt. Depending upon the state when the error is detected, handling will be done as described below:<br /> <br /> SSF SCP<br /> 1. --------------------- IDP(serviceKey,oTermAttemptAuth) -------------------------------&gt;<br /> &lt;-------------------- Continue --------------------------------------------------------<br /> <br /> SSF SCP<br /> 6. --------------------- ICA Result -----------------------------------------------------&gt;<br /> &lt;-------------------- ReleaseCall -----------------------------------------------------<br /> <br /> <br /> =====Errors received from SSF / Timeout detected for class 1 and 3 operations=====<br /> <br /> The following schematics describe general error procedures when a error is reported by the SSF or when a result for an operation is not received in the specified time allotted for the operation.<br /> <br /> SSF SCP<br /> SCP can be in either of the states : 1 / 2 / 3 <br /> &lt;-------------------- Continue --------------------------------------------------------<br /> <br /> <br /> SSF SCP<br /> SCP can be in either of the states : 4 / 5 / 13/ 14 <br /> &lt;-------------------- ReleaseCall --------------------------------------------------------<br /> <br /> <br /> SSF SCP<br /> SCP can be in either of the states : 6 - 11 <br /> 14. &lt;-------------------- MoveLeg --------------------------------------------------------<br /> <br /> ===Behaviour CAMEL phase 2/3===<br /> <br /> ====Normal procedure for dialogue====<br /> <br /> <br /> The following diagrams will detail the operation of the CRBT script in case of normal, error free phase 2/3 handling.<br /> <br /> <br /> SSF SCP<br /> 1. -------------------------- IDP (serviceKey, termAttemptAuth) ---------------------------&gt;<br /> 2. &lt;------ RRBE (leg1,tAbandon) &amp; (leg2,tBusy,tAnswer,tNoAnswer)----------------------------<br /> 3. &lt;------------------------- ETC ----------------------------------------------------------<br /> 4. &lt;------------------------- CONT ---------------------------------------------------------<br /> 5. -------------------------- ERBE (leg2,tAnswer) ------------------------------------------<br /> 6. &lt;------------------------- DFC ----------------------------------------------------------<br /> 7. &lt;------------------------- CONT ---------------------------------------------------------<br /> <br /> ====Abnormal procedures====<br /> <br /> <br /> Situations described in sections 2.1.2.1 - 2.1.2.4 shall also apply here:<br /> * [[#Initial DP ServiceKey mismatch / DP mismatch|Initial DP ServiceKey mismatch / DP mismatch]]<br /> * [[#Initial DP missing parameters| Initial DP missing parameters]]<br /> * [[#Application context mismatch| Application context mismatch]]<br /> * [[#Receiving an unsupported CAMEL phase| Receiving an unsupported CAMEL phase]]<br /> <br /> ====Errors received from SSF====<br /> <br /> <br /> SSF SCP<br /> SCP can be in either of the states : 2 / 3 <br /> &lt;-------------------- Continue --------------------------------------------------------</div>

Monica https://ss7api.null.ro/index.php/ETSI-TS_100_974 2013-08-26T10:56:20Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:ETSI TS 100 974 V7.15.0 (2004-03) }}<br /> <br /> <br /> '''Technical Specification'''<br /> <br /> 3GPP TS 09.02 version 7.15.0 Release 1998 &lt;br/&gt;<br /> ETSI TS 100 974 V7.15.0 (2004-03) &lt;br/&gt;<br /> <br /> '''Digital cellular telecommunications system (Phase 2+);&lt;br/&gt;Mobile Application Part (MAP) specification&lt;br/&gt;(3GPP TS 09.02 version 7.15.0 Release 1998)'''<br /> <br /> [[File:ETSI_header_logo.gif]]&lt;br/&gt;<br /> [[File:3GPP_TM_RD-8cd3d.jpg]]&lt;br/&gt;<br /> [[File:gsm.jpeg]]<br /> <br /> '''Reference'''<br /> *RTS/TSGN-040902v7f0<br /> <br /> '''Keywords'''<br /> *GSM<br /> <br /> '''ETSI'''<br /> <br /> 650 Route des Lucioles&lt;br/&gt;<br /> F-06921 Sophia Antipolis Cedex - FRANCE&lt;br/&gt;<br /> Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16<br /> &lt;br/&gt; <br /> Siret N° 348 623 562 00017 - NAF 742 C&lt;br/&gt; <br /> Association à but non lucratif enregistrée à la&lt;br/&gt;<br /> Sous-Préfecture de Grasse (06) N° 7803/88&lt;br/&gt;<br /> <br /> <br /> '''Important notice'''<br /> <br /> Individual copies of the present document can be downloaded from: http://www.etsi.org &lt;br/&gt;<br /> <br /> The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat.&lt;br/&gt;<br /> <br /> Users of the present document should be aware that the document may be subject to revision or change of status.&lt;br/&gt;<br /> Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp&lt;br/&gt;<br /> <br /> If you find errors in the present document, send your comment to: editor@etsi.org<br /> <br /> '''Copyright Notification'''<br /> <br /> No part may be reproduced except as authorized by written permission.&lt;br/&gt;<br /> The copyright and the foregoing restriction extend to reproduction in all media.&lt;br/&gt;<br /> <br /> © European Telecommunications Standards Institute 2004.&lt;br/&gt;<br /> All rights reserved.&lt;br/&gt;<br /> <br /> '''DECT'''&lt;sup&gt;TM&lt;/sup&gt; , '''PLUGTESTS'''&lt;sup&gt;TM&lt;/sup&gt; and '''UMTS'''&lt;sup&gt;TM&lt;/sup&gt; are Trade Marks of ETSI registered for the benefit of its Members.&lt;br/&gt;<br /> <br /> '''TIPHON'''&lt;sup&gt;TM&lt;/sup&gt; and the '''TIPHON'''&lt;sup&gt;TM&lt;/sup&gt; logo are Trade Marks currently being registered by ETSI for the benefit of its Members.&lt;br/&gt;<br /> <br /> '''3GPP'''&lt;sup&gt;TM&lt;/sup&gt; is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.&lt;br/&gt;<br /> <br /> '''Intellectual Property Rights'''<br /> <br /> IPRs essential or potentially essential to the present document may have been declared to ETSI. The information<br /> pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found<br /> in ETSI SR 000 314: &quot;Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in<br /> respect of ETSI standards&quot;, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web<br /> server (http://webapp.etsi.org/IPR/home.asp).<br /> Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee<br /> can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web<br /> server) which are, or may be, or may become, essential to the present document.<br /> <br /> '''Foreword'''<br /> <br /> This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).<br /> The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.<br /> The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp . <br /> <br /> '''Foreword'''<br /> <br /> This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). &lt;br/&gt;<br /> <br /> The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. &lt;br/&gt;<br /> <br /> The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under <br /> http://webapp.etsi.org/key/queryform.asp .<br /> <br /> <br /> This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).<br /> &lt;br/&gt;<br /> The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:<br /> <br /> Version x.y.z<br /> <br /> where:<br /> <br /> x the first digit:<br /> 1 presented to TSG for information;<br /> 2 presented to TSG for approval;<br /> 3 or greater indicates TSG approved document under change control.<br /> <br /> y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.<br /> <br /> z the third digit is incremented when editorial only changes have been incorporated in the document.<br /> <br /> ==Scope==<br /> <br /> It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified by CCITT is used to transfer this information.<br /> <br /> This Technical Specification (TS) describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil these signalling needs. <br /> <br /> Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols required by MAP.<br /> <br /> MAP consists of a set of MAP services which are provided to MAP service-users by a MAP service-provider.<br /> <br /> &lt;center&gt;<br /> [[File:Modelling_principles.png]]&lt;br/&gt;<br /> '''Figure 1.1/1: Modelling principles'''<br /> &lt;/center&gt;<br /> <br /> Clauses 7 to 12 of the present document describe the MAP services.<br /> <br /> Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.).<br /> <br /> Clauses 18 to 25 describe the MAP user procedures which make use of MAP services.<br /> <br /> ==References==<br /> <br /> The following documents contain provisions which, through reference in this text, constitute provisions of the present document.<br /> <br /> * References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.<br /> <br /> * For a specific reference, subsequent revisions do not apply.<br /> <br /> * For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document ''in the same Release as the present document.''<br /> <br /> [1]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 01.04: &quot;Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms&quot;.<br /> <br /> [2]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.01: &quot;Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN)&quot;.<br /> <br /> [3]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.02: &quot;Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) Supported by a GSM Public Land Mobile Network (PLMN)&quot;.<br /> <br /> [4]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.03: &quot;Digital cellular telecommunications system (Phase 2+); Teleservices Supported by a GSM Public Land Mobile Network (PLMN)&quot;.<br /> <br /> [5]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.04: &quot;Digital cellular telecommunications system (Phase 2+); General on supplementary<br /> services&quot;.<br /> <br /> [6]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.09: &quot;Digital cellular telecommunications system (Phase 2+); Security aspects&quot;.<br /> <br /> [7]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.16: &quot;Digital cellular telecommunications system (Phase 2+); International Mobile station Equipment Identities (IMEI)&quot;.<br /> <br /> [8]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.41: &quot;Digital cellular telecommunications system (Phase 2+); Operator determined barring&quot;.<br /> <br /> [9]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.81: &quot;Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 1&quot;.<br /> <br /> [10]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.82: &quot;Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1&quot;.<br /> <br /> [11]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.83 : &quot;Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1&quot;.<br /> <br /> [12]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.84: &quot;Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 1&quot;.<br /> <br /> [13]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.85: &quot;Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG)<br /> supplementary services - Stage 1&quot;.<br /> <br /> [14]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.86: &quot;Digital cellular telecommunications system (Phase 2+); Advice of charge (AoC)<br /> supplementary services - Stage 1&quot;.<br /> <br /> [15]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.88: &quot;Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 1&quot;.<br /> <br /> [16]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 02.90: &quot;Digital cellular telecommunication system (Phase 2+); Unstructured supplementary services operation - Stage 1&quot;.<br /> <br /> [17]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.03: &quot;Digital cellular telecommunications system (Phase 2+); Numbering, addressing and identification&quot;.<br /> <br /> [18]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.04: &quot;Digital cellular telecommunications system (Phase 2+); Signalling requirements relating to routeing of calls to mobile subscribers&quot;.<br /> <br /> [19]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.07: &quot;Digital cellular telecommunications system (Phase 2+); Restoration procedures&quot;.<br /> <br /> [20]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.08: &quot;Digital cellular telecommunications system (Phase 2+); Organisation of subscriber data&quot;.<br /> <br /> [21]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.09: &quot;Digital cellular telecommunications system (Phase 2+; Handover procedures&quot;.<br /> <br /> [22]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.11: &quot;Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services&quot;.<br /> <br /> [23]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.12: &quot;Digital cellular telecommunications system (Phase 2+); Location registration procedures&quot;.<br /> <br /> [24]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.20: &quot;Digital cellular telecommunications system (Phase 2+); Security related network functions&quot;.<br /> <br /> [25]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.38: &quot;Digital cellular telecommunications system (Phase 2+); Alphabets and language specific information for GSM&quot;.<br /> <br /> [26]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.40: &quot;Digital cellular telecommunications system (Phase 2+); Technical realization of the Short Message Service (SMS) Point to Point (PP)&quot;.<br /> <br /> [26a]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.71: “Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Functional Description; Stage 2”.<br /> <br /> [27]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.81: &quot;Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 2&quot;.<br /> <br /> [28]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.82: &quot;Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 2&quot;.<br /> <br /> [29]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.83: &quot;Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2&quot;.<br /> <br /> [30]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.84: &quot;Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 2&quot;.<br /> <br /> [31]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.85: &quot;Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 2&quot;.<br /> <br /> [32]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.86: &quot;Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2&quot;.<br /> <br /> [33]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.88: &quot;Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 2&quot;.<br /> <br /> [34]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.90: &quot;Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 2&quot;.<br /> <br /> [35]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.08: &quot;Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification&quot;.<br /> <br /> [36]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.10: &quot;Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification General aspects&quot;.<br /> <br /> [37]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.11: &quot;Digital cellular telecommunications system (Phase 2+); Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface&quot;.<br /> <br /> [37a]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.71: “Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 location services specification.<br /> <br /> [38]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.80: &quot;Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding&quot;.<br /> <br /> [39]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.81: &quot;Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3&quot;.<br /> <br /> [40]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.82: &quot;Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3&quot;.<br /> <br /> [41]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.83: &quot;Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3&quot;.<br /> <br /> [42]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.84: &quot;Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 3&quot;.<br /> <br /> [43]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.85: &quot;Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3&quot;.<br /> <br /> [44]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.86: &quot;Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3&quot;.<br /> <br /> [45]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.88: &quot;Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3&quot;.<br /> <br /> [46]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 04.90: &quot;Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 3&quot;.<br /> <br /> [47]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 08.02: &quot;Digital cellular telecommunications system (Phase 2+); Base Station System - Mobile-services Switching Centre (BSS - MSC) interface Interface principles&quot;.<br /> <br /> [48]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 08.06: &quot;Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface&quot;.<br /> <br /> [49]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 08.08: &quot;Digital cellular telecommunications system (Phase 2+); Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification&quot;.<br /> <br /> [49a]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 08.31: “Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Serving Mobile Location Center (SMLC) – Serving Mobile Location Center (SMLC); SMLC Peer Protocol (SMLCPP).”<br /> <br /> [49b]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 08.71: &quot;Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC - BSS) interface Layer 3<br /> specification&quot;.<br /> <br /> [50]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.01: &quot;Digital cellular telecommunications system (Phase 2+); General network interworking scenarios&quot;.<br /> <br /> [51]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.02: &quot;Digital cellular telecommunications system (Phase 1); Mobile Application Part (MAP) specification&quot;.<br /> <br /> [52]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.03: &quot;Digital cellular telecommunications system (Phase 2+); Signalling requirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)&quot;.<br /> <br /> [53]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.04: &quot;Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)&quot;.<br /> <br /> [54]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.05: &quot;Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly facility (PAD) access&quot;.<br /> <br /> [55]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.06: &quot;Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated<br /> Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services&quot;.<br /> <br /> [56]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.07: &quot;Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services<br /> Digital Network (ISDN) or Public Switched Telephone Network (PSTN)&quot;.<br /> <br /> [57]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.08: &quot;Digital cellular telecommunications system (Phase 2+); Application of the Base Station System Application Part (BSSAP) on the E-interface&quot;.<br /> <br /> [58]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.10: &quot;Digital cellular telecommunications system (Phase 2+); Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)&quot;.<br /> <br /> [59]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.11: &quot;Digital cellular telecommunications system (Phase 2+); Signalling interworking for supplementary services&quot;.<br /> <br /> [59a]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.31: &quot;Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)”.<br /> <br /> [60]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.90: &quot;Digital cellular telecommunications system (Phase 2+); Interworking between Phase 1 infrastructure and Phase 2 Mobile Stations (MS)&quot;.<br /> <br /> [61]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 12.08: &quot;Digital cellular telecommunications system (Phase 2); Subscriber and Equipment Trace&quot;.<br /> <br /> [62]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ETS 300 102-1 (1990): &quot;Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control&quot;.<br /> <br /> [63]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ETS 300 136 (1992): &quot;Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service description&quot;.<br /> <br /> [64]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ETS 300 138 (1992): &quot;Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service Digital Subscriber Signalling System No.one (DSS1) protocol&quot;.<br /> <br /> [65]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ETS 300 287: &quot;Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities (TC) version 2&quot;.<br /> <br /> [66]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ETR 060: &quot;Signalling Protocols and Switching (SPS); Guide-lines for using Abstract Syntax Notation One (ASN.1) in telecommunication application protocols&quot;.<br /> <br /> [67]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation E.164: &quot;Numbering plan for the ISDN era&quot;.<br /> <br /> [68]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation E.212: &quot;Identification plan for land mobile stations&quot;.<br /> <br /> [69]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation E.213: &quot;Telephone and ISDN numbering plan for land mobile stations&quot;.<br /> <br /> [70]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation E.214: &quot;Structuring of the land mobile global title for the signalling connection control part&quot;.<br /> <br /> [71]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.669: &quot;Interworking between the Digital Subscriber Signalling System Layer 3 protocol and the Signalling System No.7 ISDN User part&quot;.<br /> <br /> [72]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.711: &quot;Specifications of Signalling System No.7; Functional description of the signalling connection control part&quot;.<br /> <br /> [73]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.712: &quot;Definition and function of SCCP messages&quot;.<br /> <br /> [74]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.713: &quot;Specifications of Signalling System No.7; SCCP formats and codes&quot;.<br /> <br /> [75]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.714: &quot;Specifications of Signalling System No.7; Signalling connection control part procedures&quot;.<br /> <br /> [76]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.716: &quot;Specifications of Signalling System No.7; Signalling connection control part (SCCP) performances&quot;.<br /> <br /> [77]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.721 (1988): &quot;Specifications of Signalling System No.7; Functional description of the Signalling System No.7 Telephone user part&quot;.<br /> <br /> [78]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.722 (1988): &quot;Specifications of Signalling System No.7; General function of Telephone messages and signals&quot;.<br /> <br /> [79]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.723 (1988): &quot;Specifications of Signalling System No.7; Formats and codes&quot;.<br /> <br /> [80]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.724 (1988): &quot;Specifications of Signalling System No.7; Signalling procedures&quot;.<br /> <br /> [81]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.725 (1988): &quot;Specifications of Signalling System No.7; Signalling performance in the telephone application&quot;.<br /> <br /> [82]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.761 (1988): &quot;Specifications of Signalling System No.7; Functional description of the ISDN user part of Signalling System No.7&quot;.<br /> <br /> [83]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.762 (1988): &quot;Specifications of Signalling System No.7; General function of messages and signals&quot;.<br /> <br /> [84]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.763 (1988): &quot;Specifications of Signalling System No.7; Formats and codes&quot;.<br /> <br /> [85]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.764 (1988): &quot;Specifications of Signalling System No.7; Signalling procedures&quot;.<br /> <br /> [86]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.767: &quot;Specifications of Signalling System No.7; Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections&quot;.<br /> <br /> [87]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.771: &quot;Specifications of Signalling System No.7; Functional description of transaction capabilities&quot;.<br /> <br /> [88]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.772: &quot;Specifications of Signalling System No.7; Transaction capabilities information element definitions&quot;.<br /> <br /> [89]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.773: &quot;Specifications of Signalling System No.7; Transaction capabilities formats and encoding&quot;.<br /> <br /> [90]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.774: &quot;Specifications of Signalling System No.7; Transaction capabilities procedures&quot;.<br /> <br /> [91]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation Q.775: &quot;Specifications of Signalling System No.7; Guide-lines for using transaction capabilities&quot;.<br /> <br /> [92]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation X.200: &quot;Reference Model of Open systems interconnection for CCITT Applications&quot;.<br /> <br /> [93]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation X.208 (1988): &quot;Specification of Abstract Syntax Notation One (ASN.1)&quot;.<br /> <br /> [94]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation X.209 (1988): &quot;Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)&quot;.<br /> <br /> [95]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;CCITT Recommendation X.210: &quot;Open systems interconnection layer service definition conventions&quot;.<br /> <br /> [96]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.02: &quot;Digital cellular telecommunications system (Phase 2); Mobile Application Part (MAP) specification”.<br /> <br /> [97]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.18: &quot;Digital cellular telecommunications system (Phase 2+); Basic Call Handling&quot;.<br /> <br /> [98]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.78: &quot;Digital cellular telecommunications system (Phase 2+); Customised Applications for Mobile network Enhanced Logic (CAMEL) - Stage 2”.<br /> <br /> [99]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.79: &quot;Digital cellular telecommunications system (Phase 2+); Support of Optimal Routeing (SOR) - Stage 2”.<br /> <br /> [100]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.68: &quot;Digital cellular telecommunications system (Phase 2+); - Stage 2&quot;.<br /> <br /> [101]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.69: &quot;Digital cellular telecommunications system (Phase 2+); - Stage 2&quot;.<br /> <br /> [102]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ANSI T1.113: &quot;Signaling System No. 7 (SS7) - ISDN User Part&quot;.<br /> <br /> [103]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.54 &quot;Digital cellular telecommunications system (Phase 2+); Stage 2 Description for the use of a Shared Inter Working Function (SIWF) in a GSM PLMN&quot;.<br /> <br /> [104]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.60: &quot;Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS) Description; Stage 2&quot;.<br /> <br /> [105]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.60: &quot;Digital cellular telecommunications system (Phase 2+), General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface&quot;.<br /> <br /> [106]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 09.18: &quot;Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification&quot;.<br /> <br /> [107]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.93: &quot;Digital cellular telecommunications system (Phase 2+); Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2&quot;.<br /> <br /> [108]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;GSM 03.66: &quot;Digital cellular telecommunications system (Phase 2+); Support of Mobile Number Portability (MNP); Technical Realisation Stage 2&quot;.<br /> <br /> [109]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ANSI T1.112 (1996 ): &quot;Telecommunication – Signaling No. 7 – Signaling Connection Control Part (SCCP)&quot;.<br /> <br /> ==Abreviations ==<br /> <br /> Abbreviations used in the present document are listed in GSM 01.04.<br /> <br /> <br /> ==Configuration of the mobile network==<br /> <br /> ===The entities of the mobile system===<br /> <br /> <br /> To provide the mobile service as it is defined, it is necessary to introduce some specific functions. These functional entities can be implemented in different equipments or integrated. In any case, exchanges of data occur between these entities.<br /> <br /> <br /> ====The Home Location Register (HLR)====<br /> <br /> This functional entity is a data base in charge of the management of mobile subscribers. A PLMN may contain one or several HLRs; it depends on the number of mobile subscribers, on the capacity of the equipment and on the <br /> organization of the network. All subscription data are stored there. The main information stored there concerns the location of each MS in order to be able to route calls to the mobile subscribers managed by each HLR. All management interventions occur on this data base. The HLRs have no direct control of MSCs.&lt;br/&gt;<br /> &lt;br/&gt;<br /> <br /> Two numbers attached to each mobile subscription are stored in the HLR:<br /> <br /> * IMSI;<br /> * MSISDN.<br /> <br /> The data base contains other information such as:<br /> <br /> * location information (VLR number);<br /> * basic telecommunication services subscription information;<br /> * service restrictions (e.g. roaming limitation);<br /> * supplementary services; the tables contain the parameters attached to these services;<br /> * GPRS subscription data and routeing information.<br /> <br /> The organization of the subscriber data is detailed in GSM 03.08.<br /> <br /> <br /> ====The Visitor Location Register (VLR)====<br /> <br /> An MS roaming in an MSC area is controlled by the Visitor Location Register in charge of this area. When an MS appears in a location area it starts a location updating procedure. The MSC in charge of that area notices this registration and transfers to the Visitor Location Register the identity of the location area where the MS is situated. A VLR may be in charge of one or several MSC areas.<br /> <br /> The VLR also contains the information needed to handle the calls set up or received by the MSs registered in its data base (in some cases the VLR may have to obtain additional information from the HLR); the following elements can be found in its tables:<br /> <br /> * the IMSI;<br /> * the MSISDN;<br /> * the TMSI, if applicable;<br /> * the location area where the MS has been registered. This will be used to call the station;<br /> * supplementary service parameters.<br /> <br /> The information is passed between VLR and HLR by the procedures described in GSM 03.12.<br /> <br /> The organization of the subscriber data is detailed in GSM 03.08.<br /> <br /> ====The Mobile-services Switching Centre (MSC)====<br /> <br /> The Mobile-services Switching Centre is an exchange which performs all the switching functions for MSs located in a geographical area designated as the MSC area. The main difference between an MSC and an exchange in a fixed<br /> network is that the MSC has to take into account the impact of the allocation of radio resources and the mobile nature of the subscribers and has to perform, for example, the following procedures:<br /> <br /> * procedures required for the location registration (see GSM 03.12);<br /> * procedures required for hand-over (see GSM 03.09).<br /> <br /> ====The Base Station System (BSS)====<br /> <br /> The BSS is the sub-system of Base Station equipment (transceivers, controllers, etc...) which is viewed <br /> * by the MSC through an interface (A-interface) with the functionality described in GSM 08.02;<br /> * by the SGSN through an interface (Gb-interface) with the functionality described in GSM 03.60.<br /> <br /> <br /> ====The Gateway MSC (GMSC)====<br /> <br /> In the case of incoming calls to the PLMN, if the fixed network is unable to interrogate the HLR, the call is routed to an MSC. This MSC will interrogate the appropriate HLR and then route the call to the MSC where the MS is located. The MSC which then performs the routing function to the actual location of the mobile is called the Gateway MSC.<br /> <br /> The choice of which MSCs can act as Gateway MSCs is a network operator matter (e.g. all MSCs or some designated MSCs).<br /> <br /> If the call is a voice group/broadcast call it is routed directly from the GMSC to the VBS/VGCS Anchor MSC, based on information (VBS/VGCS call reference) contained in the dialled number. See also GTSs 03.68 and 03.69.<br /> <br /> See also GSM 03.04.<br /> <br /> ====The SMS Gateway MSC====<br /> <br /> The SMS GMSC is the interface between the Mobile Network and the network which provides access to the Short Message Service Centre, for short messages to be delivered to MSs.<br /> <br /> The choice of which MSCs can act as SMS Gateway MSCs is a network operator matter (e.g. all MSCs or some designated MSCs).<br /> <br /> ====The SMS Interworking MSC====<br /> <br /> The SMS IWMSC is the interface between the Mobile Network and the network which provides access to the Short Message Service Centre, for short messages submitted by MSs.<br /> <br /> The choice of which MSCs can act as SMS Interworking MSCs is a network operator matter (e.g. all MSCs or some designated MSCs).<br /> <br /> <br /> ====The VBS/VGCS Anchor MSC====<br /> <br /> The voice broadcast/group call anchor MSC obtains from the associated GCR all relevant attributes and controls in turn all cells in its area, VBS/VGCS Relay-MSCs and dispatchers belonging to a given group call.<br /> <br /> <br /> ====The Equipment Identity Register (EIR)====<br /> <br /> This functional unit is a data base in charge of the management of the equipment identities of the MSs; see also GSM 02.16.<br /> <br /> ====The GSM Service Control Function (gsmSCF)====<br /> <br /> This functional entity contains the CAMEL service logic to implement OSS. It interfaces with the gsmSSF and the HLR; see also TS GSM 03.78.<br /> <br /> ====The VBS/VGCS Relay MSC====<br /> <br /> The voice broadcast/group call relay MSC obtains from the associated anchor MSC all relevant attributes and controls in turn all cells in its area belonging to a given group call.<br /> <br /> ====The Group Call Register (GCR)====<br /> <br /> This functional unit is a data base in charge of the management of attributes related to the establishment of Voice Broadcast Calls and Voice Group Calls<br /> <br /> ====The Shared InterWorking Function Server (SIWFS)====<br /> <br /> A Shared Inter Working Function is a network function that may be used by any MSC in the same PLMN to provide interworking for a data/fax call. Whereas an IWF can only be used by its MSC, the SIWF can be used by several other network nodes e.g. any MSC within the same PLMN (the concept is not limited to a certain number of MSCs). SIWF is applied to data services in GSM Phase 2 and GSM Phase 2+ (as defined in GSM 02.02, GSM 02.03 and GSM 02.34).<br /> <br /> The usage of an SIWF requires no additional manipulation at the MS.<br /> <br /> An IWF provides specific functions associated with the visited MSC for the interworking with other networks. It comprises signalling and traffic channel related functions. The traffic channel related functions are provided by an Inter Working Unit (IWU).<br /> <br /> The SIWF concept is that it provides specific functions for the interworking with other networks. It comprises signalling and traffic channel related functions. Whereas the signalling related functions are associated with the visited MSC, the IWU providing the traffic channel related functions has another physical location.<br /> <br /> The entity that contains all additional functions needed in the visited MSC to provide the SIWF is called SIWF Controller (SIWFC). The entity where the IWU is located is called SIWF Server (SIWFS). The Interface between a<br /> visited MSC and a SIWFS is called the K Interface.<br /> <br /> SIWFS can be provided by a MSC (MSC/SIWFS) or by another network entity (stand alone SIWFS).<br /> <br /> ====The Serving GPRS Support Node (SGSN)====<br /> <br /> This functional unit keeps track of the individual MSs' location and performs security functions and access control; see also GSM 03.60.<br /> <br /> ====The Gateway GPRS Support Node (GGSN)====<br /> <br /> This functional unit provides interworking with external packet-switched networks, network screens and routing of the Network Requested PDP-context activation;see also GSM 03.60.4.2 &quot;Configuration of a Public Land Mobile Network (PLMN)&quot;.<br /> <br /> The basic configuration of a Public Land Mobile Network is presented in figure 4.2/1. In this figure the most general solution is described in order to define all the possible interfaces which can be found in any PLMN. The specific implementation in each network may be different: some particular functions may be implemented in the same equipment and then some interfaces may become internal interfaces. In any case the configuration of a PLMN must have no impact on the relationship with the other PLMNs.<br /> <br /> In this configuration, all the functions are considered implemented in different equipments. Therefore, all the interfaces are external and need the support of the Mobile Application Part of the Signalling System No. 7 to exchange the data necessary to support the mobile service. From this configuration, all the possible PLMN organizations can be deduced.<br /> <br /> ====The Number Portability Location Register (NPLR)====<br /> <br /> This functional unit provides routing information necessary in some Mobile Number Portability environments in order to route calls for ported mobile subscribers. For details see also GSM 03.66 [108].<br /> <br /> ====The Serving Mobile Location Center (SMLC)====<br /> <br /> An SMLC is a database and processing entity that manages the procedures for obtaining the geographic location of a target MS in the coverage area served by the SMLC. In managing the location procedures, the SMLC chooses the positioning method and provides data and instructions to the LMUs or target MS that perform the actual location measurements associated with the chosen method. The SMLC also verifies any location estimate computed by the target MS or computes a location itself from measurements provided to it by the target MS or LMUs.<br /> <br /> An SMLC also manages a set of LMUs in its coverage area whose purpose is to provide location measurements and location assistance data to the SMLC to compute, or assist in computing, location estimates for target MSs. Management functions performed by an SMLC on behalf of its LMUs include maintaining the status and current serving MSC of each LMU and supporting O&amp;M procedures, <br /> <br /> The database in an SMLC contains data necessary for choosing an appropriate position method and any parameters associated with this method for a target MS in any serving cell, for computing or verifying location estimates and for managing its LMUs.<br /> <br /> An SMLC may be either NSS based or BSS based. An NSS based SMLC supports positioning and management of its LMUs via interaction with one or more MSCs using the Ls interface. A BSS based SMLC supports positioning and<br /> management of its LMUs via interaction with one or more BSCs using the Lb interface.<br /> <br /> ====The Gateway Mobile Location Center (GMLC)====<br /> <br /> The GMLC provides access to location services (LCS) for LCS clients external to a PLMN. A GMLC may also support access to location services from LCS clients internal to its own PLMN. The GMLC allows an LCS client to issue location requests for certain target MSs; it then conveys these requests to the VMSC currently serving each target MS and passes back the location results to the LCSclient. Any target MS whose location is requested may belong to either the GMLC’s own PLMN or another PLMN and may currently be served by either the GMLC’s own PLMN or another PLMN.<br /> <br /> ====The Location Measurement Unit (LMU)====<br /> <br /> The LMU is the logical network entity that performs location measurements in the VPLMN in order to either position a target MS or provide assistance data to be used in conjunction with other location measurements. An LMU is controlled by an SMLC in the VPLMN from which location commands can be received and to which any location measurements are returned.<br /> <br /> &lt;center&gt;<br /> [[File:PLMN_config.png]]&lt;br/&gt;<br /> '''Figure 4.2/1: Configuration of a PLMN'''<br /> &lt;/center&gt;<br /> <br /> ===Void===<br /> <br /> ===Interconnection between PLMNs===<br /> <br /> Since the configuration of a PLMN does not have any impact on other PLMNs, the signalling interfaces specified can<br /> be implemented both between the entities within a PLMN and between different PLMNs.<br /> <br /> <br /> ===The interfaces within the mobile service===<br /> <br /> ====Interface between the HLR and the VLR (D-interface)====<br /> <br /> This interface is used to exchange the data related to the location of the MS and to the management of the subscriber. The main service provided to the mobile subscriber is the capability to set up or to receive calls within the whole service area. To support that purpose the location registers have to exchange data. The VLR informs the HLR on the<br /> registration of a MS managed by the latter and provides it with the relevant location information. The HLR sends to the VLR all the data needed to support the service to the MS. The HLR then calls the previous VLR to inform it that it can cancel the location registration of this station because of the roaming of the mobile.<br /> <br /> Exchanges of data may also occur when the mobile subscriber requires a particular service, when he wants to change some data attached to his subscription or when some parameters of the subscription are modified by administrative means.<br /> <br /> <br /> ====Interface between the HLR and the gsmSCF (J-interface)====<br /> <br /> This interface is used by the gsmSCF to request information from the HLR (via the Any-time Interrogation function) or to allow call independent related network- or user-initiated interaction between an MS and the gsmSCF (via the USSD function). Support of the gsmSCF-HLR interface is a network operator option. As a network operator option, the HLR may refuse to provide the information requested by the gsmSCF.<br /> <br /> ====Interface between the VLR and its associated MSC(s) (B-interface)====<br /> <br /> The VLR is the location and management data base for the MSs roaming in the area controlled by the associated MSC(s). Whenever the MSC needs data related to a given MS currently located in its area, it interrogates the VLR. When a MS initiates a location updating procedure with an MSC, the MSC informs its VLR which stores the relevant information in its tables. This procedure occurs whenever a mobile roams to another location area. Also, for instance when a subscriber activates a specific supplementary service or modifies some data attached to a service, the MSC transfers (via the VLR) the request to the HLR, which stores these modifications and updates the VLR if required.<br /> <br /> However, this interface is not fully operational specified. It is strongly recommended not to implement the B-interface<br /> as an external interface.<br /> <br /> ====Interface between VLRs (G-interface)====<br /> <br /> When an MS initiates a location updating using TMSI, the VLR can fetch the IMSI and authentication set from the previous VLR.<br /> <br /> ====Interface between the HLR and the MSC (C-interface)====<br /> <br /> When the fixed network is not able to perform the interrogation procedure needed to set up a call to a mobile subscriber, the Gateway MSC has to interrogate the HLR of the called subscriber to obtain the roaming number of the called MS (see GSM 03.04).<br /> <br /> To forward a short message to a mobile subscriber, the SMS Gateway MSC has to interrogate the HLR to obtain the MSC number where the MS is located.<br /> <br /> ====Interface between the MSC and the gsmSCF (L-interface)====<br /> <br /> When one of the following Supplementary Services, CD, ECT or MPTY, is invoked in the MSC a notification shall be sent towards the gsmSCF.<br /> <br /> ====Interface between MSCs (E-interface)====<br /> <br /> When a MS moves from one MSC area to another during a call, a handover procedure has to be performed in order to continue the communication. For that purpose the MSCs involved have to exchange data to initiate and then to realize the operation.<br /> <br /> This interface is also used to forward short messages, to perform location for a target MS for which handover has occurred on an established call and to transfer LCS messages to and from an LMU for which handover of a signalling channel has occurred.<br /> <br /> This interface is also used to transfer information for inter-MSC VBS/VGCS calls .<br /> <br /> ====Interface between the MSC and Base Station Systems (A-interface)====<br /> <br /> The description of this interface is contained in the GSM 08-series of MSs.<br /> <br /> The BSS-MSC interface carries information concerning:<br /> <br /> * BSS management;<br /> * call handling;<br /> * location management.<br /> <br /> ====Interface between MSC and EIR (F-interface)====<br /> <br /> This interface is used when an MSC wants to check an IMEI.<br /> <br /> ====Interface between VBS/VGCS Anchor MSC and GCR (I-interface)====<br /> <br /> This is an internal interface.<br /> <br /> ====Interface between the MSC and the SIWF server (K-interface)====<br /> <br /> When a MSC detects that it can not provide the requested IW function, resources from an SIWF server can be used. This interface is used to allocate resources in that SIWF server and establish required physical connections to that server.<br /> <br /> ====Interface between SGSN and HLR (Gr-interface)====<br /> <br /> The description of this interface is contained in the GSM 03.60.<br /> <br /> ====Interface between SGSN and SMS-GMSC or SMS-IWMSC (Gd-interface)====<br /> <br /> The description of this interface is contained in the GSM 03.60.<br /> <br /> ====Interface between GGSN and HLR (Gc-interface)====<br /> <br /> The description of this interface is contained in the GSM 03.60.<br /> <br /> ====Interface between SGSN and EIR (Gf-interface)====<br /> <br /> The description of this interface is contained in the GSM 03.60.<br /> <br /> ====Interface between SGSN and BSC (Gb-interface)====<br /> <br /> The description of this interface is contained in the GSM 03.60.<br /> <br /> ====Interface between SGSN and MSC/VLR (Gs-interface)====<br /> <br /> The description of this interface is contained in the GSM 09.18.<br /> <br /> ====Interface between SMLC and BSC (Lb interface)====<br /> <br /> This interface is used by a BSC when an SMLC is BSS based to request either the initiation of location procedures or the retrieval of location assistance data for a particular target MS in the coverage area served by the SMLC. The interface is also used to transfer LCS measurement and O&amp;M information between an SMLC and LMU via the BSC. A description of this interface is contained in GSM 03.71 and GSM 09.31.<br /> <br /> ====Interface between SMLC and MSC (Ls interface)====<br /> <br /> This interface is used by the MSC when an SMLC is NSS based to request either the initiation of location procedures or the retrieval of location assistance data for a particular target MS in the coverage area served by the SMLC. The interface is also used to transfer LCS measurement and O&amp;M information between an SMLC and LMU or BSC via the MSC. A description of this interface is contained in GSM 03.71 and GSM 09.31.<br /> <br /> ====Interface between SMLC and SMLC (Lp interface)====<br /> <br /> This interface is used by an SMLC to obtain LCS measurement information from an LMU controlled by another SMLC. A description of this interface is contained in GSM 03.71 and GSM 08.31. <br /> <br /> ====Void====<br /> <br /> ====Interface between GMLC and HLR (Lh interface)====<br /> <br /> This interface is used by the GMLC to request the address of the visited MSC for a particular target MS whose location has been requested.<br /> <br /> ====Interface between GMLC and MSC (Lg interface)====<br /> <br /> This interface is used by the GMLC to convey a location request to the MSC currently serving a particular target MS whose location was requested. The interface is used by the MSC to return location results to the GMLC.<br /> <br /> ====Interface between LCS Client and GMLC (Le interface)====<br /> <br /> This interface is used by a client of the Location Services (LCS) to request location information from a GMLC for certain target MSs. The interface is used by the GMLC to provide location information to an LCS client. This interface is external to a PLMN and is not defined within GSM.<br /> <br /> ===Splitting of the data storage===<br /> <br /> The data attached to each MS management, operation and location are stored in the Location Registers. Some data are duplicated in the HLR and in the VLR, but others may be stored only in one place.<br /> <br /> The data associated with any client that uses a particular GMLC to access location services is stored in the GMLC.<br /> <br /> ==Overload and compatibility overview==<br /> <br /> ===Overload control===<br /> <br /> There is a requirement for an overload/congestion control for all entities of the Public Land Mobile Network and the underlying Signalling System No. 7.<br /> <br /> ====Overload control for MSC (outside MAP)====<br /> <br /> For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load:<br /> * ISDN<br /> CCITT Recommendation Q.764 (Automatic Congestion Control), applicable to reduce the mobile terminating traffic;<br /> * BSSAP<br /> GSM 08.08 (A-interface Flow Control), applicable to reduce the mobile originating traffic.<br /> <br /> ====Overload control for MAP entities====<br /> <br /> For all MAP entities, especially the HLR, the following overload control method is applied:<br /> <br /> If overload of a MAP entity is detected, requests for certain MAP operations (see tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4) may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP service provider and is based upon the priority of the application context.<br /> <br /> Since most of the affected MAP operations are supervised in the originating entity by TC timers (medium) an additional delay effect is achieved for the incoming traffic.<br /> <br /> If overload levels are applicable in the Location Registers the MAP operations should be discarded taking into account the priority of their application context (see table 5.1/1 for HLR, table 5.1/2 for MSC/VLR, table 5.1/3 for the SGSN and table 5.1/4 for the SMLC; the lowest priority is discarded first).<br /> <br /> The ranking of priorities given in the tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4 is not normative. The tables can only be seen as a proposal which might be changed due to network operator/implementation matters.<br /> <br /> ====Congestion control for Signalling System No. 7====<br /> <br /> The requirements of SS7 Congestion control have to be taken into account as far as possible.<br /> <br /> Means which could be applied to achieve the required traffic reductions are described in subclauses 5.1.1 and 5.1.2.<br /> <br /> ===Compatibility===<br /> <br /> ====General====<br /> <br /> The present document of the Mobile Application Part is designed in such a way that an implementation which conforms to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR interface. <br /> <br /> A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol version used between two entities for supporting a MAP-user signalling procedure.<br /> <br /> When starting a signalling procedure, the MAP-user supplies an application-context-name to the MAP-provider. This name refers to the set of application layer communication capabilities required for this dialogue. This refers to the required TC facilities (e.g. version 1 or 2) and the list of operation packages (i.e. set of operations) from which operations can be invoked during the dialogue.<br /> <br /> A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP operational version 1).<br /> <br /> If the proposed application-context-name can be supported by the responding entity the dialogue continues on this basis otherwise the dialogue is refused and the initiating user needs to start a new dialogue, which involves another application-context-name which requires less communication capabilities but provides similar functionalities (if possible).<br /> <br /> When a signalling procedure can be supported by several application contexts which differ by their version number, the MAP-User needs to select a name. It can either select the name which corresponds to the highest version it supports or follow a more specific strategy so that the number of protocol fallbacks due to version compatibility problems be minimized.<br /> <br /> ====Strategy for selecting the Application Context (AC) version====<br /> <br /> A method should be used to minimize the number of protocol fall-backs which would occur sometimes if the highest supported AC-Name were always the one selected by GSM entities when initiating a dialogue. The following method is<br /> an example which can be used mainly at transitory phase stage when the network is one of mixed phase entities.<br /> <br /> =====Proposed method=====<br /> <br /> A table (table 1) may be set up by administrative action to define the highest application context (AC) version supported by each destination; a destination may be another node within the same or a different PLMN, or another PLMN considered as a single entity. The destination may be defined by an E.164 number or an E.214 number derived from an IMSI or in North America (World Zone 1) by an E.164 number or an IMSI (E.212 number). The table also includes the date when each destination is expected to be able to handle at least one AC of the latest version of the MAP protocol. When this date is reached, the application context supported by the node is marked as &quot;unknown&quot;, which will trigger the use of table 2.<br /> <br /> A second table (table 2) contains an entry for each destination which has an entry in table 1. For a given entity, the entry in table 2 may be a single application context version or a vector of different versions applying to different application contexts for that entity. Table 2 is managed as described in subclause 5.2.2.2.<br /> <br /> The data for each destination will go through the following states:<br /> <br /> &amp;nbsp;a) the version shown in table 1 is &quot;version n-1&quot;, where 'n' is the highest version existing in this specification; table 2 is not used;<br /> <br /> &amp;nbsp;b) the version shown in table 1 is &quot;unknown&quot;; table 2 is used, and maintained as described in subclause 5.2.2.2;<br /> <br /> &amp;nbsp;c) when the PLMN operator declares that an entity (single node or entire PLMN) has been upgraded to support all the MAP version n ACs defined for the relevant interface, the version shown in table 1 is set to &quot;version n&quot; by administrative action; table 2 is no longer used, and the storage space may be recovered.<br /> <br /> =====Managing the version look-up table=====<br /> <br /> '''WHEN''' it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the IMSI or the MSISDN.<br /> <br /> '''IF''' the entity number is known<br /> '''THEN'''<br /> It updates (if required) the associated list of highest supported ACs<br /> '''ELSE'''<br /> It creates an entry for this entity and includes the received AC-name in the list of highest supported ACs.<br /> <br /> '''WHEN''' starting a procedure, the originating MAP-user looks up its version control table.<br /> <br /> '''IF''' the destination address is known and not timed-out<br /> '''THEN'''<br /> It retrieves the appropriate AC-name and uses it<br /> '''IF''' the dialogue is accepted by the peer<br /> '''THEN'''<br /> It does not modify the version control table<br /> '''ELSE''' (this should never occur)<br /> It starts a new dialogue with the common highest version supported (based on information implicitly or explicitly provided by the peer).<br /> It replace the old AC-name by the new one in the list of associated highest AC supported.<br /> '''ELSE'''<br /> It uses the AC-name which corresponds to the highest version it supports.<br /> '''IF''' the dialogue is accepted by the peer<br /> '''THEN'''<br /> It adds the destination node in its version control table and includes the AC-Name in the list of associated highest AC supported.<br /> '''ELSE'''<br /> It starts a new dialogue with the common highest version supported (based on information implicitly or explicitly provided by the peer).<br /> '''IF''' the destination node was not known<br /> '''THEN'''<br /> It adds the destination node in its version control table and includes the new AC-Name in the list of associated highest AC supported.<br /> '''ELSE'''<br /> It replaces the old AC-name by the new one in the list of highest supported AC and reset the timer.<br /> <br /> =====Optimizing the method=====<br /> <br /> A table look-up may be avoided in some cases if both the HLR and the VLR or both the HLR and the SGSN store for each subscriber the version of the AC-name used at location updating. Then:<br /> <br /> * for procedures which make use of the same application-context, the same AC-name (thus the same version) can be selected (without any table look-up) when the procedure is triggered;<br /> * for procedures which make use of a different application-context but which includes one of the packages used by the location updating AC, the same version can be selected (without any table look-up) when the procedure is triggered;<br /> <br /> '''for HLR:'''<br /> <br /> *Subscriber data modification (stand alone);<br /> <br /> '''for VLR:'''<br /> <br /> *Data Restoration.<br /> <br /> ==Requirements concerning the use of SCCP and TC==<br /> <br /> ===Use of SCCP===<br /> <br /> The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full specification of SCCP. In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. Interworking between a PLMN in North America and a PLMN outside North America will involve an STP to translate between ANSI SCCP and ITU-T/CCITT SCCP.<br /> <br /> ====SCCP Class====<br /> <br /> MAP will only make use of the connectionless classes (0 or 1) of the SCCP.<br /> <br /> ====Sub-System Number (SSN)====<br /> <br /> The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are addressed by sub-system numbers (SSNs). The SSN for MAP are specified in GSM 03.03 [17].<br /> <br /> When the SGSN emulates MSC behavior for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, MAP_CHECK_IMEI) towards entities which do not support interworking to SGSNs, it shall use the MSC SSN in the calling party address instead of the SGSN SSN.<br /> <br /> ====SCCP addressing====<br /> <br /> =====Introduction=====<br /> <br /> Within the GSM System there will be a need to communicate between entities within the same PLMN and in different PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7.<br /> <br /> Only the entities which should be addressed are described below. If the CCITT or ITU-T SCCP is used , the format and coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 with the following restrictions:<br /> <br /> &lt;nowiki&gt;<br /> 1) Intra-PLMN addressing<br /> For communication between entities within the same PLMN, a MAP SSN shall always be included in the called and calling party addresses. All other aspects of SCCP addressing are network specific.<br /> <br /> 2) Inter-PLMN addressing<br /> a) Called Party Address<br /> * SSN indicator = 1 (MAP SSN always included);<br /> * Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator);<br /> * the translation type field will be coded &quot;00000000&quot; (Not used). For call related messages for non-optimal routed calls (as described in GSM 03.66) directed to another PLMN the translation type field may be coded &quot;10000000&quot; (CRMNP);<br /> * Routing indicator = 0 (Routing on global title);<br /> <br /> b) Calling Party Address<br /> * SSN indicator = 1 (MAP SSNs always included);<br /> * Point code indicator = 0;<br /> * Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator);<br /> * Numbering Plan = 0001 (ISDN Numbering Plan, E.164; In Case of Inter-PLMN Signalling, the dialogue initiating entity and dialogue responding entity shall always include its own E.164 Global Title as Calling Party Address);<br /> * the translation type field will be coded &quot;00000000&quot; (Not used);<br /> * Routing indicator = 0 (Routing on Global Title).<br /> &lt;/nowiki&gt;<br /> If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall comply with ANSI specification T1.112 with the following restrictions:<br /> <br /> &lt;nowiki&gt;<br /> 1) Intra-PLMN addressing<br /> <br /> For communication between entities within the same PLMN, a MAP SSN shall always be included in the called and calling party addresses. All other aspects of SCCP addressing are network specific.<br /> <br /> 2) Inter-PLMN addressing<br /> <br /> a) Called Party Address<br /> * SSN indicator = 1 (MAP SSN always included);<br /> * Global title indicator = 0010 (Global title includes translation type);<br /> * the Translation Type (TT) field will be coded as follows:<br /> TT = 9, if IMSI is included,<br /> TT = 14, if MSISDN is included,<br /> Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked.)<br /> * Routing indicator = 0 (Routing on global title);<br /> <br /> b) Calling Party Address<br /> * SSN indicator = 1 (MAP SSNs always included);<br /> * Point code indicator = 0;<br /> * Global title indicator = 0010 (Global title includes translation type);<br /> TT = 9, if IMSI is included,<br /> TT = 14, if MSISDN is included,<br /> Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked.)<br /> Routing indicator = 0 (Routing on Global Title).<br /> &lt;/nowiki&gt;<br /> <br /> If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and E.214 is applicable.<br /> <br /> * E.212 numbering plan<br /> <br /> &amp;nbsp;&amp;nbsp;When CCITT or ITU-T SCCP is used, an E.212 number must not be included as Global Title in an SCCP UNITDATA message. The translation of an E.212 number into a Mobile Global Title is applicable in a dialogue initiating VLR, SGSN or GGSN if the routeing information towards the HLR is derived from the subscriber's IMSI. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR. When an MS moves from one VLR service area to another, the new VLR may derive the address of the previous VLR from the Location Area Identification provided by the MS in the location registration request.<br /> <br /> &amp;nbsp;&amp;nbsp;The PLMN where the previous VLR is located is identified by the E.212 numbering plan elements of the Location Area Identification, ie the Mobile Country Code (MCC) and the Mobile Network Code (MNC).<br /> <br /> * E.214 and E.164 numbering plans<br /> <br /> &amp;nbsp;&amp;nbsp;When CCITT or ITU-T SCCP is used, , only address information belonging to either E.214 or E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. In World Zone 1 when<br /> ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR.<br /> <br /> &amp;nbsp;&amp;nbsp;If the Calling Party Address associated with the dialogue initiating message contains a Global Title, the sending network entity shall include its E.164 entity number.<br /> <br /> &amp;nbsp;&amp;nbsp;When receiving an SCCP UNITDATA message, SCCP shall accept either of the valid numbering plans in the Called Party Address and in the Calling Party Address.<br /> <br /> &amp;nbsp;&amp;nbsp;When CCITT or ITU-T SCCP is used and an N-UNITDATA-REQUEST primitive from TC is received, SCCP shall accept an E.164 number or an E.214 number in the Called Address and in the Calling Address. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used instead of E.214 number.<br /> <br /> <br /> The following subclauses describe the method of SCCP addressing appropriate for each entity both for the simple intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered:<br /> <br /> * the Mobile-services Switching Centre (MSC);<br /> * the Home location Register (HLR);<br /> * the Visitor Location Register (VLR);<br /> * the Gateway Mobile-services Switching Centre (GMSC);<br /> * the GSM Service Control Function (gsmSCF);<br /> * the Interworking Mobile-services Switching Centre (IWMSC);<br /> * the Shared Inter Working Function (SIWF);<br /> * the Serving GPRS Support Node (SGSN);<br /> * the Gateway GPRS Support Node (GGSN);<br /> * the Gateway Mobile Location Center (GMLC).<br /> <br /> =====The Mobile-services Switching Centre (MSC)=====<br /> <br /> There are several cases where it is necessary to address the MSC.<br /> <br /> ======MSC interaction during handover======<br /> <br /> The address is derived from the target Cellid.<br /> <br /> ======MSC for short message routing======<br /> <br /> When a short message has to be routed to a MS, the GMSC addresses the VMSC by an MSC identity received from the HLR which complies with E.164 rules.<br /> <br /> For MS originating short message, the IWMSC address is derived from the Service Centre address.<br /> <br /> ======MSC for location request routing======<br /> <br /> When a location request for a particular MS needs to be sent to the MS’s VMSC, the GMLC addresses the VMSC using an E.164 address received from the MS’s HLR.<br /> <br /> ======MSC for LMU Control======<br /> <br /> When a control message has to be routed to an LMU from an SMLC, the SMLC addresses the serving MSC for the LMU using an E.164 address.<br /> <br /> =====The Home Location Register (HLR)=====<br /> <br /> There are several cases where the HLR has to be addressed:<br /> <br /> ======During call set-up======<br /> <br /> When a call is initiated the HLR of the called mobile subscriber will be interrogated to discover the whereabouts of the MS. The addressing required by the SCCP will be derived from the MSISDN dialled by the calling subscriber. The dialled number will be translated into either an SPC, in the case of communications within a PLMN, or a Global Title if other networks are involved (i.e. if the communication is across a PLMN boundary).<br /> <br /> If the calling subscriber is a fixed network subscriber, the interrogation can be initiated from the Gateway MSC of the home PLMN in the general case. If the topology of the network allows it, the interrogation could be initiated from any Signalling Point which has MAP capabilities, e.g. local exchange, outgoing International Switching Centre (ISC), etc.<br /> <br /> ======Before location updating completion======<br /> <br /> When a MS registers for the first time in a VLR, the VLR has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the VLR has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing the established update location dialogue (as with any other dialogue), the VLR must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. This means that the VLR must be able to address the HLR based:<br /> <br /> * on an E.214 Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is used), or an E.212 number originally derived from IMSI (when ANSI SCCP is used, an IMSI); or<br /> <br /> * on an E.164 HLR address; or<br /> <br /> * in the case of intra-PLMN signalling, on an SPC.<br /> <br /> When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of the SCCP message containing the first responding CONTINUE message.<br /> <br /> If the HLR is in the same PLMN as the VLR, local translation tables may exist to derive an SPC. For authentication information retrieval and location updating via the international PSTN/ISDN signalling network that requires the use of CCITT or ITU-T SCCP, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. In World Zone 1 where the ANSI SCCP is used, IMSI (E.212 number) is used as Global Title. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT<br /> Recommendation E.214) is shown below:<br /> <br /> * E.212 Mobile Country Code translates to E.164 Country Code;<br /> <br /> * E.212 Mobile Network Code translates to E.164 National Destination Code;<br /> <br /> * E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits ). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by<br /> deleting the least significant digits.<br /> <br /> This translation will be done either at the application or at SCCP level in the VLR. The Mobile Global Title thus derived will be used to address the HLR.<br /> <br /> If location updating is triggered by an MS that roams from one MSC Area into a different MSC Area served by the same VLR, the VLR shall address the HLR in the same way as if the MS registers for the first time in the VLR.<br /> <br /> ======After location updating completion======<br /> <br /> In this case, the subscriber's basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with<br /> the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing information towards the HLR. This may apply in particular if the dialogue with the HLR is triggered by subscriber<br /> controlled input.<br /> <br /> Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the E.164 MSISDN or the E.164 number allocated to the HLR or either the E.214 Mobile Global Title derived from the IMSI if CCITT or ITU-T SCCP is used, or the IMSI if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).<br /> <br /> ======VLR restoration======<br /> <br /> If a roaming number is requested by the HLR for an IMSI that has no data record in the interrogated VLR, the VLR provides the roaming number in the dialogue terminating message. Subsequently the VLR must retrieve the<br /> authentication data from the MS's HLR, if required, and must then trigger the restore data procedure. For this purpose, the VLR has to initiate in succession two independent dialogues with the MS's HLR. The MTP and SCCP address information needed for routeing towards the HLR can be derived from the IMSI received as a parameter of the MAP message requesting the roaming number. In this case, the IMSI received from the HLR in the roaming number request shall be processed in the same way as the IMSI that is received from an MS that registers for the first time within a VLR. Alternatively to the IMSI, the Calling Party Address associated with the roaming number request may be used to obtain the routeing information towards the HLR.<br /> <br /> ======During Network-Requested PDP Context Activation======<br /> <br /> When receiving a PDP PDU the GGSN may interrogate the HLR of the MS for information retrieval. When initiating such a dialogue, the only data for addressing the HLR that the GGSN has available is contained in the IMSI, and<br /> addressing information must be derived from it. The IMSI is obtained from the IP address or the X.25 address in the incoming IP message by means of a translation table. This means that the GGSN shall be able to address the HLR based on an E.214, (if CCITT or ITU-T SCCP is used), or E.212 (if ANSI SCCP is used), Mobile Global Title originally derived by the GGSN from the IMSI in the case of inter-PLMN signalling. In the case of intra-PLMN signalling, an SPC may also be used.<br /> <br /> If the HLR is in the same PLMN as the GGSN, local translation tables may exist to derive an SPC. For information retrieval via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below:<br /> <br /> * E.212 Mobile Country Code translates to E.164 Country Code;<br /> <br /> * E.212 Mobile Network Code translates to E.164 National Destination Code;<br /> <br /> * E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.<br /> <br /> This translation will be done either at the application or at SCCP level in the GGSN. The Mobile Global Title thus derived will be used to address the HLR. <br /> <br /> ======Before GPRS location updating completion======<br /> <br /> When a MS registers for the first time in a SGSN, the SGSN has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the SGSN has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing the established update location dialogue (as with any other dialogue), the SGSN must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. This means that the SGSN must be able to address the HLR based:<br /> <br /> * on an E.214 (if CCITT or ITU-T SCCP is used) or E.212 (if ANSI SCCP is used) Mobile Global Title originally derived by the SGSN from the IMSI; or<br /> <br /> * on an E.164 HLR address; or<br /> <br /> * in the case of intra-PLMN signalling, on an SPC.<br /> <br /> If the HLR is in the same PLMN as the SGSN, local translation tables may exist to derive an SPC. For authentication information retrieval and location updating via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below:<br /> <br /> * E.212 Mobile Country Code translates to E.164 Country Code;<br /> <br /> * E.212 Mobile Network Code translates to E.164 National Destination Code;<br /> <br /> * E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits ). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.<br /> <br /> This translation will be done either at the application or at SCCP level in the SGSN. The Mobile Global Title thus derived will be used to address the HLR.<br /> <br /> ======After GPRS location updating completion======<br /> <br /> In this case, the subscriber's Basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing<br /> information towards the HLR.<br /> <br /> Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the E.164 MSISDN or the E.164 number allocated to the HLR or the E.214 Mobile Global Title derived from the IMSI.<br /> <br /> ======Query for a Location Request======<br /> <br /> For a location request from an external client, the GMLC needs to address the home HLR of the target MS to obtain the address of the target MS’s serving MSC. The GMLC uses either the international E.164 MSISDN, the international E.214 number (if CCITT or ITU-T SCCP is used) or the international E.212 number (if ANSI SCCP is used) of the MS as means to route a query to the HLR.<br /> <br /> =====The Visitor Location Register (VLR)=====<br /> <br /> There are several cases when the VLR needs to be addressed.<br /> <br /> ======Inter-VLR information retrieval======<br /> <br /> When an MS moves from one VLR service area to another, the new VLR may request the IMSI and authentication sets from the previous VLR. The new VLR derives the address of the previous VLR from the Location Area identification provided by the MS in the location registration request.<br /> <br /> ======HLR request======<br /> <br /> The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR's service area. This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has indicated successful completion of the update location procedure to the VLR.<br /> <br /> When initiating dialogues towards the VLR after successful completion of location updating, the routeing information used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the update location dialogue. If the VLR is in the same PLMN as the HLR, the VLR may be addressed directly by an SPC derived from the E.164 VLR number. For dialogues via the international PSTN/ISDN signalling network, presence of the E.164 VLR number in the Called Party Address is required.<br /> <br /> =====The Interworking MSC (IWMSC) for Short Message Service=====<br /> <br /> The IWMSC is the interface between the mobile network and the network to access to the Short Message Service Centre. This exchange has an E.164 address known in the SGSN or in the MSC.<br /> <br /> =====The Equipment Identity Register (EIR)=====<br /> <br /> The EIR address is either unique or could be derived from the IMEI. The type of address is not defined.<br /> <br /> =====The Shared Inter Working Function (SIWF)=====<br /> <br /> When the Visited MSC detects a data or fax call and the IWF in the V-MSC can not handle the required service an SIWF can be invoked. The SIWF is addressed with an E.164 number.<br /> <br /> =====The Serving GPRS Support Node (SGSN)=====<br /> <br /> The HLR will initiate dialogues towards the SGSN if it is aware that one of its subscribers is in the SGSN's serving area. This means that a GPRS location updating has been successfully completed, i.e, the HLR has indicated successful completion of the GPRS location update to the SGSN. The routeing information used by the HLR is derived form the E.164 SGSN number received as parameter of the MAP message initiating the GPRS update location procedure. If the SGSN is in the same PLMN as the HLR, the SGSN may be addressed directly by an SPC derived from the E.164 SGSN number. For dialogues via the international PSTN/ISDN signalling network, the presence of the E.164 SGSN number in the Called Party Address is required.<br /> <br /> When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See GSM 03.03) shall be included in the called party address. The routeing information used by the GMSC is derived from the E.164 SGSN number received<br /> as a parameter of the MAP message initiating the forward short message procedure. If the GMSC does not support the GPRS functionality the MSC (MAP) SSN value shall be included in the called party address.<br /> <br /> NOTE: Every VMSC and SGSN shall have uniquely identifiable application using E.164 numbers, for the purpose of SMS over GPRS when the GMSC does not support the GPRS functionality.<br /> <br /> =====The Gateway GPRS Support Node (GGSN)=====<br /> <br /> The GGSN provides interworking with external packet-switched networks, network screens and routing of the Network-Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the HLR will alert the GGSN when the subscriber becomes reachable. The HLR will use the E.164 GGSN number received as parameter of the MAP message reporting the failure.<br /> <br /> =====The Gateway MSC (GMSC) for Short Message Service=====<br /> <br /> The GMSC provides interworking with the network to access the Short Message Service Centre, the mobile network and routing of Send Routing Info For SM. The GMSC has on E.164 address known in the HLR, SGSN or MSC.<br /> <br /> =====Void=====<br /> <br /> ======Void======<br /> <br /> ======Void======<br /> <br /> =====The Gateway Mobile Location Center (GMLC)=====<br /> <br /> The GMLC initiates location requests on behalf of external clients. The E.164 address of the GMLC is provided to an HLR when the GMLC requests a serving MSC address from the HLR for a target MS. The E.164 address of the GMLC is also provided to a serving MSC when the GMLC requests the location of a target MS served by this MSC.<br /> <br /> =====Summary table=====<br /> <br /> The following tables summarize the SCCP address used for invoke operations. As a principle, within a PLMN either an SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT<br /> must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. <br /> <br /> For a response, the originating address passed in the invoke is used as SCCP Called Party Adress. For extra-PLMN addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP.<br /> <br /> &lt;center&gt;<br /> '''Table 6.1/1'''&lt;br/&gt;<br /> [[File:tabel611.png]]&lt;br/&gt;<br /> [[File:tabel6111.png]]&lt;br/&gt;<br /> <br /> '''Table 6.1/2'''&lt;br/&gt;<br /> <br /> [[File:tabel612.png]]<br /> &lt;/center&gt;<br /> <br /> ===Use of TC===<br /> <br /> The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of signalling system No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be<br /> consulted for the full specification of TC.<br /> <br /> The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility.<br /> <br /> From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is for further study.<br /> <br /> Transaction Capabilities refers to a protocol structure above the network layer interface (i.e, the SCCP service interface) up to the application layer including common application service elements but not the specific application service elements using them.<br /> <br /> TC is structured as a Component sub-layer above a Transaction sub-layer.<br /> The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives and TC-Component handling primitives respectively.<br /> <br /> Services for dialogue control include the ability to exchange information related to application-context negotiation as well as initialization data.<br /> <br /> Services for Remote Operation handling provide for the exchange of protocol data units invoking tasks (operations), and reporting their outcomes (results or errors) plus any non-application-specific protocol errors detected by the component sub-layer. The reporting of application-specific protocol errors by the TC user, as distinct from application process errors, is also provided. The Transaction sub-layer provides a simple end-to-end connection association service over which several related protocol data units (i.e. built by the Component Sub-Layer) can be exchanged. A Transaction termination can be prearranged (no indication provided to the TC user) or basic (indication provided).<br /> <br /> &lt;center&gt;<br /> '''Figure 6.2/1: Facilities for supporting the Mobile Application Part in Signalling System No.7'''&lt;br/&gt;<br /> [[File:tabel621.png]]<br /> &lt;/center&gt;<br /> <br /> ==General on MAP services==<br /> <br /> ===Terminology and definitions===<br /> <br /> The term service is used in clauses 7 to 12 as defined in CCITT Recommendation X.200. The service definition conventions of CCITT Recommendation X.210 are also used.<br /> <br /> ===Modelling principles===<br /> <br /> MAP provides its users with a specified set of services and can be viewed by its users as a &quot;black box&quot; or abstract machine representing the MAP service-provider. The service interface can then be depicted as shown in figure 7.2/1.<br /> <br /> &lt;center&gt;<br /> [[File:tabel721.png]]&lt;br/&gt;<br /> <br /> '''Figure 7.2/1: Modelling principles'''<br /> &lt;/center&gt;</div>

Monica https://ss7api.null.ro/index.php/ActivityTest 2013-08-26T10:23:25Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:activityTest}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used to check for the continued existence of a relationship between the gsmSCF and gsmSSF, gsmSCF and gsmSRF or gsmSCF and assistSSF. If the relationship is still in existence, then the gsmSSF, gsmSRF or assistSSF will respond.<br /> <br /> ==Expected actions==<br /> <br /> * When receiving this operation, the receiving end will respond the this invocation in order to acknowledge that the connection is still in existence.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation hasn't any invoke parameters.<br /> <br /> ==Result parameters==<br /> <br /> This operation expects a result.<br /> <br /> ==Example==<br /> <br /> &lt;component remoteCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;activityTest&quot;/&gt;</div>

Monica https://ss7api.null.ro/index.php/Cancel 2013-08-26T10:22:20Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:cancel}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to request the gsmSRF to cancel a correlated previous operation. The operation to be deleted can be either a PlayAnnouncement or a PromptAndCollectUserInformation operation. It can also be used to cancell all outstanding requests.<br /> <br /> ==Expected actions==<br /> <br /> <br /> ==Invoke parameters==<br /> <br /> * The operation contains one of the following parameters:<br /> ** '''invokeID''' – specifies the operation to be cancelled<br /> ** '''allRequests''' – indicates that all active requests for EventReportBCSM, ApplyChargingReport and CallInformationReport shall be cancelled.<br /> <br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;cancel&quot;&gt;<br /> &lt;cancelArg&gt;<br /> &lt;allRequests/&gt;<br /> &lt;/cancelArg&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/SpecializedResourceReport 2013-08-26T10:21:16Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:specializedResourceReport}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSRF to indicate as a response to the gsmSCF that a “PlayAnnouncement” operation that the announcement was completed when a report indication was set.<br /> <br /> ==Expected actions==<br /> <br /> ==Invoke parameters==<br /> <br /> This operation has not any Invoke parameters.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;specializedResourceReport&quot;/&gt;</div>

Monica https://ss7api.null.ro/index.php/PromptAndCollectUserInformation 2013-08-26T10:20:08Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:promptAndCollectUserInformation}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is used to interact with a user to collect information. When the gsmSRF is colocated with the gsmSSF, this operation is relayed from the gsmSCF to the gsmSRF via the gsmSSF.<br /> <br /> ==Expected actions==<br /> <br /> ==Invoke parameters==<br /> <br /> * '''CollectedInfo''' – contains the following list:<br /> ** '''collectedDigits'''<br /> *** '''minimumNbOfDigits''' – minimum number of digits to be collected. Defaults to 1.<br /> *** '''maximumNbOfDigits''' – maximum number of digits to be collected.<br /> *** ''endofReplyDigit'' – indicates the digit(s) to signal end of input. It can be one or 2 digits.<br /> *** ''cancelDigit'' – indicates the cancel digit for a possible retry. It can be one or 2 digits.<br /> *** ''startDigit'' – indicates the start digit for collecting valid digits. It can be one or 2 digits.<br /> *** ''firstDigitTimeOut'' – timer value for the first digit to be received.<br /> *** ''InterDigitTimeOut'' – timer value for maximum interval at which digits should be received.<br /> *** ''errorTreatment'' – indicates the error treatment to the gsmSRF. It can have the following values:<br /> **** stdErrorAndInfo<br /> **** help<br /> **** repeatPrompt<br /> *** ''interruptableAnnInd'' – if this parametes is set to true, the announcement is interrupted after the first digit received by the gsmSRF, otherwise the digits received during the announcement are discarded.<br /> *** ''voiceInformation'' – if this parametes is set to false, all valid/invalid digits are entered by DTMF, otherwise the user is required to provide information by speech.<br /> *** ''voiceBack'' – if this parameter is set to true, the valid input digits received by the gsmSRF are announced back to the user immediately. Invalid digits or an end digits are not reported back.<br /> * '''disconnectFromIPForbidden''' – indicates whether the gsmSRF shall be disconnected from the user when all information has been sent.<br /> * ''informationToSend'' - indicates an announcement or tone to be sent to the end user by the gsmSRF. It's a choice between the following parameters:<br /> ** '''inbandInfo''' – specifies the inband information to be sent:<br /> **** '''messageID''' – the message to be sent and can be one of the following:<br /> ***** '''elementaryMessageID''' – indicates a single announcement.<br /> ***** '''text''' – indicates a text to be sent. The text will be transformed to inband information by the gsmSRF....<br /> ***** '''elementaryMessageIDs''' – indicates a series of announcements. ..<br /> ***** '''variableMessage''' – indicates a message with one or more variable parts...<br /> **** ''numberOfRepetitions'' – the maximum number of times the message shall be sent to the user.<br /> **** ''duration'' – the maximum duration in seconds that the message shall be played. A value of zero indicates endless repetition.<br /> **** ''interval'' – indicates interval in seconds between repetitions.<br /> *** '''tone''' – indicates a tone to be sent to the user by:<br /> **** '''toneID''' – the id of the tone to be sent<br /> **** ''toneDuration'' – duration in seconds of the tone to be sent. Zero indicates infinite duration.<br /> <br /> * ''extensions''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;promptAndCollectUserInformation&quot;&gt;<br /> &lt;collectedInfo&gt;<br /> &lt;collectedDigits&gt;<br /> &lt;minimumNbOfDigits&gt;3&lt;/minimumNbOfDigits&gt;<br /> &lt;maximumNbOfDigits&gt;10&lt;/maximumNbOfDigits&gt;<br /> &lt;endOfReplyDigit&gt;22&lt;/endOfReplyDigit&gt;<br /> &lt;cancelDigit&gt;84&lt;/cancelDigit&gt;<br /> &lt;startDigit&gt;57&lt;/startDigit&gt;<br /> &lt;firstDigitTimeOut&gt;2&lt;/firstDigitTimeOut&gt;<br /> &lt;interDigitTimeOut&gt;1&lt;/interDigitTimeOut&gt;<br /> &lt;errorTreatment&gt;help&lt;/errorTreatment&gt;<br /> &lt;interruptableAnnInd&gt;true&lt;/interruptableAnnInd&gt;<br /> &lt;voiceInformation&gt;true&lt;/voiceInformation&gt;<br /> &lt;voiceBack&gt;false&lt;/voiceBack&gt;<br /> &lt;/collectedDigits&gt;<br /> &lt;/collectedInfo&gt;<br /> &lt;disconnectFromIPForbidden&gt;true&lt;/disconnectFromIPForbidden&gt;<br /> &lt;informationToSend&gt;<br /> &lt;inbandInfo&gt;<br /> &lt;messageID&gt;<br /> &lt;text&gt;<br /> &lt;messageContent&gt;Text&lt;/messageContent&gt;<br /> &lt;attributes&gt;84 79 32 01 25&lt;/attributes&gt;<br /> &lt;/text&gt;<br /> &lt;/messageID&gt;<br /> &lt;numberOfRepetitions&gt;3&lt;/numberOfRepetitions&gt;<br /> &lt;duration&gt;5&lt;/duration&gt;<br /> &lt;interval&gt;10&lt;/interval&gt;<br /> &lt;/inbandInfo&gt;<br /> &lt;/informationToSend&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/PlayAnnouncement 2013-08-26T10:18:16Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:playAnnouncement}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is to be used by the gsmSCF and sent to the gsmSRF after Establish Temporary Connection (assist procedure with a second gsmSSF) or a Connect to Resource (no assist) operation. It may be used for inband user interaction with a Mobile Station.<br /> <br /> ==Expected actions==<br /> <br /> * On receipt of this operation the gsmSSF performs actions to send the advice of charge information to the indicated Call Party's MS (Mobile Station).<br /> <br /> ==Invoke parameters==<br /> <br /> * '''informationToSend''' – it's a choice between the following parameters:<br /> ** '''inbandInfo''' – specifies the inband information to be sent:<br /> *** '''messageID''' – the message to be sent and can be one of the following:<br /> **** '''elementaryMessageID''' – indicates a single announcement.<br /> **** '''text''' – indicates a text to be sent. The text will be transformed to inband information by the gsmSRF....<br /> **** '''elementaryMessageIDs''' – indicates a series of announcements. ..<br /> **** '''variableMessage''' – indicates a message with one or more variable parts...<br /> *** ''numberOfRepetitions'' – the maximum number of times the message shall be sent to the user.<br /> *** ''duration'' – the maximum duration in seconds that the message shall be played. A value of zero indicates endless repetition.<br /> *** ''interval'' – indicates interval in seconds between repetitions.<br /> ** '''tone''' – indicates a tone to be sent to the user by:<br /> *** '''toneID''' – the id of the tone to be sent<br /> *** ''toneDuration'' – duration in seconds of the tone to be sent. Zero indicates infinite duration.<br /> * '''disconnectFromIPForbidden''' – indicates whether the gsmSRF shall be disconnected from the user when all information has been sent.<br /> * '''requestAnnouncementComplete''' - indicates whether a SpecializedResourceReport shall be sent when all information has been sent.<br /> * ''extensions''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;playAnnouncement&quot;&gt;<br /> &lt;informationToSend&gt;<br /> &lt;tone&gt;<br /> &lt;toneID&gt;5&lt;/toneID&gt;<br /> &lt;duration&gt;10&lt;/duration&gt;<br /> &lt;/tone&gt;<br /> &lt;/informationToSend&gt;<br /> &lt;disconnectFromIPForbidden&gt;false&lt;/disconnectFromIPForbidden&gt;<br /> &lt;requestAnnouncementComplete&gt;true&lt;/requestAnnouncementComplete&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/SendChargingInformation 2013-08-26T10:16:56Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:sendChargingInformation}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to instruct the gsmSSF on the advice of charge information to be sent by the gsmSSF. The SCI operation may be invoked on multiple occasions.<br /> <br /> ==Expected actions==<br /> <br /> * On receipt of this operation the gsmSSF performs actions to send the advice of charge information to the indicated Call Party's MS (Mobile Station).<br /> <br /> ==Invoke parameters==<br /> <br /> * '''sCIBillingChargingCharacteristics''' – it's a choice between the following parameters:<br /> ** ''' aOCBeforeAnswer''' – list of parameters sent only before an answer event was detected. It contains the following parameters:<br /> *** '''aOCInitial''' - a set of GSM Charge Advice Information elements, as defined in GSM 02.24 and these CAI elements are sent by the gsmSSF to the MS when an ANSWER is received and a tariff switch has not yet occurred.<br /> **** ''e1, e2, e3, e4, e5, e6, e7''<br /> *** ''aOCSubsequent'' – a list containing the following information:<br /> **** '''cAI-GSM0224''' - a set of GSM Charge Advice Information elements, as defined in GSM 02.24 and these CAI elements are sent by the gsmSSF to the MS when an ANSWER is detected and a tariff switch occurs.<br /> ***** ''e1, e2, e3, e4, e5, e6, e7''<br /> **** ''tariffSwitchInterval'' – indicates to the gsmSSF the time duration until the next tariff switch.<br /> ** ''' aOCAfterAnswer''' – list of parameters sent only after an answer event was detected. It contains the following parameters:<br /> *** '''cAI-GSM0224''' - a set of GSM Charge Advice Information elements, as defined in GSM 02.24 and these CAI elements are sent by the gsmSSF to the MS when an ANSWER is detected and a tariff switch has occurred previously or when an Answer has been previously detected and a tariff switch occurs.<br /> **** ''e1, e2, e3, e4, e5, e6, e7''<br /> *** ''tariffSwitchInterval'' – indicates to the gsmSSF the time duration until the next tariff switch.<br /> * '''partyToCharge''' – indicates where the charging information is to be sent.<br /> <br /> * ''extensions''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;sendChargingInformation&quot;&gt;<br /> &lt;sCIBillingChargingCharacteristics&gt;<br /> &lt;aOCBeforeAnswer&gt;<br /> &lt;aOCInitial&gt;<br /> &lt;e1&gt;1&lt;/e1&gt;<br /> &lt;e2&gt;2&lt;/e2&gt;<br /> &lt;/aOCInitial&gt;<br /> &lt;aOCSubsequent&gt;<br /> &lt;cAI-GSM0224&gt;<br /> &lt;e1&gt;1&lt;/e1&gt;<br /> &lt;e2&gt;2&lt;/e2&gt;<br /> &lt;e3&gt;3&lt;/e3&gt;<br /> &lt;/cAI-GSM0224&gt;<br /> &lt;tariffSwitchInterval&gt;65&lt;/tariffSwitchInterval&gt;<br /> &lt;/aOCSubsequent&gt;<br /> &lt;/aOCBeforeAnswer&gt;<br /> &lt;/sCIBillingChargingCharacteristics&gt;<br /> &lt;partyToCharge&gt;<br /> &lt;sendingSideID&gt;leg2&lt;/sendingSideID&gt;<br /> &lt;/partyToCharge&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/CallInformationRequest 2013-08-26T10:14:11Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:callInformationRequest}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is sent by the gsmSCF to the gsmSSF to request that it collect specific information about a single call and reported back to the gsmSCF using the [[callInformationReport]] operation.<br /> <br /> ==Expected actions==<br /> <br /> * The gsmSSF allocates a record and will retain the requested information about the call.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''requestedInformationTypeList''' – contains a list of requested information types:<br /> ** '''requestedInformationType''' – type of requested information. Can have one the following values:<br /> *** callAttemptElapsedTime – duration between the end of processing for initial call setup and the answer indication.<br /> *** callStopTime – timestamp for when the call was released.<br /> *** callConnectedElapsedTime – request the duration between the answer and the release of the call.<br /> *** releaseCause – request the release cause for the call<br /> * ''extensions''<br /> <br /> * ''legID'' – indicates the party for which the information has to be collected. If absent, it indicated the outgoing call leg.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;callInformationRequest&quot;&gt;<br /> &lt;requestedInformationTypeList&gt;<br /> &lt;requestedInformationType&gt;callStopTime&lt;/requestedInformationType&gt;<br /> &lt;/requestedInformationTypeList&gt;<br /> &lt;legID&gt;<br /> &lt;sendingSideID&gt;leg2&lt;/sendingSideID&gt;<br /> &lt;/legID&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/CallInformationReport 2013-08-26T10:13:18Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:callInformationReport}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is sent by the gsmSSF to the gsmSCF to provide the gsmSCF with specific call information for a single call as requested in a previous [[callInformationRequest]].<br /> <br /> ==Expected actions==<br /> <br /> * The report is sent at the end of a call/call party connection.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''requestedInformationList''' – list of the following parameters:<br /> ** '''requestedInformation''' – contains the following 2 parameters:<br /> *** '''requestedInformationType''' – type of requested information. Can have one the following values:<br /> **** callAttemptElapsedTime<br /> **** callStopTime<br /> **** callConnectedElapsedTime<br /> **** releaseCause<br /> *** requestedInformationValue – the value for the requested information type<br /> <br /> * ''extensions''<br /> <br /> * ''legID'' – indicates the party for which the information has been collected. If absent, it indicated the outgoing call leg.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;callInformationReport&quot;&gt;<br /> &lt;requestedInformationList&gt;<br /> &lt;requestedInformation&gt;<br /> &lt;requestedInformationType&gt;<br /> callConnectedElapsedTime<br /> &lt;/requestedInformationType&gt;<br /> &lt;requestedInformationValue&gt;<br /> &lt;callStopTimeValue&gt;500&lt;/callStopTimeValue&gt;<br /> &lt;/requestedInformationValue&gt;<br /> &lt;/requestedInformation&gt;<br /> &lt;/requestedInformationList&gt;<br /> &lt;legID&gt;<br /> &lt;receivingSideID&gt;leg1&lt;/receivingSideID&gt;<br /> &lt;/legID&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/ApplyChargingReport 2013-08-26T10:10:40Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:applyChargingReport}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation provides the feedback from the gsmSSF to the gsmSCF regarding the charging related information as previously requested by the gsmSCF by using the [[applyCharging]] operation.<br /> <br /> ==Expected actions==<br /> <br /> * When the gsmSSF detects that a call was disconnected pr that the period indicated by the “maxCallPeriodDuration” has been excedeed, a report is sent to the gsmSCF.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''callResult''' – contains the charging related information. It contains the following parameter:<br /> ** '''timeDurationChargingResult''' – list of parameters containing:<br /> *** '''partyToCharge''' – the leg which is to be charged, as received in the related “ApplyCharging” operation. Contains the “receivingSideID” parameter.<br /> *** '''timeInformation''' – this is a choice between the following parameters:<br /> **** '''timeIfNoTariffSwitch''' – parameter is present if no tariff switch has occurred. Specifies the time elapsed since the detection of the “Answer” event. <br /> **** '''TimeIfTariffSwitch – parameter is present if a tariff switch has occurred. It contains the parameters:'''<br /> ***** '''timeSinceTariffSwitch''' – elapsed time since the last tariff switch.<br /> ***** ''TariffSwitchInterval'' – interval between the previous tariff switch and the last tariff switch reported.<br /> *** '''callActive''' – true if the call is still active, false if it has been released.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;applyChargingReport&quot;&gt;<br /> &lt;callResult&gt;<br /> &lt;timeDurationChargingResult&gt;<br /> &lt;partyToCharge&gt;<br /> &lt;receivingSideID&gt;leg2&lt;/receivingSideID&gt;<br /> &lt;/partyToCharge&gt;<br /> &lt;timeInformation&gt;<br /> &lt;timeIfTariffSwitch&gt;<br /> &lt;timeSinceTariffSwitch&gt;60&lt;/timeSinceTariffSwitch&gt;<br /> &lt;tariffSwitchInterval&gt;120&lt;/tariffSwitchInterval&gt;<br /> &lt;/timeIfTariffSwitch&gt;<br /> &lt;/timeInformation&gt;<br /> &lt;callActive&gt;false&lt;/callActive&gt;<br /> &lt;/timeDurationChargingResult&gt;<br /> &lt;/callResult&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/ApplyCharging 2013-08-26T10:09:07Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:applyCharging}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to interact with the CSE control of call duration function of the gsmSSF. <br /> <br /> ==Expected actions==<br /> <br /> * On receipt of this operation, the gsmSSF sets the charging data using the information set in this operation.<br /> <br /> * The gsmSSF will start monitoring for the “Answer” event when receiving this operation if the answer has not been already received. When detecting the “Answer” event on the outgoing connection, the charging is started (or charging starts immediately if answer was already received).<br /> <br /> ==Invoke parameters==<br /> <br /> * '''aCHBillingChargingCharacteristics''' – specifies the parameters for the control of the call duration. It contains the following parameter:<br /> <br /> * '''timeDurationCharging''' – specifies the following parameters:<br /> ** '''maxCallPeriodDuration''' – duration of time for which a call can progress before an “ApplyChargingReport” is to be sent to the gsmSCF.<br /> *** ''releaseIfdurationExceeded'' – specifies the action to be taken by the gsmSSF when the duration specified above is reached. The presence of this parameter implies that the call should be released. It contains two parameters:<br /> **** '''tone''' – if true, a warning tone should be played before releasing the call.<br /> **** ''extensions''<br /> *** ''tariffSwitchInterval'' - <br /> * '''partyToCharge''' - indicates the party in the call. Contains the parameter “sendingSideID”.<br /> * ''extensions''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;applyCharging&quot;&gt;<br /> &lt;aChBillingChargingCharacteristics&gt;<br /> &lt;timeDurationCharging&gt;<br /> &lt;maxCallPeriodDuration&gt;120&lt;/maxCallPeriodDuration&gt;<br /> &lt;releaseIfdurationExceeded&gt;<br /> &lt;tone&gt;true&lt;/tone&gt;<br /> &lt;/releaseIfdurationExceeded&gt;<br /> &lt;tariffSwitchInterval&gt;60&lt;/tariffSwitchInterval&gt;<br /> &lt;/timeDurationCharging&gt;<br /> &lt;/aChBillingChargingCharacteristics&gt;<br /> &lt;partyToCharge&gt;<br /> &lt;sendingSideID&gt;leg2&lt;/sendingSideID&gt;<br /> &lt;/partyToCharge&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/FurnishChargingInformation 2013-08-26T10:04:59Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:furnishChargingInformation}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to request the gsmSSF to generate, to register a logical call record or to include some information in the default call record used for charging the call. The logicall call record is CAMEL specific.<br /> <br /> ==Expected actions==<br /> <br /> * The first FCI (Furnish Call Information) of a call leg leads to the generation of the logical call record.<br /> <br /> * Subsequent FCIs on the same call leg shall overwrite the contents of the call record.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''fCIBillingChargingCharacteristics''' – contains the following parameter:<br /> ** '''fCIBCCCAMELsequence1''' – contains the following parameters:<br /> *** '''freeFormatData''' - indicates free-format billing and/or charging characteristics.<br /> *** '''partyToCharge''' – indicates the party to be billed. Contains the parameter “sendingSideID”.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;furnishChargingInformation&quot;&gt;<br /> &lt;fCIBillingChargingCharacteristics&gt;<br /> &lt;fCIBCCCAMELsequence1&gt;<br /> &lt;freeFormatData&gt;99 94 40 62&lt;/freeFormatData&gt;<br /> &lt;partyToCharge&gt;<br /> &lt;sendingSideID&gt;leg2&lt;/sendingSideID&gt;<br /> &lt;/partyToCharge&gt;<br /> &lt;/fCIBCCCAMELsequence1&gt;<br /> &lt;/fCIBillingChargingCharacteristics&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/ResetTimer 2013-08-26T10:03:52Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:resetTimer}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to request the gsmSSF to refresh an application timer in the gsmSSF in order to avoid a timeout at the gsmSSF.<br /> <br /> ==Expected actions==<br /> <br /> * The gsmSSF will continue call processing without substituting new data from gsmSCF.<br /> * Basic call processing is resumed.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''timerID''' – specifies the timer to be set. It has to have the value “tssf” (TSSF).<br /> <br /> * '''''timerValue''''' – the value in seconds at which the TSSF is to be set.<br /> <br /> * ''extensions''<br /> <br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;resetTimer&quot;&gt;<br /> &lt;timerID&gt;tssf&lt;/timerID&gt;<br /> &lt;timervalue&gt;30&lt;/timervalue&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/Continue 2013-08-26T10:02:51Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:continue}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to request the gsmSSF to proceed with call processing from a DP at which the call was previously suspended in order to await instructions from the gsmSCF.<br /> <br /> ==Expected actions==<br /> <br /> * The gsmSSF will continue call processing without substituting new data from gsmSCF.<br /> <br /> * Basic call processing is resumed.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation does not have Invoke parameters.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;continue&quot;/&gt;</div>

Monica https://ss7api.null.ro/index.php/EventReportBCSM 2013-08-26T10:00:51Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:eventReportBCSM}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSSF to notify the gsmSCF of a call related event for which monitoring was previously requested through a RequestReportBCSMEvent operation. <br /> <br /> ==Expected actions==<br /> <br /> * While monitoring of multiple events can be requested through a single RequestReportBCSMEvent operation, each monitored event is reported separately through a EventReportBCSM.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''eventTypeBCSM''' – the type of event being reported. Possible values are: <br /> ** collectedInfo<br /> ** routeSelectFailure<br /> ** oCalledPartyBusy<br /> ** oNoAnswer<br /> ** oDisconnect<br /> ** oAbandon<br /> ** termAttemptAuthorized<br /> ** tBusy<br /> ** tNoAnswer<br /> ** tAnswer<br /> ** tDisconnect<br /> ** tAbandon<br /> * ''eventSpecificInformationBCSM'' - contains specific call related information:<br /> ** for eventTypeBCSM “routeSelectFailure”, this parameter will contain the “failureCause” if available.<br /> ** for “tBusy”, “busyCause” may be present.<br /> ** for “tNoAnswer”, the parameter may contain the “callForwarded” reason.<br /> ** for “oDisconnect”/”tDisconnect”, the parameter will contain the “releaseCause” if possible.<br /> ** for events “oNoAnswer”, “oAnswer”, “tAnswer”, this parameter will be empty.<br /> * ''legID'' – the party of the call for which the event is reported. In this case, the gsmSSF will use the “receivingSideID” option only.<br /> * ''miscCallInfo'' – indicates the DP (Detection Point) related information. It contains the following parameter:<br /> ** messageType: can have values “request”/”notification”<br /> <br /> * ''extensions''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component remoteCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;eventReportBCSM&quot;&gt;<br /> &lt;eventTypeBCSM&gt;tDisconnect&lt;/eventTypeBCSM&gt;<br /> &lt;eventSpecificInformationBCSM&gt;<br /> &lt;oCalledPartyBusySpecificInfo&gt;<br /> &lt;busyCause&gt;29 03&lt;/busyCause&gt;<br /> &lt;/oCalledPartyBusySpecificInfo&gt;<br /> &lt;/eventSpecificInformationBCSM&gt;<br /> &lt;legID&gt;<br /> &lt;receivingSideID&gt;leg2&lt;/receivingSideID&gt;<br /> &lt;/legID&gt;<br /> &lt;miscCallInfo&gt;<br /> &lt;messageType&gt;notification&lt;/messageType&gt;<br /> &lt;/miscCallInfo&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/RequestReportBCSMEvent 2013-08-26T09:58:15Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:requestReportBCSMEvent}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used to request by the gsmSCF that the gsmSSF should monitor for a call event (e.g., busy or no answer), then send a notification back to the gsmSCF when the event is detected.<br /> <br /> ==Expected actions==<br /> <br /> * The requested events are monitored until the monitoring is ended, until the end of the call, until the requested events are detected or the corresponding call leg is released.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''bcsmEvents''' – list of parameters which specify the event/events for which a report is requested. An event is specified by the following parameters:<br /> ** '''eventTypeBCSM''' – type of event for which a report is requested. Values “collectedInfo” and “termAttemptAuthorize” aren't valid for this operation.<br /> ** '''monitorMode''' – indicates how the event is to be reported. If its value is “interrupted”, the event is reported as a request, if its value is “notifyAndContinue”, the event is reported as a notification, if its value is “transparent”, the event is not reported.<br /> ** ''legID'' – the party of the call for which the event is to be reported. The gsmSCF uses only the “sendingSideID” only.<br /> *** '''sendingSideID'''<br /> ** dPSpecificCriteria – specific information specific to the DP to be armed<br /> *** '''applicationTimer'''<br /> * extensions<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;requestReportBCSMEvent&quot;&gt;<br /> &lt;bcsmEvents&gt;<br /> &lt;bcsmEvent&gt;<br /> &lt;eventTypeBCSM&gt;tAnswer&lt;/eventTypeBCSM&gt;<br /> &lt;monitorMode&gt;transparent&lt;/monitorMode&gt;<br /> &lt;legID&gt;<br /> &lt;receivingSideID&gt;leg2&lt;/receivingSideID&gt;<br /> &lt;/legID&gt;<br /> &lt;dPSpecificCriteria&gt;<br /> &lt;applicationTimer&gt;25&lt;/applicationTimer&gt;<br /> &lt;/dPSpecificCriteria&gt;<br /> &lt;/bcsmEvent&gt;<br /> &lt;/bcsmEvents&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/ReleaseCall 2013-08-26T09:54:46Z

<p>Oana: /* Example */ Updated documentation</p> <hr /> <div>{{DISPLAYTITLE:releaseCall}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is used by the gsmSCF to tear down an existing call at any phase of the call for all parties involved in the call. <br /> <br /> ==Expected actions==<br /> <br /> * Upon the receipt of this operation, the gsmSCF will release the call in all directions with the cause indicator specified by the “cause” parameter.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''cause''' – the reason for releasing the call. This is a Q.850 cause. This has the following attributes:<br /> ** ''coding'' with possible values<br /> *** &quot;CCITT&quot;<br /> *** &quot;ISO/IEC&quot;<br /> *** &quot;national&quot;<br /> *** &quot;network specific&quot;<br /> ** ''location'' with possible values:<br /> *** &quot;U&quot; - User<br /> *** &quot;LPN&quot; - Private network serving the local user<br /> *** &quot;LN&quot; - Public network serving the local user<br /> *** &quot;TN&quot; - Transit network<br /> *** &quot;RLN&quot; - Public network serving the remote user<br /> *** &quot;RPN&quot; - Private network serving the remote user<br /> *** &quot;INTL - International network<br /> *** &quot;BI&quot; - Network beyond the interworking point<br /> <br /> Values for CCITT causes are:<br /> * &quot;normal-event&quot;<br /> * &quot;unallocated&quot; - Unallocated (unassigned) number<br /> * &quot;noroute-to-network&quot; - No route to specified transit network<br /> * &quot;noroute&quot; - No route to destination<br /> * &quot;send-info-tone&quot; - Send special information tone<br /> * &quot;misdialed-trunk-prefix&quot; - Misdialed trunk prefix<br /> * &quot;channel-unacceptable&quot; - Channel unacceptable<br /> * &quot;call-delivered&quot; - Call awarded and being delivered in an established channel<br /> * &quot;preemption&quot; - Preemption<br /> * &quot;preemption-circuit-reserved&quot; - Preemption circuit reserved for re-use<br /> * &quot;ported-number&quot; - QoR: ported number Q.850 Addendum 1 (06/2000)<br /> * &quot;excess-digits&quot; - Excess digits received, call is proceeding<br /> * &quot;normal-clearing&quot; - Normal Clearing<br /> * &quot;busy&quot; - User busy<br /> * &quot;noresponse&quot; - No user responding<br /> * &quot;noanswer&quot; - No answer from user (user alerted)<br /> * &quot;offline&quot; - Subscriber absent<br /> * &quot;rejected&quot; - Call Rejected<br /> * &quot;moved&quot; - Number changed<br /> * &quot;redirection&quot; - Redirection to new destination Q.850 05/98<br /> * &quot;rejected-by-feature&quot; - Call rejected due to feature at the destination Q.850 Amendment 1 (07/2001)<br /> * &quot;looping&quot; - Exchange routing error (hop counter) Q.850 05/98<br /> * &quot;answered&quot; - Non-selected user clearing (answered elsewhere)<br /> * &quot;out-of-order&quot; - Destination out of order<br /> * &quot;invalid-number&quot; - Invalid number format<br /> * &quot;facility-rejected&quot; - Facility rejected<br /> * &quot;status-enquiry-rsp&quot; - Response to STATUS ENQUIRY<br /> * &quot;normal&quot; - Normal, unspecified<br /> * &quot;resource-unavailable&quot; - Resource unavailable<br /> * &quot;congestion&quot; / &quot;channel-congestion&quot; - No circuit/channel available<br /> * &quot;net-out-of-order&quot; - Network out of order<br /> * &quot;frame-mode-conn-down&quot; - Permanent frame mode connection out of service<br /> * &quot;frame-mode-conn-up&quot; - Permanent frame mode connection operational<br /> * &quot;temporary-failure&quot; / &quot;noconn&quot;- Temporary failure<br /> * &quot;congestion&quot; / &quot;switch-congestion&quot; - Switching equipment congestion<br /> * &quot;access-info-discarded&quot; - Access information discarded<br /> * &quot;channel-unavailable&quot; - Requested channel not available<br /> * &quot;preemption-congestion&quot; - Precedence call blocked<br /> * &quot;noresource&quot; - Resource unavailable, unspecified<br /> * &quot;service-unavailable&quot; - Service or option not available<br /> * &quot;qos-unavailable&quot; - Quality of service unavailable<br /> * &quot;facility-not-subscribed&quot; - Requested facility not subscribed<br /> * &quot;forbidden-out&quot; - Outgoing call barred within CUG<br /> * &quot;forbidden-in&quot; - Incoming call barred within CUG<br /> * &quot;bearer-cap-not-auth&quot; - Bearer capability not authorized<br /> * &quot;bearer-cap-not-available&quot; / &quot;nomedia&quot; - Bearer capability not presently available<br /> * &quot;invalid-access-info-out&quot; - Inconsistency in designated outgoing access information and subscriber class<br /> * &quot;service-unavailable&quot; - Service or option not available<br /> * &quot;bearer-cap-not-implemented&quot; - Bearer capability not implemented<br /> * &quot;channel-type-not-implemented&quot; - Channel type not implemented<br /> * &quot;facility-not-implemented&quot; - Requested facility not implemented<br /> * &quot;restrict-bearer-cap-avail&quot; - Only restricted digital information bearer capability is available<br /> * &quot;service-not-implemented&quot; - Service or option not implemented, unspecified<br /> * &quot;invalid-callref&quot; - Invalid call reference value<br /> * &quot;unknown-channel&quot; - Identified channel does not exist<br /> * &quot;unknown-callid&quot; - A suspended call exists, but this call identity does not<br /> * &quot;duplicate-callid&quot; - Call identity in use<br /> * &quot;no-call-suspended&quot; - No call suspended<br /> * &quot;suspended-call-cleared&quot; - Call having the requested call identity has been cleared<br /> * &quot;not-subscribed&quot; - User not member of CUG<br /> * &quot;incompatible-dest&quot; - Incompatible destination<br /> * &quot;unknown-group&quot; - Non-existent CUG<br /> * &quot;invalid-transit-net&quot; - Invalid transit network selection<br /> * &quot;invalid-message&quot; - Invalid message, unspecified<br /> * &quot;missing-mandatory-ie&quot; - Mandatory information element is missing<br /> * &quot;unknown-message&quot; - Message type non-existent or not implemented<br /> * &quot;wrong-message&quot; - Message not compatible with call state, non-existent or not implemented<br /> * &quot;unknown-ie&quot; - Information element non-existent or not implemented<br /> * &quot;invalid-ie&quot; - Invalid information element contents<br /> * &quot;wrong-state-message&quot; - Message not compatible with call state<br /> * &quot;timeout&quot; - Recovery on timer expiry<br /> * &quot;unknown-param-passed-on&quot; - Parameter non-existent or not implemented, passed on<br /> * &quot;unknown-param-message-droppped&quot; - Message with unrecognized parameter, discarded<br /> * &quot;protocol-error&quot; - Protocol error, unspecified<br /> * &quot;interworking&quot; - Interworking, unspecified<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> <br /> With decoded Q.850 cause:<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;releaseCall&quot;&gt;<br /> &lt;cause coding=&quot;CCITT&quot; location=&quot;LN&quot;&gt;<br /> noconn<br /> &lt;/cause&gt;<br /> &lt;/component&gt;<br /> <br /> <br /> Before introduction of Q.850 decoders, cause was an octet string:<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;releaseCall&quot;&gt;<br /> &lt;cause&gt;69 35&lt;/cause&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/Connect 2013-08-26T09:53:00Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:connect}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by gsmSCF to request the gsmSSF to perform the needed actions in order to route a call to a specific destination or in order to influence other call setup information.<br /> <br /> ==Expected actions==<br /> <br /> ==Invoke parameters==<br /> <br /> * '''destinationRoutingAddress''' - the called party number to which the call is to be routed<br /> <br /> * ''alertingPattern'' – the type of allerting to be applied<br /> <br /> * ''originalCalledPartyID'' – the dialled digits if the call was forwarded by the gsmSCF.<br /> <br /> * ''extensions''<br /> <br /> * ''callingPartysCategory'' – type of calling party (e.g., operator, pay phone, subscriber)<br /> <br /> * ''redirectingPartyID'' – the number from where the call was redirected.<br /> <br /> * ''redirectionInformation'' – forwarding related information (e.g., redirecting counter).<br /> <br /> * ''genericNumbers'' – used by the gsmSCF to set the Generic Number parameter used in the network.<br /> <br /> * ''suppressionOfAnnouncement'' - indicates that announcements and tones which are played in the GMSC or the VMSC at non-successful call set-up attempts shall be suppressed.<br /> <br /> * ''oCSIApplicable'' - indicates to the GMSC/gsmSSF that the Originating CAMEL Subscription Information, if present, shall be applied on the outgoing call leg created with the Connect operation.<br /> <br /> * ''na-Info'' – contains the following parameters:<br /> ** ''naCarrierInformation'': carrier identification code and carrier selection type which is to be used by the SSF for routing a call to a carrier.<br /> ** ''naOliInfo'': the originating line information identifying the charged party number type to the carrier.<br /> ** ''naChargeNumber'': the chargeable number for the usage of the carrier.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;connect&quot;&gt;<br /> &lt;destinationRoutingAddress&gt;<br /> &lt;calledPartyNumber nature=&quot;international&quot; plan=&quot;national&quot; inn=&quot;true&quot; restrict=&quot;unavailable&quot; screened=&quot;network-provided&quot;&gt;0123456789&lt;/calledPartyNumber&gt;<br /> &lt;/destinationRoutingAddress&gt;<br /> &lt;alertingPattern&gt;38 19&lt;/alertingPattern&gt;<br /> &lt;callingPartysCategory&gt;ordinary&lt;/callingPartysCategory&gt;<br /> &lt;redirectionInformation reason_original=&quot;diverted&quot; counter=&quot;5&quot; reason=&quot;deflected&quot;&gt;diverted-restrict-all&lt;/redirectionInformation&gt;<br /> &lt;genericNumbers&gt;<br /> &lt;genericNumber nature=&quot;international&quot; plan=&quot;national&quot; inn=&quot;true&quot; restrict=&quot;unavailable&quot; screened=&quot;network-provided&quot;&gt;0123456789&lt;/genericNumber&gt;<br /> &lt;/genericNumbers&gt;<br /> &lt;suppressionOfAnnouncement/&gt;<br /> &lt;oCSIApplicable/&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/ConnectToResource 2013-08-26T09:49:53Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:connectToResource}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is used by gsmSCF to connect a call from the gsmSSF to a specialized resource.<br /> <br /> ==Expected actions==<br /> <br /> * After the successful connection to the gsmSRF, interaction with the caller can take place. The gsmSSF will relay all operations for the gsmSRF and all responses from the gsmSRF.<br /> <br /> * The call is switched to the gsmSRF and a control relationship with the gsmSRF is established.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''resourceAddress''' – identifies the physical location of the gsmSRF. It can be:<br /> ** ipRoutingAddress : the routing address to set up the connection to the gsmSRF.<br /> ** none: the call party is to be connected to a predefined gsmSRF.<br /> * ''extensions'' <br /> * ''serviceInteractionIndicatorsTwo'' - contains an indicator sent from the gsmSCF to the gsmSSF for the control of the connection to the Calling Party. The assisting gsmSSF shall always assume that BothwayThroughConnection is required, so it will always the parameter if it's received.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;connectToResource&quot;&gt;<br /> &lt;resourceAddress&gt;<br /> &lt;ipRoutingAddress nature=&quot;international&quot; plan=&quot;national&quot;inn=&quot;true&quot; restrict=&quot;unavailable&quot; screened=&quot;network-provided&quot;&gt;0123456789&lt;/ipRoutingAddress&gt;<br /> &lt;/resourceAddress&gt;<br /> &lt;serviceInteractionIndicatorsTwo&gt;<br /> &lt;bothwayThroughConnectionInd&gt;<br /> bothwayPathNotRequired<br /> &lt;/bothwayThroughConnectionInd&gt;<br /> &lt;/serviceInteractionIndicatorsTwo&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/DisconnectForwardConnection 2013-08-26T09:22:10Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:disconnectForwardConnection}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is used by gsmSCF to clear a connection:<br /> <br /> * to an gsmSRF: explictly disconnect a connection to a resource (the gsmSRF) established previously by a “connectToResource” operation. It is used as a forward disconnection from the gsmSSF.<br /> <br /> * to an assisting gsmSSF: the operation is sent to the non-assisting gsmSSF to disconnect the temporary connection between the gsmSSF and the assisting gsmSSF and the connection between the assisting gsmSSF and its associated gsmSRF.<br /> <br /> ==Expected actions==<br /> <br /> * The connection to the gsmSRF or assisting SSF is released.<br /> <br /> * The receipt of this operation results in disconnecting the assisting SSF or the PE containing the gsmSRF from the call.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation does not have invoke parameters.<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;disconnectForwardConnection&quot;/&gt;</div>

Monica https://ss7api.null.ro/index.php/EstablishTemporaryConnection 2013-08-26T09:12:24Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:establishTemporaryConnection}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is invoked by gsmSCF and it is used to create a connection between a gsmSSF and an assisting SSF as part of a service assist procedure. It is also used to create a connection between a gsmSSF and a gsmSRF when the gsmSRF resides in a separate addressable physical entity.<br /> <br /> ==Expected actions==<br /> <br /> * When a gsmSSF receives this operation, it should route the call to the assisting gsmSSF/gsmSRF according to the &quot;assistingSSPIPRoutingAddress&quot; parameter.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''assistingSSPIPRoutingAddress''' – indicates the destination address of the gsmSRF/assisting gsmSSF for the assist procedure. It may contain a “correlationID” and “scfID”, but only if these are not specified separately. This parameter should contain routing digits, a “correlationID” and “scfID” when there is no bilateral agreement between PLMNs to transfer the “correlationID” and “scfID” as separate parameters.<br /> <br /> * ''correlationID'' – parameter used by the gsmSCF to associate the dialogue created by the assisting gsmSSF/gsmSRF to the SCF with the “initialDP” from the gsmSSF. Used only if it's not embedded in the “assistingSSIPRoutingAddress” parameter.<br /> <br /> * ''scfID'' – the gsmSCF identifier. Enables the assisting gsmSSF to identify to which gsmSCF the “assistRequestInstructions” should be sent to. Used only if it's not embedded in the “assistingSSIPRoutingAddress” parameter.<br /> <br /> * ''extensions''<br /> <br /> * ''serviceInteractionIndicatorsTwo'' – contains an indicator sent from the gsmSCF to the gsmSSF for the control of the connection to the Calling Party.<br /> <br /> * ''na-Info''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;establishTemporaryConnection&quot;&gt;<br /> &lt;assistingSSPIPRoutingAddress&gt;0723543123&lt;/assistingSSPIPRoutingAddress&gt;<br /> &lt;correlationID&gt;077685977&lt;/correlationID&gt;<br /> &lt;scfID&gt;55 08 23 10&lt;/scfID&gt;<br /> &lt;serviceInteractionIndicatorsTwo&gt;<br /> &lt;bothwayThroughConnectionInd&gt;<br /> bothwayPathNotRequired<br /> &lt;/bothwayThroughConnectionInd&gt;<br /> &lt;/serviceInteractionIndicatorsTwo&gt;<br /> &lt;na-Info&gt;<br /> &lt;naCarrierInformation&gt;<br /> &lt;naCarrierId&gt;1836&lt;/naCarrierId&gt;<br /> &lt;naCICSelectionType&gt;<br /> subscribed-dialing-undeterminded<br /> &lt;/naCICSelectionType&gt;<br /> &lt;/naCarrierInformation&gt;<br /> &lt;naOliInfo&gt;74 04 33&lt;/naOliInfo&gt;<br /> &lt;naChargeNumber nature=&quot;international&quot; plan=&quot;national&quot; inn=&quot;true&quot; restrict=&quot;unavailable&quot; screened=&quot;network-provided&quot;&gt;021456912&lt;/naChargeNumber&gt;<br /> &lt;/na-Info&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/AssistRequestInstructions 2013-08-26T09:09:29Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:assistRequestInstructions}}<br /> ==Capability: Camel== <br /> <br /> ==Usage==<br /> <br /> This operation is sent to the gsmSCF when an assisting gsmSSF or an gsmSRF receives an indication from an initiating gsmSSF requesting an assist procedure.<br /> <br /> ==Expected actions==<br /> <br /> * When receiving an assist indication from a gsmSSF, the assisting gsmSSF/gsmSRF shall first ensure that there are enough resources to invoke the operation and to indicate to the initiating gsmSSF that the call is accepted.<br /> <br /> * After the call is accepted, the operation is sent to the gsmSCF.<br /> <br /> * After sending the operation to the gsmSCF, the assisting gsmSSF/gsmSRF shall wait for instructions from the SCF.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''correlationID''' – associates the dialogue created from the assisting gsmSSF/gsmSCF to the gsmSCF with the “initialDP” operation received from the initiating gsmSSF. The value can be extracted from the digits received from the initiating gsmSSF.<br /> <br /> * '''iPSSPCapabilities''' – indicates which resource are attached, available and supported within the VMSC/GMSC or at the IP where the gsmSRF resides<br /> <br /> * ''extensions''<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;assistRequestInstructions&quot;&gt;<br /> &lt;correlationID&gt;352928133&lt;/correlationID&gt;<br /> &lt;iPSSPCapabilities&gt;27 39 14&lt;/iPSSPCapabilities&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/InitialDP 2013-08-26T09:05:48Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:initialDP}}<br /> ==Capability: Camel==<br /> <br /> ==Usage==<br /> <br /> This operation is sent by the gsmSSF after detection of a request in the BCSM, to request the gsmSCF for instructions to complete a call.<br /> <br /> ==Expected actions==<br /> <br /> * A control relationship is established between the gsmSSF and the gsmSCF. The gsmSSF awaits for instructions from gsmSCF.<br /> <br /> ==Invoke parameters==<br /> <br /> * '''serviceKey''' – identifies the requested IN service within the gsmSCF.<br /> <br /> * ''calledPartyNumber'' – the number that indentifies the called party in the forward direction. Parameter is sent only in the Mobile Terminating/Forwarding cases.<br /> <br /> * ''callingPartyNumber'' – the calling party / origin of the call.<br /> <br /> * ''callingPartysCategory'' – type of calling party.<br /> <br /> * ''iPSSPCapabilities'' – indicates which gsmSRF resources are supported within the VMSC/GMSC the gsmSSF resides in.<br /> <br /> * ''locationNumber'' – the geographical area address for mobility services, used when the “callingPartyNumber” does not contain the geographical location of the calling party.<br /> <br /> * ''originalCalledPartyID'' – the dialed digits if the call was forwarded at some point on the route to the gsmSSF.<br /> <br /> * ''extensions''<br /> <br /> * ''highLayerCompatibility'' – identifies de ISDN-teleservice of a connected terminal.<br /> <br /> * ''additionalCallingPartyNumber'' – number provided by the access signalling system of the calling user.<br /> <br /> * ''bearerCapability'' – the type of connection to the user. Contains the following parameter:<br /> ** bearerCap – value of the ISUP USI parameter.<br /> <br /> The parameter should only be included if ISUP USI parameter is available at gsmSSF. If ISUP USI (User Service Information) and USI Prime are both available at gsmSSF, “the bearerCap” shall contain USI Prime parameter.<br /> <br /> * ''eventTypeBCSM'' – the event which triggerred the InitialDP operation.<br /> <br /> * ''redirectingPartyID'' – the number from which the call was redirected.<br /> <br /> * ''redirectionInformation'' – redirection information, such as redirect counter.<br /> <br /> * ''imsi'' - IMSI of the mobile subscriber for which the CAMEL service is invoked<br /> <br /> * ''subscriberState'' - the state of the mobile subscriber for which the CAMEL service is invoked, possible states are Busy, Idle, Not reachable and Not provided from VLR.<br /> <br /> * ''locationInformation'' – provides the location of the MS and the age of its whereabouts<br /> <br /> * ''ext-basicServiceCode'' - indicates the Basic Service Code<br /> <br /> * ''callReferenceNumber'' - call reference number assigned to the call by the GMSC/MSC<br /> <br /> * ''mscAddress'' - gives the mscId assigned to the GMSC/MSC.<br /> <br /> * ''calledPartyBCDNumber'' – number used to identify the called party. Sent only in MO case.<br /> <br /> * ''timeAndTimezone'' – the time when the gsmSSF was triggered, including the timezone<br /> <br /> * ''gsm-ForwardingPending'' – indicates that a call is to be forwarded due to a forwarded-to-number being received<br /> <br /> * ''initialDPArgExtension'' - contains the following 2 parameters:<br /> ** naCarrierInformation - the carrier identification code and carrier selection type associated with the calling subscriber of a mobile originating call / the called subscriber of a mobile terminating call / the forwarding subscriber of a mobile forwarded call.<br /> ** gmscAddress – gives the mscId assigned to the GMSC<br /> <br /> ==Result parameters==<br /> <br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component remoteCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;initialDP&quot;&gt;<br /> &lt;serviceKey&gt;110&lt;/serviceKey&gt;<br /> &lt;calledPartyNumber nature=&quot;subscriber&quot; plan=&quot;isdn&quot; inn=&quot;true&gt;<br /> 0123456789<br /> &lt;/calledPartyNumber&gt;<br /> &lt;callingPartyNumber nature=&quot;international&quot; plan=&quot;national&quot; inn=&quot;true&quot;<br /> restrict=&quot;unavailable&quot; screened=&quot;network-provided&quot;&gt;<br /> 0123456789<br /> &lt;/callingPartyNumber&gt;<br /> &lt;additionalCallingPartyNumber&gt;7274530741&lt;/additionalCallingPartyNumber&gt;<br /> &lt;bearerCapability coding=&quot;ISO/IEC&quot; transfercap=&quot;3.1khz-audio&quot;<br /> transfermode=&quot;packet&quot; transferrate=&quot;1536kbit&quot; multiplier=&quot;5&quot;&gt;<br /> mulaw<br /> &lt;/bearerCapability&gt;<br /> &lt;eventTypeBCSM&gt;termAttemptAuthorized&lt;/eventTypeBCSM&gt;<br /> &lt;redirectionInformation reason_original=&quot;diverted&quot; counter=&quot;5&quot;<br /> reason=&quot;deflected&quot;&gt;<br /> diverted-restrict-all<br /> &lt;/redirectionInformation&gt;<br /> &lt;subscriberState&gt;<br /> &lt;netDetNotReachable&gt;restrictedArea&lt;/netDetNotReachable&gt;<br /> &lt;/subscriberState&gt;<br /> &lt;locationInformation&gt;<br /> &lt;ageOfLocationInformation&gt;15&lt;/ageOfLocationInformation&gt;<br /> &lt;geographicalInformation&gt;18 16 54 10&lt;/geographicalInformation&gt;<br /> &lt;vlr-Number nature=&quot;international&quot; plan=&quot;isdn&quot;&gt;69029932957&lt;/vlr-Number&gt;<br /> &lt;locationNumber&gt;53 57 09 23&lt;/locationNumber&gt;<br /> &lt;cellIdOrLAI&gt;<br /> &lt;cellIdFixedLength&gt;00812628&lt;/cellIdFixedLength&gt;<br /> &lt;/cellIdOrLAI&gt;<br /> &lt;/locationInformation&gt;<br /> &lt;ext-basicServiceCode&gt;<br /> &lt;bearerService&gt;general-dataCDS&lt;/bearerService&gt;<br /> &lt;/ext-basicServiceCode&gt;<br /> &lt;callReferenceNumber&gt;26 92 38 35&lt;/callReferenceNumber&gt;<br /> &lt;mscAddress enc=&quot;e164&quot; nature=&quot;international&quot; plan=&quot;isdn&quot;&gt;<br /> 82802477725<br /> &lt;/mscAddress&gt;<br /> &lt;calledPartyBCDNumber enc=&quot;e164&quot; nature=&quot;international&quot; plan=&quot;isdn&quot;&gt;<br /> 82722803066<br /> &lt;/calledPartyBCDNumber&gt;<br /> &lt;timeAndTimezone&gt;9828157516&lt;/timeAndTimezone&gt;<br /> &lt;gsm-ForwardingPending/&gt;<br /> &lt;initialDPArgExtension&gt;<br /> &lt;naCarrierInformation&gt;<br /> &lt;naCarrierId&gt;7060&lt;/naCarrierId&gt;<br /> &lt;naCICSelectionType&gt;<br /> subscribed-dialing-undeterminded<br /> &lt;/naCICSelectionType&gt;<br /> &lt;/naCarrierInformation&gt;<br /> &lt;gmscAddress enc=&quot;e164&quot; nature=&quot;international&quot; plan=&quot;isdn&quot;&gt;<br /> 54737210042<br /> &lt;/gmscAddress&gt;<br /> &lt;/initialDPArgExtension&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/CAMEL_operations 2013-08-26T09:00:17Z

<p>Monica: </p> <hr /> <div>List of supported CAMEL operations:<br /> <br /> * [[initialDP]]<br /> * [[assistRequestInstructions]]<br /> * [[establishTemporaryConnection]]<br /> * [[disconnectForwardConnection]]<br /> * [[connectToResource]]<br /> * [[connect]]<br /> * [[releaseCall]]<br /> * [[requestReportBCSMEvent]]<br /> * [[eventReportBCSM]]<br /> * [[continue]]<br /> * [[resetTimer]]<br /> * [[furnishChargingInformation]]<br /> * [[applyCharging]]<br /> * [[applyChargingReport]]<br /> * [[callInformationReport]]<br /> * [[callInformationRequest]]<br /> * [[sendChargingInformation]]<br /> * [[playAnnouncement]]<br /> * [[promptAndCollectUserInformation]]<br /> * [[specializedResourceReport]]<br /> * [[cancel]]<br /> * [[activityTest]]</div>

Monica https://ss7api.null.ro/index.php/ReportSM-deliveryStatus 2013-08-26T08:52:06Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:reportSM-deliveryStatus}}<br /> ==Usage==<br /> <br /> This operation is used between the gateway MSC and the HLR. It sets the Message Waiting Data into the HLR or informs the HLR of a successful SM transfer after polling. This service is invoked by the gateway MSC.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation has the following invoke parameters:<br /> *'''msisdn''' - ISDN number assigned to the mobile subscriber.<br /> *'''serviceCentreAddress''' - the address of the SMSC.<br /> *'''sm-DeliveryOutcome''' - indicates the cause for setting the Message Waiting Data in the mobile terminated SM delivery. It can have one of the following values: memoryCapacityExceeded, absentSubscriber, successfulTransfer.<br /> *''absentSubscriberDiagnosticSM'' - indicates the reason why the subscriber is absent.<br /> *''extensionContainer''<br /> *''gprsSupportIndicator'' - indicates that the MSC supports GPRS specific procedure of combine delivery SM via MSC and/or via the SGSN.<br /> *''deliveryOutcomeIndicator'' - indicates that the delivery outcome sent to the HLR is for GPRS.<br /> *''additionalSM-DeliveryOutcome'' - this parameter is used to indicate the GPRS delivery outcome in case a combination between delivery outcome for GPRS and non-GPRS are sent to the HLR<br /> *''additionalAbsentSubscriberDiagnosticSM'' - indicates the reason why the subscriber is absent.<br /> *''ip-sm-gw-Indicator'' - indicates by its presence that sm-deliveryOutcome is for delivery via IMS.<br /> *''ip-sm-gw-sm-deliveryOutcome'' - is used to indicate the delivery outcome for the IMS domain. It can have one of the values liste for ''sm-DeliveryOutcome''.<br /> *''ip-sm-gw-absentSubscriberDiagnosticSM'' - indicates the reason why the subscriber is absent.<br /> <br /> ==Result parameters==<br /> This operation does expect a result. It can have one of the following parameters:<br /> *''storedMSISDN'' - - the stored MSISDN in the Message Waiting Data file.<br /> *''extensionContainer''<br /> <br /> ==Possible errors==<br /> <br /> * dataMissing<br /> * unexpectedDataValue<br /> * unknownSubscriber<br /> * messageWaitingListFull<br /> <br /> ==Example==<br /> <br /> &lt;component remoteCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;reportSM-DeliveryStatus&quot;&gt;<br /> &lt;msisdn nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;19786148973&lt;/msisdn&gt;<br /> &lt;serviceCentreAddress nature=&quot;international&quot; plan=&quot;land-mobile&quot; enc=&quot;e212&quot;&gt;89379726071&lt;/serviceCentreAddress&gt;<br /> &lt;sm-DeliveryOutcome&gt;successfulTransfer&lt;/sm-DeliveryOutcome&gt;<br /> &lt;absentSubscriberDiagnosticSM&gt;2&lt;/absentSubscriberDiagnosticSM&gt;<br /> &lt;gprsSupportIndicator/&gt;<br /> &lt;deliveryOutcomeIndicator/&gt;<br /> &lt;additionalSM-DeliveryOutcome&gt;absentSubscriber&lt;/additionalSM-DeliveryOutcome&gt;<br /> &lt;additionalAbsentSubscriberDiagnosticSM&gt;5&lt;/additionalAbsentSubscriberDiagnosticSM&gt;<br /> &lt;ip-sm-gw-Indicator/&gt;<br /> &lt;ip-sm-gw-sm-deliveryOutcome&gt;memoryCapacityExceeded&lt;/ip-sm-gw-sm-deliveryOutcome&gt;<br /> &lt;ip-sm-gw-absentSubscriberDiagnosticSM&gt;6&lt;/ip-sm-gw-absentSubscriberDiagnosticSM&gt;<br /> &lt;/component&gt; <br /> ...<br /> &lt;component localCID=&quot;1&quot; type=&quot;ResultLast&quot; operationCode=&quot;reportSM-DeliveryStatus&quot;&gt;<br /> &lt;storedMSISDN nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;19786148973&lt;/storedMSISDN&gt;<br /> &lt;/component&gt; <br /> <br /> ==References==<br /> * ETSI TS 129 002 V10.6.0 (2012-04) p.342</div>

Monica https://ss7api.null.ro/index.php/Mo-forwardSM 2013-08-26T08:49:41Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:mo-forwardSM}}<br /> ==Usage==<br /> <br /> This is operation is used to forward mobile originated short messages between the a serving MSC/SGSN and its outbound MSC.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation has the following parameters:<br /> *'''sm-RP-DA''' – represents the destination address used by the SMS relay sub-layer protocol. In the mobile originated SM transfer, this parameter contains the service centre address received from the mobile station. It can be one the following:<br /> **imsi - identity of the SIM.<br /> **lmsi - local identity allocated by the VLR to a given subscriber for internal management of data in the VLR<br /> **serviceCentreAddressDA – destination address of the SMSC.<br /> **noSM-RP-DA22<br /> *'''sm-RP-OA''' – represents the originating address used by the SMS relay sub-layer protocol. It can be one the following:<br /> **msisdn - number associated with the SIM.<br /> **serviceCentreAddressOA – originating address of the SMSC.<br /> **noSM-RP-OA<br /> *'''sm-RP-UI''' - this parameter represents the user data field carried by the SMS relay sub-layer protocol.<br /> *''moreMessagesToSend'' - indicates whether the MSC has more short messages to send.<br /> *''extensionContainer''<br /> *''imsi'' - the originating subscriber's SIM identification number<br /> <br /> ==Result parameters==<br /> <br /> *''sm-RP-UI'' – this parameter represents the user data field carried by the SMS relay sub-layer protocol.<br /> *''extensionContainer''<br /> <br /> ==Example==<br /> &lt;component remoteCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;mo-forwardSM&quot;&gt;<br /> &lt;sm-RP-DA&gt;<br /> &lt;serviceCentreAddressDA nature=&quot;international&quot; plan=&quot;isdn&quot; enc=&quot;e164&quot;&gt;4915555229999&lt;/serviceCentreAddressDA&gt;<br /> &lt;/sm-RP-DA&gt;<br /> &lt;sm-RP-OA&gt;<br /> &lt;msisdn nature=&quot;international&quot; plan=&quot;isdn&quot; enc=&quot;e164&quot;&gt;4915555223391&lt;/msisdn&gt;<br /> &lt;/sm-RP-OA&gt;<br /> &lt;sm-RP-UI enc=&quot;hex&quot;&gt;21 78 0c 81 10 55 55 22 33 09 00 00 06 c8 32 9b fd 0e 01&lt;/sm-RP-UI&gt;<br /> &lt;imsi enc=&quot;str&quot;&gt;901700000003001&lt;/imsi&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/Mt-forwardSM 2013-08-26T08:45:19Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:mt-forwardSM}}<br /> ==Usage==<br /> <br /> This operation is used between the gateway MSC and the serving MSC/SGSN to forward mobile terminated short messages.<br /> <br /> ==Invoke parameters==<br /> <br /> * sm-RP-DA – represents the destination address used by the SMS relay sub-layer protocol. It can be one the following:<br /> ** imsi - identity of the SIM.<br /> ** lmsi - local identity allocated by the VLR to a given subscriber for internal management of data in the VLR<br /> ** serviceCentreAddressDA – destination address of the SMSC.<br /> ** noSM-RP-DA <br /> <br /> * sm-RP-OA – represents the originating address used by the SMS relay sub-layer protocol. It can be one the following:<br /> ** msisdn - number associated with the SIM.<br /> ** serviceCentreAddressOA – originating address of the SMSC.<br /> ** noSM-RP-OA <br /> <br /> * sm-RP-UI - this parameter represents the user data field carried by the SMS relay sub-layer protocol.<br /> * extensionContainer<br /> <br /> ==Result parameters==<br /> * sm-RP-UI – this parameter represents the user data field carried by the SMS relay sub-layer protocol.<br /> * extensionContainer<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;mt-forwardSM&quot; timeout=&quot;15&quot;&gt;<br /> &lt;sm-RP-DA&gt;<br /> &lt;imsi&gt;901700000003000&lt;/imsi&gt;<br /> &lt;/sm-RP-DA&gt;<br /> &lt;sm-RP-OA&gt;<br /> &lt;serviceCentreAddressOA plan=&quot;isdn&quot; nature=&quot;international&quot;&gt;<br /> 4915555229999<br /> &lt;/serviceCentreAddressOA&gt;<br /> &lt;/sm-RP-OA&gt;<br /> &lt;sm-RP-UI&gt;20 0d 91 94 51 55 25 32 93 f1 00 00 21 40 42 61 22 44 40 06 c8 32 9b fd 0e 01&lt;/sm-RP-UI&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/InformServiceCenter 2013-08-26T08:40:31Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:informServiceCenter}}<br /> ==Usage==<br /> <br /> This operation is used by the HLR to inform the gateway MSC which MSISDN number is stored in the Message Waiting Data file (has a SM waiting).<br /> <br /> ==Invoke parameters==<br /> <br /> This operation has the following invoke parameters:<br /> *''storedMSISDN'' - the stored MSISDN in the Message Waiting Data file.<br /> *''mw-Status'' - it is a set of the following flags:<br /> **sc-AddressNotIncluded - indicates if the address of the originator service centre is included in the Message Waiting Data file.<br /> **mnrf-Set - Mobile subscriber Not Reachable flag. <br /> **mcef-Set - Memory Capacity Exceeded flag.<br /> **mnrg-Set - Mobile station Not Reachable for GPRS flag.<br /> *''extensionContainer''<br /> *''absentSubscriberDiagnosticSM'' - indicates the reason why the subscriber is absent.<br /> *''additionalAbsentSubscriberDiagnosticSM'' - indicates the reason of the additional SM delivery outcome.<br /> <br /> ==Result parameters==<br /> This operation does not expect a result.<br /> <br /> ==Example==<br /> <br /> &lt;component remoteCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;informServiceCentre&quot;&gt;<br /> &lt;msisdn&gt;448499559676&lt;/msisdn&gt;<br /> &lt;mw-status&gt;mnrf-Set&lt;/mw-status&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/AlertServiceCenter 2013-08-26T08:39:02Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:alertServiceCenter}}<br /> ==Usage==<br /> <br /> This operation is used by the HLR to indicate to the MSC that it detected that a subscriber who has a message waiting is active or that it has memory available.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation has the following parameters:<br /> *'''msisdn''' - indicates the MSISDN who is active or has available memory.<br /> *'''serviceCentreAddress''' - the address of the SMSC.<br /> <br /> ==Result parameters==<br /> <br /> This operation has no result parameters.<br /> <br /> ==Example==<br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;alertServiceCentre&quot;&gt;<br /> &lt;msisdn enc=&quot;e212&quot; nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;55477627900&lt;/msisdn&gt;<br /> &lt;serviceCentreAddress enc=&quot;e212&quot; nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;44015781099&lt;/serviceCentreAddress&gt;<br /> &lt;/component&gt;<br /> <br /> ==Reference==<br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1086</div>

Monica https://ss7api.null.ro/index.php/ReadyForSM 2013-08-26T08:37:52Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:readyForSM}}<br /> ==Usage==<br /> This operation is used:<br /> * between a MSC and VLR or between a VLR and a HLR to indicate that a subscriber had a memory available situation. The VLR initiates this operation if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the MSC.<br /> * between the SGSN and the HLR to indicate that a subscriber has a memory available situation.<br /> <br /> ==Invoke parameters==<br /> This operation has the following Invoke parameters<br /> *'''imsi''' - identity of the SIM that has a memory available situation.<br /> *'''alertReason''' - used to indicate the reason why the service centre is alerted. It can have one of the following values:<br /> **ms-Present - indicates that the mobile subscriber is present.<br /> **memoryAvailable - indicates that the mobile subscriber has memory available.<br /> *''alertReasonIndicator'' - indicates that the alert reason is sent to the HLR due to GPRS activity.<br /> *''extensionContainer''<br /> *''additionalAlertReasonIndicator'' - indicates that the alert reason is sent to the HLR due to IMS activity.<br /> <br /> ==Result parameters==<br /> This operation expects a result containing the following parameters:<br /> *''extensionContainer''<br /> <br /> ==Example==<br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;readyForSM&quot;&gt;<br /> &lt;imsi&gt;542552552853&lt;/imsi&gt;<br /> &lt;alertReason&gt;memoryAvailable&lt;/alertReason&gt;<br /> &lt;alertReasonIndicator/&gt;<br /> &lt;/component&gt;<br /> <br /> ==Reference==<br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1086</div>

Monica https://ss7api.null.ro/index.php/SendRoutingInfoForSM 2013-08-26T08:34:39Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:sendRoutingInfoForSM}}<br /> ==Usage==<br /> <br /> This operation is used by a gateway MSC to retrieve from the HLR the routing information needed for routing a short message to the servicing MSC or SGSN.<br /> <br /> ==Invoke parameters==<br /> <br /> *'''msisdn''' - the number assigned to a mobile subscriber.<br /> *'''sm-RP-PRI''' - indicates whether the delivery of the short message shall be attempted.<br /> *'''serviceCentreAddress''' - the address of the SMSC<br /> *''extensionContainer''<br /> *''gprsSupportIndicator'' - the presence of this parameter indicates that the SMS-GMSC supports the GPRS specific procedure of combine delivery of the short message via MSC and/or via SGSN.<br /> *''sm-RP-MTI'' - represents the RP-MessageType of the short message. Distinguishes between a SM sent to a mobile station in order to acknowledge a mobile originated SM initiated by the mobile from a normal mobile terminated SM.<br /> *''sm-RP-SMEA'' - represents the RP-Originating address of the SM entity that originated the short message.<br /> *''sm-deliveryNotIntended'' - the presence of this parameter indicates that the delivery of a short message is not intended.<br /> <br /> ==Result parameters==<br /> <br /> *'''imsi''' - identity of the SIM.<br /> *'''locationInfoWithLMSI''' - contains the following parameters<br /> **'''networkNode-Number''' - contains either the ISDN number of the SGSN or of the MSC.<br /> **''lmsi'' - local mobile station identity (VLR specific)<br /> **''extensionContainer''<br /> **''gprsNodeIndicator'' - indicates that the Network Node Number sent by the HLR is the SGSN number. The presence of this parametr is mandatory if the Network Node Number is in fact the SGSN number.<br /> **''additional-Number'' - either the SGSN or MSC number.<br /> *''extensionContainer''<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;sendRoutingInfoForSM&quot;&gt;<br /> &lt;msisdn enc=&quot;e212&quot; nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;75368395527&lt;/msisdn&gt;<br /> &lt;sm-RP-PRI&gt;true&lt;/sm-RP-PRI&gt;<br /> &lt;serviceCentreAddress enc=&quot;e212&quot; nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;50730011326&lt;/serviceCentreAddress&gt;<br /> &lt;gprsSupportIndicator/&gt;<br /> &lt;sm-RP-MTI&gt;20&lt;/sm-RP-MTI&gt;<br /> &lt;sm-RP-SMEA&gt;34 72 91 61 13&lt;/sm-RP-SMEA&gt;<br /> &lt;/component&gt;</div>

Monica https://ss7api.null.ro/index.php/SM_Format 2013-08-26T08:27:24Z

<p>Monica: Created page with &quot;This page documents the body of the Short Messages (SMS TPDU). This format is not MAP (ASN.1) but a binary block of octets. The decoding of the message body depends on the di...&quot;</p> <hr /> <div>This page documents the body of the Short Messages (SMS TPDU). This format is not MAP (ASN.1) but a binary block of octets.<br /> <br /> The decoding of the message body depends on the direction (MO to MT or MT to MO). At any point it is important to know which direction is the message.<br /> <br /> == Mobile Originated==<br /> <br /> !!!!!!<br /> <br /> == Mobile Terminated==<br /> <br /> !!!!!!<br /> <br /> ==References==<br /> * ETSI TS 123 040 Technical realization of the Short Message Service<br /> * [http://www.dreamfabric.com/sms/submit_fo.html SMS-SUBMIT PDU]<br /> * [http://www.dreamfabric.com/sms/deliver_fo.html SMS-DELIVER PDU]</div>

Monica https://ss7api.null.ro/index.php/SMS_functions 2013-08-26T08:24:24Z

<p>Monica: /* References */</p> <hr /> <div>The purpose of the Short Message functions is to deliver short messages from one Mobile Station to another. The routing, storage, reporting, error handling and retransmission are all handled by the implementation.<br /> <br /> There are two major types of SMS operations:<br /> * Mobile originated (MO)<br /> ** From the Mobile Station to its own outbound SMSC<br /> * Mobile terminated (MT)<br /> ** From SMSC to Mobile Station (through MSC or SGSN)<br /> ** Between SMSCs<br /> <br /> For MAP versions 1 and 2 there is a single operation for forwarding the SMS: forwardSM. In this case the existence of the IMSI in the Destination Address indicates the message is MT.<br /> <br /> For MAP version 3 separate operations [[mo-forwardSM]] and [[mt-forwardSM]] are defined. The format of the MAP messages reflect the possible ways of addressing the Origination and the Destination addresses.<br /> <br /> The [[SM Format|format]] of the SMS body and the meaning of the bits depends of the direction of the message. It is important to know this direction to be able to decode the SMS.<br /> <br /> The sequence of operations for sending a short message is:<br /> <br /> == Mobile Originated SMS==<br /> Path: <br /> MS &gt;--&gt; (VLR or SGSN) &gt;-(mo-forwardSM)-&gt; SMSC<br /> <br /> The mobile station sends the short message to its assigned SMSC. The SMSC should check that the subscriber is authorized to send short messages.<br /> <br /> The SMSC address (number) can be:<br /> * Configured in the Mobile Station<br /> ** Manually<br /> ** From SIM<br /> ** From VLR subscriber data<br /> * Replied using same SMSC as the received message<br /> <br /> == Routing to the destination network==<br /> Path: <br /> SMSC &gt;-(sendRoutingInfoForSM)-&gt; HLR<br /> <br /> The [[sendRoutingInfoForSM]] operation is sent from SMSC to the HLR of the destination number (after resolving number portability). The HLR returns the MSC and possibly SGSN through which the message can be delivered.<br /> <br /> It is possible that a HLR returns the address of an Incoming Gateway MSC. This allows the destination network more control over how the messages are handled.<br /> <br /> == Delivery to destination==<br /> <br /> Path: <br /> SMSC &gt;-(mt-forwardSM)-&gt; (MSC or SGSN or IGWMSC)<br /> (MSC or SGSN) &gt;--&gt; MS<br /> IGWMSC &gt;--&gt; (MSC or SGSN) &gt;--&gt; MS<br /> <br /> The message is delivered to the Switching Center that will forward to the Mobile Station.<br /> <br /> A Delivery Report is normally returned by the MS. This is converted to a Submit Report that is sent back to the Originating MS.<br /> <br /> An error may be returned if the destination subscriber is unknown, offline or the MS cannot save the short message. This is converted to an error Status Report that is sent back to the Originating MS.<br /> <br /> If the Originating MS requested it in the initial short message a Status Report is generated when an IGWMSC accepts the message. This indicates that the message is progressing but has not been delivered yet.<br /> <br /> == Error handling, retries, expiration==<br /> Any SMSC will store a message that cannot be delivered immediately and will retry later. The retries are based on a repeat interval but may be triggered by a notification that the mobile station is available to receive messages.<br /> <br /> The messages are not stored indefinitely. A validity interval is set in the initial message and the SMSCs will use it as a maximum time (subject to its own policy) to preserve the message. If a message expires it is discarded and a Status Report is sent back to the Originating MS.<br /> <br /> Finally, Status Reports are never generated in response to other reports. This prevents infinite error loops.<br /> <br /> ==List of supported operations==<br /> <br /> *[[sendRoutingInfoForSM]]<br /> *[[readyForSM]]<br /> *[[alertServiceCenter]]<br /> *[[informServiceCenter]]<br /> *[[mt-forwardSM]]<br /> *[[mo-forwardSM]]<br /> *[[reportSM-deliveryStatus]]<br /> <br /> ==References==<br /> * [http://en.wikipedia.org/wiki/Short_message_service_technical_realisation_%28GSM%29 SMS Technical Realisation on Wikipedia]</div>

Monica https://ss7api.null.ro/index.php/SetReportingState 2013-08-26T08:17:09Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:setReportingState}}<br /> ==Usage==<br /> <br /> This operation is used by the HLR to set in the VLR the reporting state for a requested service.<br /> <br /> ==Invoke parameters==<br /> *''imsi'' - the identity of the SIM.<br /> *''lmsi'' - local mobile station identity (VLR specific).<br /> *''ccbs-Monitoring'' - indicates whether the monitoring for CCBS shall be started or stopped. It has one of the following values:<br /> **stopMonitoring<br /> **startMonitoring<br /> *''extensionContainer''<br /> <br /> !Result parameters<br /> *''ccbs-SubscriberStatus'' - the CCBS subscriber status. It has one of the following values:<br /> **ccbsNotIdle<br /> **ccbsIdle<br /> **ccbsNotReachable<br /> *''extensionContainer''<br /> <br /> ==Example==<br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;setReportingState&quot;&gt;<br /> &lt;imsi&gt;157320925330&lt;/imsi&gt;<br /> &lt;ccbs-Monitoring&gt;startMonitoring&lt;/ccbs-Monitoring&gt;<br /> &lt;/component&gt;<br /> <br /> ==References==<br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1073</div>

Monica https://ss7api.null.ro/index.php/SendIMSI 2013-08-26T08:15:22Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:sendIMSI}}<br /> ==Usage==<br /> <br /> This message is sent from a VLR to a HLR to confirm the identity of a subscriber by its MSISDN.<br /> <br /> ==Expected actions==<br /> <br /> * If the MSISDN is known the HLR must respond with the IMSI of the SIM.<br /> <br /> * If the MSISDN is not known or in the wrong format an appropriate error must be returned.<br /> <br /> * If there are multiple IMSI associated with the MSISDN (for example GSM / UMTS) the most current active should be returned<br /> <br /> ==Invoke parameters==<br /> <br /> * '''msisdn''' – Subscriber's directory number<br /> <br /> ==Result parameters==<br /> <br /> * ''imsi'' – Subscriber's SIM identification number<br /> <br /> ==Example==<br /> &lt;component remoteCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;sendIMSI&quot;&gt;<br /> &lt;msisdn enc=&quot;e164&quot;&gt;49173123456&lt;/msisdn&gt;<br /> &lt;/component&gt;<br /> ...<br /> &lt;component remoteCID=1&quot; type=&quot;ResultLast&quot;&gt;<br /> &lt;imsi enc=&quot;e212&quot;&gt;497012345678900&lt;/imsi&gt;<br /> &lt;/component&gt;<br /> <br /> <br /> ==References==<br /> <br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1061</div>

Monica https://ss7api.null.ro/index.php/FailureReport 2013-08-26T08:13:52Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:failureReport}}<br /> ==Usage==<br /> <br /> This message is used to report GPRS failures to the HLR.<br /> This message is used by the GGSN to inform the HLR that network requested PDP-context activation has failed.<br /> <br /> ==Invoke parameters==<br /> <br /> This operation has the following invoke parameters:<br /> *'''imsi''' - the identity of the SIM.<br /> *'''ggsn-Number''' - refers to the ISDN number of a GGSN.<br /> *''ggsn-Address'' - IP address of a GGSN.<br /> *''extensionContainer''<br /> <br /> ==Result parameters==<br /> <br /> This operation has the following result parameters:<br /> *''ggsn-Address'' - IP address of a GGSN.<br /> *''extensionContainer''<br /> <br /> ==Example==<br /> &lt;component localCID=&quot;1&quot; type=&quot;Invoke&quot; operationCode=&quot;failureReport&quot;&gt;<br /> &lt;imsi&gt;846849459906&lt;/imsi&gt;<br /> &lt;ggsn-Number enc=&quot;e212&quot; nature=&quot;international&quot; plan=&quot;land-mobile&quot;&gt;98849529029&lt;/ggsn-Number&gt;<br /> &lt;ggsn-Address&gt;68 54 04 82 22&lt;/ggsn-Address&gt;<br /> &lt;/component&gt;<br /> <br /> ==References==<br /> <br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1092</div>

Monica https://ss7api.null.ro/index.php/ForwardCheckSS-Indication 2013-08-26T08:12:18Z

<p>Monica: </p> <hr /> <div>{{DISPLAYTITLE:forwardCheckSS-Indication}}<br /> ==Usage==<br /> <br /> This is an optional message sent to all mobile stations after a HLR outage so they initiate a synchronization of their standard supplementary services states with the VLR.<br /> <br /> This message must be sent only after reset was sent to all known VLRs and they had a chance to have subscriber data restored.<br /> <br /> ==Addressing==<br /> <br /> The TCAP dialog '''userInformation''' is used for identifying the subscriber. The '''destinationReference''' parameter will normally hold the IMSI as a land-mobile international number.<br /> <br /> ==Invoke parameters==<br /> <br /> No parameters can be specified.<br /> <br /> ==Example==<br /> <br /> &lt;component localCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;forwardCheckSS-Indication&quot;/&gt;<br /> <br /> ==References==<br /> <br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1059</div>

Monica https://ss7api.null.ro/index.php/Reset 2013-08-26T08:11:01Z

<p>Paulc: Fixed structure for various MAP versions, commercial Yate Rev. 2507</p> <hr /> <div>{{DISPLAYTITLE:reset}}<br /> ==Usage==<br /> <br /> This message is sent by a HLR that (re)starts after an outage to all VLRs or SGSNs to which subscribers were registered according to the data before the outage.<br /> <br /> <br /> ==Invoke parameters==<br /> <br /> === MAP v1 ===<br /> * '''networkResource''' - type of node generating the message, normally '''hlr'''<br /> * '''networkNode-Number''' - node identification number<br /> * ''hlr-List'' - optional list of '''HLR-Id''', each containing an IMSI prefix to which the reset applies<br /> <br /> === MAP v2 ===<br /> * '''hlr-Number''' – HLR identification number<br /> * ''hlr-List'' - optional list of '''HLR-Id''', each containing an IMSI prefix to which the reset applies<br /> <br /> === MAP v3 ===<br /> * '''sendingNodeNumber''' - choice of one of:<br /> ** '''hlr-Number''' – HLR identification number<br /> ** '''css-Number''' – CSS identification number<br /> * ''hlr-List'' - optional list of '''HLR-Id''', each containing an IMSI prefix to which the reset applies<br /> * &lt;strike&gt;''reset-Id-List''&lt;/strike&gt; – Not supported<br /> * &lt;strike&gt;''subscriptionData''&lt;/strike&gt; – Not supported<br /> * &lt;strike&gt;''subscriptionDataDeletion''&lt;/strike&gt; – Not supported<br /> <br /> <br /> ==Result==<br /> This operation is of class '''reportNone''' so no result or error is expected from the MAP layer.<br /> <br /> It is possible to receive an error from the TCAP layer (dialog or component problem).<br /> <br /> <br /> ==Examples==<br /> &lt;component localCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;reset&quot;&gt;<br /> &lt;networkResource&gt;hlr&lt;/networkResource&gt;<br /> &lt;networkNode-Number&gt;4970100&lt;/networkNode-Number&gt;<br /> &lt;/component&gt;<br /> <br /> <br /> &lt;component localCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;reset&quot;&gt;<br /> &lt;hlr-Number&gt;4970100&lt;/hlr-Number&gt;<br /> &lt;/component&gt;<br /> <br /> <br /> &lt;component localCID=1&quot; type=&quot;Invoke&quot; operationCode=&quot;reset&quot;&gt;<br /> &lt;sendingNodeNumber&gt;<br /> &lt;hlr-Number&gt;4970100&lt;/hlr-Number&gt;<br /> &lt;/sendingNodeNumber&gt;<br /> &lt;hlr-List&gt;<br /> &lt;HLR-Id&gt;00101&lt;/HLR-Id&gt;<br /> &lt;HLR-Id&gt;00102&lt;/HLR-Id&gt;<br /> &lt;/hlr-List&gt;<br /> &lt;/component&gt;<br /> <br /> <br /> ==Reference==<br /> * ETSI TS 100 974 V7.15.0 (2004-03) p1059</div>

Monica