Shulou(Shulou.com)06/01 Report--

MGCP protocol troubleshooting example analysis, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Reason: the message reported by the user off-hook contextID non-empty docking ZTE platform is not compatible, resulting in the user can not hear the dialtone off-hook

Failure phenomenon:

1. Docking with ZTE platform, the user does not have a dial tone when he goes off-hook, or does not have a dial tone after restarting the device.

2. After an outside call, the phone can answer normally, and then the call will be normal.

Device packet prompt message:

Reason analysis: through the message analysis in the packet, the contextid reported off-hook is not empty, and the ZTE platform is not compatible with this kind of message. the normal processing flow platform should send a MF message, which carries a signal (cg/dt) requiring the device to play dailtone; to the user after the device is restarted, because the platform has not sent a message to remove the contextid, so the contextid in the off-hook message is still not empty and cannot be called. When an external call comes in, the incoming call and the outgoing call are normal, because the office sends a message to the device to create the associated domain, and instructs the device to remove the associated domain at the end of the call, and the contextid=NULL in the terminal message can be handled correctly when the terminal goes off-hook again, so the subsequent call can be normal.

Treatment measures:

1. Negotiation platform. It is recommended to do compatibility processing for such messages.

2. The device side detects the call, confirms that the call is due to network interruption, goes off-hook again, and empties the contextid actively.

Remarks: how to reproduce the problem

1. The device goes off-hook and calls any outside line.

2. Disconnect the network for a period of time

3. When the call of the device is interrupted, resume the network connection

4. Call off-hook again

After going through the above steps, the call of the device is interrupted, but the associated domain is not removed. After the network is restored, the device registers successfully and goes off-hook again. The contextid in the reported message is not empty.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.