Hello, everyone!
I will share one case about the ONT HG8245's call outage below.
Product Model
ONT HG8245
Problem Description
Fault symptom: The ONT's call service drops some minutes after the call is made.
Problem Analysis
1. The optical module status, optical power, and temperature of ONT were verified.
WAP>display optic
LinkStaus: ok
Voltage : 3234 (mV)
Bias : 33 (mA)
Temperature: 59 (C)
RxPower : -20.09 (dBm)
TxPower : 1.87 (dBm)
RfRxPower : -- (dBm)
VendorName : SOURCEPHOTONICS
VendorSN : CBU2025003
2. We review the status of MG.
WAP>vspa display mg if state
MgID :0
MgSignalIPaddress :10.67.151.245
MgMediaIPaddress :10.67.151.245
ProxyPriIPaddress1 :192.168.40.6
ProxyPriIPaddress2 :255.255.255.255
ProxySecIPaddress1 :255.255.255.255
ProxySecIPaddress2 :255.255.255.255
ProfileIndex :0x0
SrvLogicIndex :0x0
MgSignalPort :5060
ProxyPriPort :5060
ProxySecPort :65535
MgDesc :
MgDomainName :
ProxyPriDomainName :
ProxySecDomainName :
RegisterURI :cnt.voip.gye
HomeDomainName :cnt.voip.gye
PhoneContext :
ConferenceFactoryURL :
ProfileName :
SrvLogicName :Default
TransMode :1
CSMode :0
ProxyAddrMode :0
FaxTransMode :0
ModemTransMode :0
FaxModemNegoMode :0
FaxModemPacketInterval :0
FaxModem2198NegoMode :0
FaxModem2198StartMode :0
PrimaryProxyState :2
SecondaryProxyState :3
DhcpOption :1
AuthUserName :
AuthPassWord :
3. During the call flows, signalization messages were captured and we could observe that the call outage occurred on two different telephone lines at the same time.
func[HW_TPA_UDPRecv L467]:
Receive Message From 192.168.40.6:5060@1380080 Ticks
func[HW_TPA_UDPRecv L468]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.67.151.245:5060;branch=z9hG4bK1ip001021n01j10nm31lj3jlp
Call-ID: j2s0k23z401p388k3j0k24jz2n1kpnin@10.67.151.245
From: <sip:43883261@cnt.voip.gye>;tag=1s8cpiiz
To: <sip:2925791@cnt.voip.gye;user=phone>;tag=5n01tu33-CC-26
CSeq: 4 BYE
Content-Length: 0
$Time:[2015-04-11 09:23],DOT_Code:495714684,^~0^$
func[HW_TPA_UDPRecv L467]:
Receive Message From 192.168.40.6:5060@1380078 Ticks
func[HW_TPA_UDPRecv L468]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.67.151.245:5060;branch=z9hG4bKc4kl8i3cipkj1kc232jm044c3
Call-ID: 3ziznmm04mi2pl482j42l1mjjms1s1l3@10.67.151.245
From: <sip:43883480@cnt.voip.gye>;tag=mjczzp40
To: <sip:2925830@cnt.voip.gye;user=phone>;tag=2z16y76y-CC-26
CSeq: 7 BYE
Content-Length: 0
4. We asked for help from Chinese staff and we sent them the log information of a 2 hours call, according to the parameters below.
WAP>set dbgoutput outputtype all swt 1
WAP>vspa debug module 201 cmd 2 subcmd 1
WAP>vspa debug module 206 cmd 1 subcmd 1
WAP>vspa debug module 200 cmd 1 subcmd 1
WAP>vspa debug module 27 cmd 1 subcmd 0xffffffff para1 0 para2 0
Root Cause
After analyzing the log information, it was found that a new signaling message (INVITE) was sent by the ONT during the call-on process causing the outage of the current call and therefore the call drop occurred.
Solution Description
It was necessary to set the following configuration to solve the issue in order to force the voice working mode during an established call.
Suggestion
During the configuration process, the previous parameters should be set to avoid this issue.
Thank you.
