You are on page 1of 34

Ia Interface and MEGACO / H.

248 Protocol

Ia Interface and MEGACO / H.248


Ia Interface and MEGACO & H248 protocol
Basic terms
MEGACO / H.248 Protocol
Termination Properties and Descriptors
Service Change Reasons
Error descriptor

© 2011 Nokia Siemens Networks



Ia Interface and MEGACO / H.248 Protocol


© 2011 Nokia Siemens Networks

Ia Interface and MEGACO / H.248 Protocol


Ia Interface and MEGACO & H248 protocol

© 2011 Nokia Siemens Networks


On this interface protocol H248 / MEGACO is used.Ia Interface and MEGACO / H. A Border Gateway Function (BGF) provides the interface between two IP-transport domains. The SPDF makes policy decisions using policy rules and forwards the session and media related information obtained from AF (Application Function) to the BGF (Border Gateway Function). It may reside at the boundary between an access network and a core network or between two core networks. standardized by ETSI ES 283 018.248 Protocol 1.248 MGC" role.1 Basic terms Ia interface is reference point between AF and BGF. The BGF has the "H.248 MG" role. SPDF The Service Policy Decision Function (SPDF) is a functional element that coordinates the resource reservation request received from AF (e. The BGF has the "H. ETSI specifies the H.248 Ia profile. The BGF performs policy enforcement functions under the control of the SPDF. 4 FN42425EN60GLA1 © 2011 Nokia Siemens Networks . BGF BGF is packet-to-packet gateway for user plane media traffic. P-CSCF).g.

248 Protocol Reference architecture AF Gq„+ Diameter PCS (SPDF) Ia H248 Core Transport Network Access Transport Network BGF Fig.Ia Interface and MEGACO / H. 1 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 5 .

248 the set of messages is defined Events describe what is detectable and reportable. but are also dependent on the system. Stream: Bidirectional media or control flow received/sent by a media gateway as part of a call or conference.248 (ITU terminology) is a protocol between Media Gateway Controller (MGC) and Media Gateways (MG) that is identically standardized by ITU and IETF (H. For example.Media Gateway Control (IETF terminology) or H. RFC 3015).248 Protocol 1. signals and events.248 from 06/2000 vs. RTP streams in an IP network).248 Protocol MEGACO . DS0s) and media streams from a packet network (e.. The basic communication units exchanged between functional units defined in the framework is a message. busy tone). interfaces and abstract models. 6 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .g. Call bearer control protocols are usually specific to the transport technology used.2 MEGACO / H.248 ABNF (Augmented BNF) coding (short and long text format). or objects. It controls the parts of the call state that concern to connection control for media channels in a MG. modification and release. PCS supports H.g. Procedures define rules and actions associated with messages. Parameters describe how bearers and related things can be described.  trigger and detect tones and signals on the bearer. within the Media Gateway that can be controlled by the Media Gateway Controller. By standard is defined a basic framework for protocol. A connection model for the protocol describes the logical entities. parameters.  indicate of events concerning the bearer connections. ABNF is used for the syntax specification. It is specified in RFC4234 Media Gateway (MG): Provides a connection point between two dissimilar networks. Signals are various indications running on the bearer (e. a MG could terminate bearer channels from a switched circuit network (e. It converts media provided in one type of network to the format required in another type of network. A framework specifies the functional architecture.. With H. MEGACO V1. Main tasks of MEGACO protocol are to:  control bearer connection setup. Media Gateway Controller (MGC): Provides the management of resources on the MG. The main abstractions used in the connection model are Terminations and Contexts.  retrieve statistics about the bearer connection.g.Ia Interface and MEGACO / H.

248 . 2 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 7 .ITU terminology • MEGACO .IETF terminology RFC 3015 MGC the management of resources on the MG H248 / MEGACO media media H248 / MEGACO media media MG connection point between two dissimilar networks Fig.Media Gateway Control .Ia Interface and MEGACO / H.248 Protocol • H.

In contrast. which are grouped in a set of Descriptors that are included in commands. it is taken from or to the null Context. timeslot(s) on PCM line(s)  Termination Id: ip/84/access/338 port of RTP stream in an IP environment  TerminationID: "ROOT" means: ALL . Two types of terminations are distinguished:  physical terminations: Physical terminations are associated with a physical resource (e.TRAINING. Termination has unique identities -TerminationID.g. Such resources can be dynamically established and released. Examples for ephemeral terminations are RTP flows. A Termination is described by a number of characterizing Properties.3 Terminations A Termination is the very basic element of connection model. Terminations have a semi-permanent existence. when a physical Termination is Added to or Subtracted from a Context.Ia Interface and MEGACO / H. Each command specifies the TerminationId the command operates on.DE" hiG1200. Ephemeral Terminations are created by means of an Add command. respectively. Both must be IP Termination. 8 FN42425EN60GLA1 © 2011 Nokia Siemens Networks . They exist only for the duration of their use. Some examples:  Termination Id: "DS/S_17/STM1_01/E1_57@MG13. Signal to the MG to select an idle termination. PCS supports up to 2 Terminations in one Context.  ephemeral terminations: Ephemeral terminations do not represent physical resource but logical transport resources.the ROOT termination is used to indicate the entire MG  TerminationID "$" or ip/84/access/$ means: CHOOSE. timeslot of PCM line) which cannot be automatically released or setup. The Termination ID is assigned to the termination by the MG at the time of its creation. They are destroyed by means of a Subtract command.248 Protocol 1. It is logical entity on a MG that sources or sinks media and/or control streams.

The maximum number of Terminations in a Context is a MG property. Examples:  Context=170  Context = $ Connection model: termination and context Fig. If the MGC does not specify an existing Context to which the Termination is to be added. Media gateways that offer only point-to-point connectivity might allow at most two Terminations per Context. In general. 3 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 9 . A Termination exists in only one Context at a time. Media gateways that support multipoint conferences might allow three or more Terminations per Context. The Context describes the topology (who hears/sees whom) and the media mixing and/or switching parameters if more than two Terminations are involved in the association.4 Context A Context is an association between numbers of Terminations. the MG creates a new Context. A Termination may be removed from a Context with a Subtract command.248 Protocol 1.Ia Interface and MEGACO / H. an Add command is used to add Terminations to Contexts. and a Termination may be moved from one Context to another with a Move command.

AuditValue: The AuditValue command returns the current state of properties. The MGC may announce a handover to the MG by sending it a ServiceChange command. Subtract: The Subtract command disconnects a Termination from its Context and returns statistics on the Termination's participation in the Context. which signals/actions are to be applied to a Termination and specifying the topology of a Context (who hears/sees whom). modify Terminations or subtract Terminations from a Context. events and signals of a Termination. Add: The Add command adds a Termination to a Context. signals and statistics of Terminations. events. ServiceChange: The ServiceChange command allows the Media Gateway to notify the Media Gateway Controller that a Termination or group of Terminations is about to be taken out of service or has just been returned to service. 5. Furthermore. 10 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .248 Protocol 1. ServiceChange is also used by the MG to announce its availability to a MGC (registration). The Add command on the first Termination in a Context is used to create a Context. Notify: The Notify command allows the Media Gateway to inform the Media Gateway Controller of the occurrence of events in the Media Gateway. This includes specifying which events a Termination is to report. 6. The MGC may also use ServiceChange to instruct the MG to take a Termination or group of Terminations in or out of service. 3. 1. 4. 2.Ia Interface and MEGACO / H. Move: The Move command atomically moves a Termination to another Context. commands make possible complete control of the properties of Contexts and Terminations. and to notify the MGC of impending or completed restart of the MG. 7.5 Commands The protocol provides commands for manipulating Contexts and Terminations. Below is an overview of the commands. For example to add Terminations to a Context. The Subtract command on the last Termination in a Context deletes the Context. Modify: The Modify command modifies the properties.

Ia Interface and MEGACO / H. 4 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 11 .) MF ModifyReply Notify N NotifyReply ServiceChange SC ServiceChangeReply AuditValue AV AuditValueReply Fig.248 Protocol MEGACO commands Command token Add A AddReply Modify MF ModifyReply Substract S SubstractReply Modify(Event=….

248 Protocol 12 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .Ia Interface and MEGACO / H.

and which wildcard options are supported for the specific command. FN42425EN60GLA1 © 2011 Nokia Siemens Networks 13 . Command Add Sent By Used on Termination Type Wildcard Support IP ROOT W- O- No No No - - - SPDF Yes AuditCapabilitie s - AuditValue SPDF No Yes No No Modify SPDF Yes Yes No No Notify BGF Yes No No No ServiceChange BGF Yes Yes No No Subtract SPDF Yes No Yes No The PCS does not perform any state synchronization via audit commands. which terminations they can be associated with.Ia Interface and MEGACO / H. The audit command is just used to evaluate the BGF supported packages.248 Protocol Commands and Terminations between PCS and BGF: Following table shows in which direction commands are sent.

A TransactionPending indicates that the Transaction is actively being processed. each of which specifies its target Context and one or more Commands per Context. Corresponding responses to a TransactionRequest are received in a single reply. Entities may choose to delete the copies of the responses to transactions whose id is included in "confirmed transaction-id ranges" received in the transaction response messages. The TransactionID parameter must be the same as that of the corresponding TransactionRequest. It is used to prevent the sender from assuming the TransactionRequest was lost where the Transaction will take some time to complete. Each action typically specifies a ContextID. One is the case of modification of a termination outside of a context. A request contains one or more Actions. The other is where the controller requests the gateway to create a new context. A TransactionReply includes the results for all of the Commands in the corresponding TransactionRequest.Ia Interface and MEGACO / H. but has not been completed. there are two circumstances where a specific ContextID is not provided with an action. possibly preceded by a number of TransactionPending messages. The TransactionResponse Acknowledgement parameter can be found in any message. each of which is identified by a TransactionID. 14 FN42425EN60GLA1 © 2011 Nokia Siemens Networks . It carries a set of "confirmed transaction-id ranges".6 Transactions Commands between the Media Gateway Controller and the Media Gateway are grouped into Transactions.248 Protocol 1. Transactions are presented as TransactionRequests. However.

Ia Interface and MEGACO / H. 5 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 15 .248 Protocol Fig.

 Under-specified parameters. The command responder chooses one value from the offered list and returns that value to the command initiator. For each media stream. parm=value_.}. The list order specifies the command initiator's order of preference of selection. unambiguous value that the command initiator is instructing the command responder to use for the specified parameter. the text format of descriptors is: DescriptorName=<someID>{parm=value. The following table lists all of the possible Descriptors and their use. The common properties are also called the termination state properties. In general. using the CHOOSE value. over-specified or under-specified:  Fully specified parameters have a single. There are a number of common properties for Terminations and properties specific to media streams. These properties are described by Descriptors. Command parameters are structured into a number of descriptors. Not all descriptors are legal as input or output parameters to every command.  Over-specified parameters have a list of potential values. Parameters may be fully specified. 16 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .248 Protocol 1. allow the command responder to choose any value it can support.Ia Interface and MEGACO / H.7 Termination Properties and Descriptors Terminations have properties. there are local properties and properties of the received and transmitted flows.

ServiceChange In ServiceChange. report of events observed.Ia Interface and MEGACO / H. ObservedEvents In Notify or AuditValue. report of statistics kept on a termination or stream. TerminationState Properties of a termination (which can be defined in packages) that are not stream specific. LocalControl Contains properties (which can be defined in packages) that are of interest between the MG and the MGC. Packages In AuditValue. returns a list of packages realized by the termination. FN42425EN60GLA1 © 2011 Nokia Siemens Networks 17 . what. Events Describes events to be detected by the MG and what to do when an event is detected. Stream A list of Remote/Local/LocalControl Descriptors for a single stream. Remote Contains properties that specify the media flows that the MG sends to the remote entity. Statistics In Subtract and Audit. Local Contains properties that specify the media flows that the MG receives from the remote entity.248 Protocol Descriptor name Description Media A list of media stream specifications. it may occur in command replies and in Notify requests. Error Contains an Error Code and optionally error text. identifies which information is desired. etc. why ServiceChange occurred. Signals Describes signals applied to terminations. Audit In Audit commands.

Signals …. the Add command is used. either by creating it (ephemeral termination) or take it from the NULL context (physical termination). the descriptors consist of session descriptions as defined in SDP (RFC2327).  termination ID: The termination ID indicates which termination shall be added. 18 FN42425EN60GLA1 © 2011 Nokia Siemens Networks . Local. which means. If a new context is to be created. Stream.  termination descriptors: The termination can be specified by Media. The MGW adds the termination. Typically the MGC will set this to CHOOSE.248 Protocol Example of some Descriptor in Add and AddReply: To add a new termination to context. the context ID is set to a wildcard ($).request to the MG. that the MGW can freely select one of its terminations.Ia Interface and MEGACO / H. LocalControl. Events.request typically contains:  context ID: It specifies the context a new termination shall be added to. When text encoding the protocol. The MGC must issue an Add.descriptors. The AddReply gives the acknowledgement and can contain as additional parameters an Observed Events descriptor and a Statistics descriptor. In the Add.

LocalControl { Mode: Inactive gm/rsb=ON } } } }.7.248 Protocol Transaction = 222{ Context = $ { Priority = 0. LocalControl { Mode: Inactive gm/rsb =ON } Reply=222{ Context=168{ Add=ip/83/access/334{ Termination Id Media{ Stream=1{ Local{ v=0\r\nc=IN IP4 192. 6 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 19 .8.250\r\nm=audio 16568 RTP/AVP 0\r\n }}\n\t\t\t}\n\t\t}. Add =ip/83/access/${ Termination Id Media { Stream = 1 { Local { v=0\r\nc=IN IP4 $\r\nm=audio $ RTP/AVP 0\r\n }.141\r\nm=audio 5134 RTP/AVP 0\r\n }.80\r\nm=audio 16568 RTP/AVP 0\r\n } Fig.7.168.168.Ia Interface and MEGACO / H.168. Add =ip/83/core/${ Termination Id Media { Stream = 1 { Local { v=0\r\nc=IN IP4 $\r\nm=audio $ RTP/AVP 0\r\n }. Add=ip/83/core/336{ Termination Id Media{ Stream=1{ Local{ v=0\r\nc=IN IP4 192. Remote { v=0\r\nc=IN IP4 192.

 etc.  MSC Server out of service. The following ServiceChangeReasons are defined. 20 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .8 Service Change Reasons There may be events which must always be reported without any activation mechanism.Ia Interface and MEGACO / H. Such events are indicated by a SERVICE CHANGE command.248 Protocol 1. Typical examples for events triggering a SERVICE CHANGE are  termination out of service / termination in service  MGW restart  MGW registration (initial startup). This list may be extended by an IANA registration.

7 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 21 . downstream sync) 907 Transmission Failure 908 MG Impending Failure 909 MGC Impending Failure 910 Media Capability Failure 911 Modem Capability Failure 912 Mux Capability Failure 913 Signal Capability Failure 914 Event Capability Failure 915 State Loss Fig.248 Protocol Service Change Reasons 900 Service Restored 901 Cold Boot 902 Warm Boot 903 MGC Directed Change 904 Termination malfunctioning 905 Termination taken out of service 906 Loss of lower layer connectivity (e.g.Ia Interface and MEGACO / H.

as annexes). 22 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .Ia Interface and MEGACO / H. Packages may also define new error codes.g.248 Protocol 1. Packages defined by ITU-T may appear in the relevant recommendations (e. events and signals and statistics. events. Packages defined by IETF will appear in separate RFCs. But because different technologies and systems require different parameters. signals and procedures it is possible to define packages.9 Packages Protocol defines basic set of parameters. which are specific.

26) Extended Analog Line Supervision Package XAL (H.248.23) Fig. 8 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 23 .26) Analog Line Display ANDISP (H.23) Enhanced Alerting ALERT (H.Ia Interface and MEGACO / H. Protocol Package Name PackageID Generic G Base Root Package ROOT Tone Generator Package TONEGEN Tone Detection Package TONEDET Basic DTMF Generator Package DG DTMF Detection Package DD Call Progress Tones Generator Package CG Call progress tones detection package CD Analog Line Supervision Package AL Basic Continuity Package CT Network Package NT RTP Package RTP TDM Circuit Package TDMC Segmentation Package SEG Notification Behavior NB Call Type Discrimination package CTYP FAX/Textphone/Modem Tones Detection package FTMD Text Conversation package TXC Text Telephone package TXP Fax package FAX IP Fax package IPFAX Automatic Metering AMET (H.

and on-hook and off-hook transitions. The RequestIdentifier is used to correlate the request with the notifications that it may trigger. fax tones. 24 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .10 Events The EventsDescriptor parameter contains a RequestIdentifier and a list of events that the Media Gateway is requested to detect and report.248 Protocol 1. for example. The Event name consists of a Package Name (where the event is defined) and an EventID. continuity test results. Requested events include. Each event in the descriptor contains the Event name and optional parameters.Ia Interface and MEGACO / H.

248.1 DigitMap Completion Event CE H.248.1 On-hook ON H.248.248 Protocol Event name Event ID Standard Generic error event CAUSE H..248.248.1 Connection State Change CONNCHANGE H.Ia Interface and MEGACO / H.2 Connection State Change CONNCHANGE H.1 Quality Alert QUALERT H.1 DTMF character * DS H.248.1 End Tone Detected ETD H.1 DTMF character A … D DA…DD H..2 Discriminating Tone Detected DTONE H. Signal Completion SC H.248.1 Completion of a continuity test CMP H. 9 D0 .1 Flashhook FL H.2 Connection Mode Changed CONNCHNG H.248.1 DTMF character # DO H.1 Payload Transition PLTRANS H.1 DTMF character 0 .2 Fax Connection State Change FAXCONNCHANGE H.2 Call Type Discrimination Result CALLDISRES H.1 Long Tone Detected LTD H. Fig.248. D9 H.248.. 9 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 25 .1 Off-hook OF H.1 Network Failure NETFAIL H. Start Tone Detected STD H..248.248.248.

Ia Interface and MEGACO / H.248 Protocol 1.11 26 Tokens Token Coding for Token Add "A" Audit "AT" AuditCap "AC" AuditValue "AV" Auth "AU" Bothway "BW" Brief "BR" Buffer "BF" Ctx "C" ContextAudit "CA" DigitMap "DM" Disconnected "DC" Delay "DL" Duration "DR" Embed "EM" Emergency "EG" Error "ER" EventBuffer "EB" Events "E" Failover "FL" Forced "FO" Graceful "GR" H221 "H221" H223 "H223" H226 "H226" HandOff "HO" ImmAckRequired "IA" Inactive "IN" FN42425EN60GLA1 © 2011 Nokia Siemens Networks .

Ia Interface and MEGACO / H.248 Protocol Token Coding for Token Isolate "IS" InSvc "IV" InterruptByEvent "IBE" InterruptByNewSignalsDescr "IBS" KeepActive "KA" Local "L" LocalControl "O" LockStep "SP" Loopback "LB" Media "M" Megacop "!" Method "MT" MgcId "MG" Mode "MO" Modify "MF" Modem "MD" Move "MV" MTP "MTP" Mux "MX" Notify "N" NotifyCompletion "NC" Nx64k "N64" ObservedEvents "OE" Oneway "OW" OnOff "OO" OtherReason "OR" OutOfSvc "OS" Packages "PG" Pending "PN" Priority "PR" FN42425EN60GLA1 © 2011 Nokia Siemens Networks 27 .

248 Protocol 28 Token Coding for Token Profile "PF" Reason "RE" Recvonly "RC" Reply "P" Restart "RS" Remote "R" ReservedGroup "RG" ReservedValue "RV" Sendonly "SO" Sendrecv "SR" Services "SV" ServiceStates "SI" ServiceChange "SC" ServiceChangeAddress "AD" SignalList "SL" Signals "SG" SignalType "SY" Stats "SA" Stream "ST" Subtract "S" SynchISDN "SN" TerminationState "TS" Test "TE" TimeOut "TO" Topology "TP" Trans "T" ResponseAck "K" V18 "V18" V22 "V22" V22bis "V22b" FN42425EN60GLA1 © 2011 Nokia Siemens Networks .Ia Interface and MEGACO / H.

Ia Interface and MEGACO / H.248 Protocol Token Coding for Token V32 "V32" V32bis "V32b" V34 "V34" V76 "V76" V90 "V90" V91 "V91" Version "V" FN42425EN60GLA1 © 2011 Nokia Siemens Networks 29 .

The errors.12 Error descriptor Error Codes sent by MGC: 400 401 402 403 406 410 411 413 421 422 430 431 433 434 435 441 442 443 444 445 446 447 448 449 454 457 458 501 503 533 Syntax error in message Protocol Error Unauthorized Syntax error in transaction request Version Not Supported Incorrect identifier The transaction refers to an unknown ContextId Number of transactions in message exceeds maximum Unknown action or illegal combination of actions Syntax Error in Action Unknown TerminationID No TerminationID matched a wildcard TerminationID is already in a Context Max number of Terminations in a Context exceeded Termination ID is not in specified Context Missing Remote or Local Descriptor Syntax Error in Command Unsupported or Unknown Command Unsupported or Unknown Descriptor Unsupported or Unknown Property Unsupported or Unknown Parameter Descriptor not legal in this command Descriptor appears twice in a command Unsupported or Unknown Parameter or Property Value No such parameter value in this package Missing parameter in signal or event Unexpected Event/Request ID Not Implemented Service Unavailable Response exceeds maximum transport PDU size Yes No Yes No Yes No No No Yes No Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes The PCS sends out the error codes listed above. which are marked in the third column with “No”. 30 FN42425EN60GLA1 © 2011 Nokia Siemens Networks . will not be sent out.Ia Interface and MEGACO / H. but instead an error code 400 will be generated.248 Protocol 1.

The PCS reacts on all error codes not mentioned below in the same way: The session will either be rejected (ADD error command) or removed (MODIFY error) on the Application Function interface. with exception of: #514 "Media Gateway cannot send the specified announcement" #518 "Event buffer full" #519 "Out of space to store digit map" #520 "Digit Map undefined in the MG" #522 "Functionality Requested in Topology Triple Not Supported" Supported Error Codes defined in packages: All error codes defined in supported packages need to be supported. The following error codes have a special meaning: 412 No ContextIDs available 432 Out of TerminationIDs or No TerminationID available 506 Number of Transaction Pendings Exceeded 510 Insufficient resources 526 Insufficient bandwidth 529 Internal hardware failure in MG 530 Temporary Network failure 531 Permanent Network failure In all these cases the PCS will mark the BGF as overloaded and wait a configurable time before it retry to allocate resources on the BGF.248. FN42425EN60GLA1 © 2011 Nokia Siemens Networks 31 .248 Protocol Error Codes sent by MG: Supported H.Ia Interface and MEGACO / H.8 Error Codes: ALL.

(SDP)} 6: Context = $ Add = 20. Choose local session parameter 5: Reply Context = abc Add = 10. Add = 21{local parameter (SDP)} 9: Reply Context = abc Modify = 11 Fig... choose local session parameter 7: Reply Context = xyz Add = 20. Add = $ {remote parameter (SDP) Create Transaction. 10 32 FN42425EN60GLA1 © 2011 Nokia Siemens Networks . Create RTP Term.13 Examples Connection Set Up – Virtual Trunking hiG 1100 / 1200 hiG 1100 / 1200 4: Context = $ Add = 10. Add = 11 {local parameter (SDP)} Add remote session parameter to transaction data 8: Context = abc Modify = 11 {remote param. Create Transaction.Ia Interface and MEGACO / H.248 Protocol 1. Add = $ Create RTP-Term.

H248: AddReply 5.Ia Interface and MEGACO / H.248 Protocol Connection Set Up: PCS 5000 .Diam.SIP: invite 2.:AAR 3. 11 FN42425EN60GLA1 © 2011 Nokia Siemens Networks 33 .H248: Add 4.Diam.:AAA First Session First Context (Client 1.Remote partner) Fig.BGF Client 1 P-CSCF SPDF SBC Client 2 1.

Ia Interface and MEGACO / H.248 Protocol 34 FN42425EN60GLA1 © 2011 Nokia Siemens Networks .