Teletalks CS Core Issue:

Incoming BICC from Huawei MSS call fails

For internal use

1
Nokia Siemens Networks

Presentation / Author / Date

Forward bearer establishment method

with delayed forward tunneling
3. IAM(APP ( "connect forward", BCU-ID1, BNC Char: IP/RTP,
BCT = Tunneling to be used, supported codec list))

SAI = FORW
UPD.STOM = CN

6. APM(APP ( "connect forw, no notif+sel cdc", BCU-ID2,

selected codec, available codec list))

MSS1

UPD.STOM = CN
MSS2

11. APM(APP (BCI = IPBCP1))

16. APM(APP (BCI = IPBCP2))

23. NotifyReply

22. NotifyReq(BNC Est.)

15. NotifyReply

14. NotifyReq(IPBCP2)

13. ModReply

12.ModReq(IPBCP1,
Event=Tunnel Ind,)

5. AddReply

4. AddReq(T2, codec,
TunOpt=2)

ACM depends on
the terminating
side call setup in
MSS2.

23. NotifyReply

22. NotifyReq(BNC Est.)

18. ModReply

17.ModReq(IPBCP2)

10. NotifyReply

9. NotifyReq(IPBCP1)

25. ANM

8. ModReply

2. AddReply
7.ModdReq(Establish BNC,
selected codec,
Event=Tunnel Ind.)

1. AddReq(T1, no codec,
TunOpt=2)

24. ACM

IP
19. User Plane

established.

20. NbUP Init

T1
MGW1

21. NbUP Init

Delayed forward tunneling is initiated only with codec negotiation procedure.

For internal use
2
Nokia Siemens Networks

Presentation / Author / Date

Ack

T2
MGW2
The purple parts are the IP
tunneling specific items.

Summary of Analysis

NSN MSS sent release message because the value of the UMTS
AMR2 mode-set received from Huawei MGW is not same as Active
codec set (ACS) in the BICC APM message sent by NSN MSS.

This problem has to be solved from Huawei end.

For internal use

3
Nokia Siemens Networks

Presentation / Author / Date

Detail Analysis:

In the control plane signaling (BICC) message IAM, Huawei MSS sent UMTS AMR2 codec with Active
codec set (ACS): 12.2 7.40 5.90 4.75, Supported codec set (SCS): 12.2 7.40 5.90 4.75.
Codec information from BICC: IAM sent by Huawei MSS:
- Codec List:
Single Codec
- Length indicator: 6
Compatibility information
- Send notification indicator for pass-on not possible: Do
not send notification
- Instruction indicator for pass-on not possible: Release
call
- Send notification indicator for general action: Do not s
end notification
- Instruction indicator for general action: Release call
Contents:
- Organization Identifier: ETSI
- Codec type: UMTS Adaptive Multi-Rate 2
- Active Codec Set: 12.2 7.40 5.90 4.75
- Supported Codec Set: 12.2 7.40 5.90 4.75
- Maximal number of Codec Modes: four
- Optimisation of the ACS supported

For internal use

4
Nokia Siemens Networks

Presentation / Author / Date

Detail Analysis:

NSN MSS sent codec information to NSN MGW in the megaco message: AddReq:
04 05 02 06 95 95 04 [ETSI, UMTS_AMR_2, ACS={4.75, 5.90, 7.40, 12.2}, SCS={4.75, 5.90, 7.40,
12.2}, MACS=4, ICM=4.75]

After receiving addReply from NSN MGW, NSN MSS sent APM message with selected codec UMTS
AMR2, ACS: 12.2 7.40 5.90 4.75, and SCS: 12.2 7.40 5.90 4.75 to Huawei MSS.
Codec information from BICC: APM message sent by NSN MSS:
Single Codec
- Length indicator: 6
Compatibility information
- Send notification indicator for pass-on not possible: Do not
send notification
- Instruction indicator for pass-on not possible: Release call
- Send notification indicator for general action: Do not send
notification
- Instruction indicator for general action: Release call
Contents:
- Organization Identifier: ETSI
- Codec type: UMTS Adaptive Multi-Rate 2
- Active Codec Set: 12.2 7.40 5.90 4.75
- Supported Codec Set: 12.2 7.40 5.90 4.75
- Maximal number of Codec Modes: four
- Optimisation of the ACS not supported

For internal use

5
Nokia Siemens Networks

Presentation / Author / Date

Detail Analysis:

Tunneling of IPBCP message happened between both MGWs via BICC APM message. Just after
that NSN MGW received Userplane info from Huawei MGW where the codec is UMTS AMR2 but
the codec modeset= 0x80, which indicates codec mode = 12.2 kbps. NSN MGW expected mode
sets
to be included all 12.2 kbps, 7.40kbps, 5.90kbps and 4.75kbps which is same as Active codec set in the
APM message sent by NSN MSS.
From internal message monitoring of NSN MGW:
76 B4A3 user_plane_info_s bc2prb 0004 00 <-d3p003 000A 00 20:02:13.57 00:00:00.54 24 0072 0072 0000 02 (Routed) 754F 1FFE 00 3EA5
codec 06 0x06 6 umts_amr2_c byte 20 1
modeset
80 00
modeset_dsp_t
22
2
low_byte
80
0x80 128
amr_wb_23_05_c; amr_nb_12_2_c byte
high_byte
00
0x00 0
byte 23
1
Where the codec mode is defined as below:

MSB: 8

LSB: 1

12.2

10.2

7.95

7.4

6.7

5.9

5.15

4.75

Codec mode 0x80 (hex) = 1000 0000 means 12.2 kbps only.

For internal use

6
Nokia Siemens Networks

Presentation / Author / Date

22

Detail Analysis:
Codec modeset must have to be the same both at control plane and user plane. Otherwise, MGW will
reject with AMR modeset mismatch noticed when userplane info msg received, result in REL with normal
unspecified in BICC.
From internal message monitoring of NSN MGW:
txt:HP1-29 AMR modeset mismatch noticed when userplane info msg received
loginfo:E+HP1
mgw_nsap:45000880150159986F0000000000000000000000
sctpstream:1
own_unit:ISU-14
CtxID:3454F
vmgwID(d):MGRMN2V06 (5)
type:IP
if:Nb
dsp_pp:1
dsp_servid:E037
unit:TPG-17
IPRoute:0
reservedIP:0A15658D
reservedPort:325C
remoteIP:0A15010A
remotePort:1D4
observer:5F1
msg:B4A3
codec:0206959504
payloadtype:6C
H248GenCause:Failure Temporary(FT=3)
version:BC2PRB3X.PAC 13.238-0 11/02/26 GN3ENVU4.PAC 7.5-0
For internal use
7
Nokia Siemens Networks

Presentation / Author / Date

Way forward:
Option 1: Huawei will solve the problem from their end.
Options 2: NSN will limit the value of ACS to single mode. (Already tested and working)
Option 3: Both end has to configure: a) codec negotiation as disabled Implement default codec where only
UMTS AMR2 with single mode (any of 4.75, 5.15, 5.9, 6.7, 7.4, 7.95, 10.2 or 12.2 kbps) will be allowed at
inter-MGW (Nb) interface

For internal use

8
Nokia Siemens Networks

Presentation / Author / Date