Difference between revisions of "ProvideRoamingNumber"

From ss7api.null.ro
Jump to: navigation, search
(Created page with "==Capability: Call handling== ==Usage== This message is sent by the HLR to the current VLR for each mobile terminated call to get a temporary roaming number to which the cal...")
 
 
Line 1: Line 1:
 +
{{DISPLAYTITLE:provideRoamingNumber}}
 
==Capability: Call handling==
 
==Capability: Call handling==
  

Latest revision as of 17:03, 27 August 2013

Contents

[edit] Capability: Call handling

[edit] Usage

This message is sent by the HLR to the current VLR for each mobile terminated call to get a temporary roaming number to which the call is sent over ISUP.

[edit] Notes

This message would normally be sent from the GMSC to the HLR using the MAP-C protocol using the sendRoutingInformation operation. Since MAP-C is not required the routing entity will use XML to invoke provideRoamingNumber and wait for the answer.

[edit] Expected actions

  • The routing entity needs to get a roaming number for each mobile terminated call
  • The returned number(s) must be used to route the call to the terminating network

[edit] Invoke parameters

  • imsi – IMSI of the SIM card
  • msc-Number – MSC identification string / number
  • msisdn – Number associated with the SIM
  • lmsi – Local mobile station identity (VLR specific)
  • gsm-BearerCapability – Desired bearer capabilities
    • protocolId – Desired protocol, one of "gsm-0408", " gsm-0806", "gsm-BSSMAP" or "ets-300102-1"
    • signalInfo – Signal information PDUs, already encoded
  • networkSignalInfo – Desired network signaling capabilities
    • protocolId – Desired protocol, one of "gsm-0408", " gsm-0806", "gsm-BSSMAP" or "ets-300102-1"
    • signalInfo – Signal information PDUs, already encoded
  • suppressionOfAnnouncement – If present indicates that call failure tones or messages should not be generated (MAP v3)
  • gmsc-Address – Address(es) of the GMSC handling the call (MAP v3)
  • supportedCamelPhasesInGMSC – Supported CAMEL phases, can be "phase1" and/or "phase2" (MAP v3)

[edit] Result parameters

  • roamingNumber – Number to which the call should be routed
  • extensionContainer – Container for various extensions (MAP v3)

[edit] Example

<component localCID="1" type="Invoke" operationCode="provideRoamingNumber">
	<imsi>497012345678900</imsi>
	<msc-Number enc="e212">49700500000</msc-Number>
	<msisdn enc="e164">49173123456</msisdn>
	<lmsi>94 73 43</lmsi>
	<gsm-BearerCapability>
		<protocolId>gsm-0408</protocolId>
		<signalInfo>20 36 35</signalInfo>
	</gsm-BearerCapability>
	<suppressionOfAnnouncement/>
	<gmsc-Address enc="e212">49700500001</gmsc-Address>
</component>
...
<component localCID="1" type="Result>
	<roamingNumber enc="e164">49345678901<roamingNumber>
	<roamingNumber enc="e164">49345000221<roamingNumber>
</component>

[edit] References

  • ETSI TS 100 974 V7.15.0 (2004-03) p1067
Personal tools
Namespaces

Variants
Actions
MAP & CAMEL XML Interface
Diameter XML Interface
MAP and CAMEL operations
Diameter interfaces
Examples
Resources
Navigation
Toolbox