callback stopped working after IOS upgrade

~ After IOS upgrade from 12.2(27) to 12.2(46) callback stopped working ~ with the following message: ~ ~ 1951: TTY38 Callback PPP process creation ~ 1952: TTY38 Callback process initiated, user: dialstring 9427624 ~ 1953: TTY38 Callback process before disconnect- modemcheck status=20090081 ~ ~ Platform: cisco 2621, NM-8A/DM, modem firmware source: IOS. ~ ~ Any ideas what this message means and how to fix the problem? ~ ~ Downgrading to 12.2(27) does fix the problem with callback (this means ~ the callback configuration is correct), but a downgrade is not desirable ~ as 12.2(27) has other bugs.

This looks to be CSCsc43163, fixed in 12.4(09)T04 12.4(11)T02 12.4(13.12)T. If you need the fix in 12.2M, then I'd recommend opening a TAC case and getting the DEs to patch in the fix.

Aaron

CSCsc43163 is first found in 12.4T How come that I was hit in 12.2(46) ?

Thank you for your input.

~ > ~ After IOS upgrade from 12.2(27) to 12.2(46) callback stopped working ~ > ~ with the following message: ~ > ~ ~ > ~ 1951: TTY38 Callback PPP process creation ~ > ~ 1952: TTY38 Callback process initiated, user: dialstring 9427624 ~ > ~ 1953: TTY38 Callback process before disconnect- modemcheck status=20090081 ~ > ~ ~ > ~ Platform: cisco 2621, NM-8A/DM, modem firmware source: IOS. ~ > ~ ~ > ~ Any ideas what this message means and how to fix the problem? ~ > ~ ~ > ~ Downgrading to 12.2(27) does fix the problem with callback (this means ~ > ~ the callback configuration is correct), but a downgrade is not desirable ~ > ~ as 12.2(27) has other bugs. ~ ~ > This looks to be CSCsc43163, fixed in 12.4(09)T04 12.4(11)T02 12.4(13.12)T. ~ > If you need the fix in 12.2M, then I'd recommend opening a TAC case and getting ~ > the DEs to patch in the fix. ~ ~ CSCsc43163 is first found in 12.4T ~ How come that I was hit in 12.2(46) ?

My guess is that whatever bugfix it was that caused CSCsc43163 to appear in 12.4T finally got committed to 12.2M some time between 12.2(27) and 12.2(46).

Regards,

Aaron

Do you mean there is absolutely no luck for me trying anything between

No, it means that the same change was made to 12.2 between 12.2(27) and

Releases in any of the trains before that point will be ok. There isn't an unbroken line of descent from 12.2(49) to 12.4(09)T04. it's more complicated than that.

See White Paper: Cisco IOS Reference Guide