Sympton:
——————————————-
TE40 caller : 202.102.40.211, E.164: 02510000
TE40 caller : 192.168.0.109, E.164: 02510000
H600 callee : 192.168.0.105, E.164: 654320
VP9650: 202.102.40.219
Pcap file was captured on H600 side.
All exchanged signaling commands between H600 and VP9650:
->SCI
<-SCR,facility
->setup
<-ARQ
->ACF
<-alerting,connect
->facility
->TCS
…Twenty seconds later…
–>ReleaseComplete, DRQ
(h225 or h245) and ((ip.dst eq 192.168.0.105 and ip.src eq 202.102.40.219) or (ip.src eq 192.168.0.105 and ip.dst eq 202.102.40.219))
Sympton:
H600 after received TCS from VP9650 did not response with any further commands, and led to a ReleaseComplete of VP9650.
Trouble shooting:
Checked the facility commands of VP9650, found that its Q.931 crv value was 0, but with a facility reason of 5(startH245)
But we did not support that kind of rules.
Checked the ITU/T documents, found out it’s a standard procedure.
Solution:
You know what should be done.