MSAN UA5000 Cases Chapter 5 UA5000 Narrow-band Service
Confidential Information of Huawei. No Spreading without Permission
77
Alarm Informati
on:
Null
Cause Analysi
s:
1. The subscriber perception may be biased.
2. Because the digitmap is not optimal, multiple matches exist during digit collection. When
both long and short timers are set, the long timer takes precedence.
Handling Proce
ss:
1. Capture lower layer messages using DSWIN when the number 010114 is dialed. It is found
that the interval from when the last digit is received by the AG to when the AG reports the digits
is 5s. This is the duration of the long timer. The short timer (3s) is not effective.
71: [021][15:04:27.620]H248_DMM: Phyterm index 1 <H248dmm.c:2507>
H248dmm_RMAMsgProc::Receive a Code From Asl: "4" in phyterm 1 at dspchannel 9
71: [022][15:04:27.620]H248_DMM: Phyterm index 1 <H248dmm.c:5451>
H248dmm_RcvDialMsgProc::ucDialNum 52 phyterm 1 runinfo 9 dcb 9 match state 6 buff now
6 begin 0 end 6
71: [023][15:04:27.620]H248_DMM: Phyterm index 1
<../../../src/yyservice/voip/H248APP/H248dmm/H248dmm.c:5613>####Dmm stop timer, name
0x1000003 para 1
71: [024][15:04:27.620]H248_DMM: Phyterm index 1
<../../../src/yyservice/voip/H248APP/H248dmm/H248dmm.c:5618> The dmm match state
change from 6 to 3, phyterm 1
71: [025][15:04:27.620]H248_DMM: Phyterm index 65535
H248dmm_MatchDigitMap::NM=0, TM=0, PM=1, FM=0, UM=0, MaxMatch=0, Match
Mode=2
71: [026][15:04:27.620]H248_DMM: Phyterm index 1 <H248dmm.c:5658>
H248dmm_RcvDialMsgProc::H248DMM_DIALMatch:ulAnswer=2, LastAnswer=2,
MaxMatch=0, MatchMode=2,TimeName=0x1000004, Buf now=6, begin=0, end=7, b
71: [---]uf content=0523114
71: [027][15:04:27.620]H248_DMM: Phyterm index 1 <H248dmm.c:5801>
H248dmm_RcvDialMsgProc::H248DMM_TIMER_SHORT
71: [028][15:04:27.620]H248_DMM: Phyterm index 1
<../../../src/yyservice/voip/H248APP/H248dmm/H248dmm.c:5804> The dmm match state
change from 3 to 5, phyterm 1
71: [029][15:04:27.620]H248_DMM: Phyterm index 1
<../../../src/yyservice/voip/H248APP/H248dmm/H248dmm.c:5831>####Dmm start timer, name
0x1000004 time 5 para 1
71: [030][15:04:32.620]H248_DMM: Phyterm index 1 <H248dmm.c:2231>
H248DMM_TIMER_Proc::pTimerMsg->ulName=16777220
71: [031][15:04:32.620]H248_DMM: Phyterm index 1 <H248dmm.c:2270>
H248DMM_TIMER_Proc::pstDcb->ucMatchResult=2
71: [032][15:04:32.620]H248_DMM: Phyterm index 1 [h248dmm.c6045]
71: [033][15:04:32.620]H248_DMM: Phyterm index 1 [h248dmm.c6078]
71: [034][15:04:32.620]H248_DMM: Phyterm index 1 [h248dmm.c6105]ucMatchResult:2
71: [035][15:04:32.620]H248_DMM: Phyterm index 1 <H248dmm.c:6150>
H248dmm_ReportMatchResult::Dcb index 9 Call type 0 Result 2 IsImm 0 timeout 1 numlen 7
num 0523114
71: [036][15:04:32.620]H248_DMM: Phyterm index 1
<../../../src/yyservice/voip/H248APP/H248dmm/H248dmm.c:2287>####Dmm start timer, name
0x1000000 time 10 para 1
8e: [037][15:04:32.620]msg from mg([10.144.76.210]:2944) to mgc([10.144.75.55]:2944): !/1
[10.144.76.210]:2944
T=193{C=-{N=A1{OE=369260805{20081013T15043262:dd/ce{ds="010114",meth=PM}}}}}
From 15:04:27.620 when the last digit "4" is received to 15:04:32.620 when the message is
reported, the interval is exactly 5s.
2. Analyze the digitmap, when 010114 is dialed, the number is first matched to 010xxxSxxxxx.
However, because of the presence of [0-9].L, where "." indicates unlimited repetition of the
dialing event before ".". The timer after "." is a long timer. According to the H.248
specifications, when the long timer conflicts with the short timer, the long timer prevails. The
long timer is therefore activated.
3. Delete the [0-9].L dialing rule and perform the test again. The short timer is effective.
To Next Page
Loading...
