<div dir="ltr">I have a couple Grandstream HT502s that occasionally get stuck with the detected NAT type of <div>Warning: 399 ip.address "Detected NAT type is UDP Blocked". When that happens the device is never able to complete a call until it is restarted. Where should I start looking to create a monitor that will parse those messages and send a reboot (i.e. sofia profile [profile] flush_inbound_reg [call_id] reboot)<br>
</div><div><br></div><div style>Thanks, </div><div style>Nick</div><div><br></div><div style><u>Sample SIP Message</u></div><div style><div>SIP/2.0 200 OK</div><div> Via: SIP/2.0/TCP XXX.XXX.XXX.XXX:PORT;branch=z9hG4bK2N9vy7BmyF40B</div>
<div> From: <<a href="mailto:sip%3A22521002@DOMAIN.COM">sip:22521002@DOMAIN.COM</a>>;tag=3yNZa6ZNv6K6g</div><div> To: <<a href="mailto:sip%3A22521002@DOMAIN.COM">sip:22521002@DOMAIN.COM</a>>;tag=1662499825</div>
<div> Call-ID: 3901be5e-db58-1230-109f-bc764e103a41</div><div> CSeq: 38881081 NOTIFY</div><div> Supported: replaces, path, timer, eventlist</div><div> User-Agent: Grandstream HT-502 V1.2A 1.0.8.4 chip V2.2</div>
<div> Warning: 399 XXX.XXX.XXX.XXX <b>"Detected NAT type is UDP Blocked"</b></div><div> Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE</div><div> Content-Length: 0</div><div style>
<br></div></div></div>