How to handle the IP inconsistency in the contact when easygbs is cascaded with the upper level

In the national standard GB28181 Agreement , Cascade if necessary , Then the subordinate platform needs to log in and register with the superior platform , To open the connection between superiors and subordinates .TSINGSEE The national standard platform of Qingxi video EasyGBS It is through GB28181 Cascade system , Connect to other platforms , When docking with third-party platforms , Many users will choose cascading function .

When we use EasyGBS When cascading with superiors , Under normal circumstances, the reply is source Inside ip（ For example, we EasyGBS and EasyCVR）：

But if the superior is right contact Inside ip If required , Some sites will show that they have received the registration status , But the superior didn't reply 200 OK：

Many users modify the local in the cascade in this case ip, Reconfigure the child link , This treatment is wrong , Grab the bag again contact It's still the same ip：

In fact, it should be modified easygbs.ini Inside siphost, After modification, restart the service , Then send the registration message again to see contact Inside ip become siphost Of course. ：

TSINGSEE National standard of Qingxi video development GB28181 Protocol platform EasyGBS Support access authentication , And to provide RTSP、RTMP、HTTP-FLV、HLS And other protocol stream output , It can easily build a security video monitoring platform , besides ,EasyGBS Provide external server access status 、 Information , control HTTP API Interface , Free to call and secondary development .