Hi guys, sorry for bother you, but I need some help.
Today my Call Manager Server fall down, so i`m running with a survival mode in a Cisco 3725 Router with Version 12.3(11) software.
In this router I have the E1 isdn with 30 channels to send and receive calls. so I don`t have a problem to dial out when the phones are in call manager fallback, but I have problems to dial in to any phone.
My internal numbering plan is 540113XX where the 13XX is the number that my ISDN line give to router (the external number is 5550 - 13XX) and in my call manager I have a translation rules that converts this 13XX in 5401 13XX.
I need to create the same rule for my router, is this possible?
The line give to me 13XX and I need to agregate 5401 + the number dialed.
I configured like you say and still have the problem that cannot reach any phone, called from outside.
I tested the configuration and looks fine but something is missing
router#test voice translation-rule 1 1388
Matched with rule 1
Original number: 1388 Translated number: 54011388
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
this is exactly what I expect because the ephone is registered in the router as:
preference 0 secondary 9
But i can reach the phone, I don`t know is something is missing,
There are any debug that I can do to test why the call cannot reach the internal phone? or any test?
I think that works now, I saw in the debug that is machting with another dial peer, so I add the destination pattern in the new dial peer and it`s seems to work, (i`m doing the config remotly, I`ll test in the office tomorrow morning) i`ll let you know.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.