VeraSMART error "53-007: Configuration error: no # prompt found"

Unanswered Question
May 3rd, 2010

First, I hope this is the right place. I was told it came w/ a year of support; however, in all the excitement, I didn't inquire if "they" referred to Cisco or Veramark.

So here's the problem; any appreciation would be greatly appreciated. Towards the end of the installation, on the screen where I enter the UC's admin credentials right before the auto-config portion of the setup begins, and I get an error message

"Configuration error: no # available"

[Screenshot attached]

I followed the setup instructions from "UC500 Interface Setup"

aaa new-model

aaa accounting connection h323 start-stop group radius

gw-accounting aaa

no suppress


radius-server host x.x.x.x acct-port 1813

radius-server vsa send accounting

radius-server key <password>


username cisco priv 15 secret 0 cisco

Obviously, I can login w/ "cisco" "cisco" and get to an enable prompt, however this program goes no further.

I can ping the router from the call accounting server, as well as telnet into it from the call-account server.

I verified the RADIUS key was typed in correctly.

The router's IP is

The call accounting server's ip is

As per the instructions we're using port 1813.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Marcos Hernandez Tue, 05/04/2010 - 09:09

When you login with this user, are you able to get to enable mode and see the "#" prompt?

jeremyneedle Tue, 05/04/2010 - 12:07

That is correct. When I telnet into the router it instantly takes me to the # prompt.

Marcos Hernandez Tue, 05/04/2010 - 12:11

In that case, you need to contact Veramark and ask why they are not parsing the prompt correctly. You can also configure the UC500 manually. VeraSMART offers sample configurations on how to achieve this integration.



jeremyneedle Wed, 05/12/2010 - 01:35

Ok. My partner called them up, and raised a little hell so that they gave us a ticket number. I'd like to keep this discussion open for the time being, and if they help me resolve it, I'll post the solution here.

I must say I really REALLY think its a weakness in their design to necessitate an EXEC shell for CDR accounting.

jeremyneedle Thu, 06/17/2010 - 00:12


Their techsupport had to open a GoTo Assist session and made multiple modifications to the program's XML file [XML configurations that you would have no way of knowing how or what to edit since there is no documentation available unless you pay the $695]

After tech support made these modifications to several of the program's XML configuration files, then it worked beautifully


This Discussion