[Spce-user] Peering Rules database vs. GUI Issue

[Gary Nieboer]

We have experienced a few issues with our "Peering Rules" on SPCE, 3.3.1.

A created rule exists in the GUI, but when routing a call through the SBC,
the call follows a route to a default peer rather than the peer indicated
in the GUI.

We recently did a comparison of what is shown in the database:  lcr_rules

                            select * from lcr_rule;


Here are a few lines from the database:   Some numbers are replaced with
"`" and not fully shown:

Note:  Rule 102 is missing from the database


| id  | lcr_id | prefix | request_uri | from_uri | stopper | enabled |
group_id |
+-----+--------+--------+-------------+----------+---------+---------+----------+
| 101 |      1 |        | ~~~~~20088  | NULL     |       0 |       1 |
  23 |
| 105 |      1 |        | ~~~~~20186  | NULL     |       0 |       1 |
  23 |
| 106 |      1 |        | ~~~~~74891  | NULL     |       0 |       1 |
  23 |



Now, here is a screenshot of the GUI for the same rules:
Note:  Rule 102 exists under peer group 23 for the GUI.
[image: Inline image 1]



It appears we should trust the data in the database and not the GUI, but
I'm assuming it is not desired behavior for the GUI and database to reflect
different info.

If you would like more information, we can share it.

Please let me know if there is anything we can do to ensure the GUI
reflects the actual activity of the database and ngcp/kamailio.

Thanks,

Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/6d896dc7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 30444 bytes
Desc: not available
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20140801/6d896dc7/attachment.png>