Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Průvodce řešením problémů stáhnout pdf (Strana 30)

F5 SDC Troubleshooting Guide

Proprietary and Confidential Information of F5 Networks

 To add a message with an application ID according to spec (not 0):

 Create a message so that the name of this message will be built as concatenation

of name and needed interface. For example, for a S6b application:

<! -- applicationId="16777272" -->

<message name="RAR-S6b" code="258" applicationId="16777272"

isProxiable="true" isRequest="true" sentByClient="false"/>

<message name="RAA-S6b" code="258" applicationId="16777272"

isProxiable="true" isRequest="false" sentByClient="true"/>

 To add AVPs for a specific vendor whose codes are used by other interfaces:

 Add a prefix (vendor name) to the AVP name. For example:

<! -- vendorId="12645" -->

<avp name="Vodafone-Radio-Access-Technology" code="260" format="enumerated"

mRule="may" vendorId="12645"/>

 To distinguish between two AVPs that have the same name, but a different code in the

interface:

 Add suffix that defines the data type of AVP. For example, in 3GPP Vendor-Id

10415 Service-Type AVP has three commands code, so can add its data type at

the end:

<avp name="Service-Type-Grouped" code="1483" format="grouped" mRule="must"

vendorId="10415"/>

<avp name="Service-Type-Unsigned32" code="2031" format="unsigned32"

mRule="must" vendorId="10415"/>

<avp name="Service-Type-Enumerated" code="6" format="enumerated"

mRule="must" vendorId="10415"/>

 If there is more than one AVP whose name ends with the same address and their

data type are addresses too, than the first character before the address should be

changed. For example:

<avp name="Served-Party-IP-Address" code="848" format="address" mRule="must"

vendorId="10415"/>

<avp name="Served-Party-Ip-Address" code="248" format="address" mRule="must"

vendorId="10415"/>

5.3.2 Message Parsing Failures

Message parsing can fail due to multiple reasons. This section presents some parsing

troubleshooting issues including providing instructions on how to investigate them in order to

find out the root cause of the issue.

1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 41 42

Žádné komentáře

Red Hat NETWORK 4.0.5 - CHANNEL MANAGEMENTT GUIDE Průvodce řešením problémů Strana 30