Incomplete entry in routing table
Posted by Elena Brambilla, Last modified by Daniel Lizaola on 14 December 2017 04:06 PM

In case of using a routing table with conflicting entries, the error NO MATCHING ENTRY (INCOMPLETE ENTRIES PRESENT) appears. This can happen when the route entries are as follows and the number 123 was dialed.

routing-table called-e164 OUT

       route 1234 dest-interface IF_BRI_03
       route 123 dest-interface IF_SIP


To avoid this, following can be set to succeed the entry for 123.

routing-table called-e164 OUT

       route 1234 dest-interface IF_BRI_03
       route 123T!0 dest-interface IF_SIP


Adding the T!0 forces the entry 123, although there is another entry which incompletely matches. 

(1926 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).