I have a central Callback server with PRI (3620) which receives callback requests from a 2611 (with up to 5 BRIs) Each BRI has a seperate telephone number (can't change this).
The config is built on rotary dialer and dialer map commands.
The config appears to be functioning correctly and adding channels as load increases BUT the central router (callback server) shows multiple failures in the "show isdn history table".
It appears as if the call comes into the callback server and the callback occurs to the dial string on the first dialer map statement. As the traffic load increases more channels are added. BUT it appears that every time a channel has to be added the router has to fail the previous channels which are already in use (BUSY). By the time the router gets to the 5th BRI it has to fail each of the previous 4 in turn. This is not necessarily causing much delay but it makes monitoring the ISDN calls very awkward. The remot router does not show any failures.
Any ideas how to prevent the failures on ISDN HISTORY?
Call Calling Called Remote Seconds Seconds Seconds Charges
Type Number Number Name Used Left Idle Units/Currency
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.