SOLVED Lenny gone AWOL

[geopeterwc]

Calls to Lenny show "answered" or "busy" in the CDR records, but Lenny isn't responding on the call. That's the case with an older iPBX2021.0, iPBX2027-D and a new iPBX2026 installation. I've configured blacklisted numbers to route to Lenny, but from all appearances, Lenny is in hiding somewhere!???

Also an aside, Eleanor isn't answering either!

 

[islandtech]

Lenny is not replying to the invite

 

[wardmundy]

Try this: https://www.voip-info.org/forum/threads/deploy-lenny-tts-apps-with-ipbx-2026.28681/#post-183070

 

[geopeterwc]

Try this: https://www.voip-info.org/forum/threads/deploy-lenny-tts-apps-with-ipbx-2026.28681/#post-183070

This calls out installation on an iPBX2026 configuration. Does this work for earlier versions of iPBX as well?

 

[wardmundy]

What version??

 

[geopeterwc]

What version??

I had called out Incredible PBX 2021-0 and Incredible PBX2027-D. These use a custom dial-out to " SIP/[email protected] " ... or has Lenny died for these iPBX versions?

 

[wardmundy]

2027 should be fine. 2021 is a maybe, but it shouldn't hurt anything so long as it's a Debian or Ubuntu platform.

 

[lleachii]

L

GO HERE Post in thread 'Trouble with Lenny'

Jan 10, 2026

I had to:

• change the URI from SIP to PJSIP
• create a trunk named 'lenny.from-nv.com' - set no authentication, no registration, and 0 for qualify frequency
• open the RTP ports on the firewall

• lleachii

• 

 

[Bleistift]

As of July 24, 2026:
• calls to 347-514-7296 (Lenny A) aren't working
• calls to 423-468-4041 (Lenny B) are working as normal

 

[ostridge]

As of July 24, 2026:
• calls to 347-514-7296 (Lenny A) aren't working
• calls to 423-468-4041 (Lenny B) are working as normal

I guess that Lenny must have moved house?

 

[geopeterwc]

I've installed the "new Lenny" per the instructions above ... but when attempting a connection to Lenny via an IVR option or Blacklist setting, I get a busy signal, and no connection to Lenny. I haven't tested transfer of "offending" calls to Lenny by users, but ... I've obviously overlooked something - maybe in the configuration of the "custom extension" settings? What's the recommendation?

 

[wardmundy]

@geopeterwc: Repeat the steps and watch for errors.

 

[geopeterwc]

Thanks @wardmundy ... I'm in the process of moving a small installation of iPBX2027 to a new 2026 to take advantage of PJSIP and moving the DIDs from Chan-SIP. The (Grandstream) phones have been using PJSIP since the iPBX2027 installation a year or so ago.

Should I presume it best to uninstall Lenny using Module Admin and then reinstall from the CLI per the instructions, or can I just run through the steps and overwrite the previous installation using the CLI? This is on a new iPBX2026, Asterisk 22 configuration?

 

[geopeterwc]

I deleted the Lenny extension from the list of extensions, then using Module Admin, I removed the Lenny application. Doing this cleared up the errors in the Demo and Stealth IVRs. Following the referenced installation instructions to reinstall Lenny on this iPBX2026 system. Then attempting to access the app through either of the IVRs results in busy tone, and no Lenny. Maybe I'm the only nerd experiencing this problem?

 

[wardmundy]

Just verified the tutorial works fine. Check the Asterisk CLI when making a call to 53669 and post results. It sounds like you forgot to clear out the previous 53669 extension which would result in the congestion message and BUSY since it attempts to call the old link:

Dial("PJSIP/701-00000000", "SIP/[email protected],,HhTtrb(func-apply-sipheaders^s^1)") in new stack
[2026-08-04 09:37:44] WARNING[817937][C-00000001]: channel.c:6280 request_channel: No channel type registered for 'SIP'
[2026-08-04 09:37:44] NOTICE[817937][C-00000001]: app_dial.c:2716 dial_exec_full: Unable to create channel of type 'SIP' (cause 66 - Channel not implemented)

What you should see if it is correctly installed:

 -- Executing [53669@from-internal:1] NoOp("PJSIP/701-00000001", "Route directly to Lenny CLI Hook") in new stack
    -- Executing [53669@from-internal:2] Goto("PJSIP/701-00000001", "app-nv-itslenny,s,1") in new stack

 

[geopeterwc]

@wardmundy ... I see EXACTLY what should appear if Lenny is installed correctly - when calling Lenny 53669 directly from an extension. But, when making the call from the "Demo IVR" (#4) it's broken.
Fortunately, very little configuration has been made so, I'm going to opt to reinstall the entire iPBX2026 and start from scratch.

 

[wardmundy]

@wardmundy ... I see EXACTLY what should appear if Lenny is installed correctly - when calling Lenny 53669 directly from an extension. But, when making the call from the "Demo IVR" (#4) it's broken.
Fortunately, very little configuration has been made so, I'm going to opt to reinstall the entire iPBX2026 and start from scratch.

The Asterisk CLI will tell you what came unglued. Beats throwing darts at the dart board.

 

[geopeterwc]

@wardmundy ... I have routinely applied the steps in "Turning Incredible PBX into a Lean, Mean Asterisk Machine" to new iPBX installations, including 2026 without issue. Is it possible that the changes from this document and implemented in the new PBX contributed to the failure of Lenny on the new box? While that documentation was written for a much earlier versions of Asterisk and Freepbx, and is six years old, applying the procedures to a new system haven't seemed to influence the performance of new systems.

 

[wardmundy]

Tutorial for Incredible PBX 2026 is here: https://nerdvittles.com/introducing-incredible-pbx-2026-for-debian-13/

You're using a tutorial that's over 6 years old. That just shy of a light-year in the VoIP space.

 

[geopeterwc]

@wardmundy No no no! I'm not using the 6-year-old tutorial to install IncrediblePBX 2026. I am using the PBX2026 for Debian tutorial you referenced to install iPBX2026. Maybe I'm foolhardy in attempting to use the 6-year-old tutorial to remove the "enchilada" stuff with the ultimate intention of having a "plain-jane" PBX with FreePBX17 and Asterisk 22, that is a system with minimal bells and whistles! Maybe we need a refresh of the old tutorial if there are parts of it that break the latest editions of iPBX?