Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| vendors:cisco:routers:radius:radiusvoicecalls [2026/11/11 14:11] – [SQL Queries] gerardorourke | vendors:cisco:routers:radius:radiusvoicecalls [2026/11/12 15:33] (current) – [SQL Queries] gerardorourke | ||
|---|---|---|---|
| Line 387: | Line 387: | ||
| === Update invalid Active Calls ==== | === Update invalid Active Calls ==== | ||
| - | === STEP 1 - Update | + | === STEP 1 - Update |
| - | We can find these calls later - by checking how many rows have a disconnect cause of 128 | + | Why disconnect cause of 128? |
| + | * Valid Disconnect causes are from 1 - 127, so 128 will never be sent by Radius - so we KNOW any record that has this connect cause was updated by this SQL query (which will run as a SQL job ever ~10 mins) | ||
| + | * We can find these calls later - by checking how many rows have a disconnect cause of 128 | ||
| <code sql> | <code sql> | ||
| UPDATE radiusVoiceCalls | UPDATE radiusVoiceCalls | ||
| Line 400: | Line 402: | ||
| </ | </ | ||
| - | === STEP 2 - Update the calls as non active with a disconnect cause of 128=== | + | === STEP 2 - Update the calls as non active with a disconnect cause of 128 === |
| We can find these calls later - by checking how many rows have a disconnect cause of 128 | We can find these calls later - by checking how many rows have a disconnect cause of 128 | ||
| <code sql> | <code sql> | ||