Bug 36073 - more flexible setup to support callback and auto-answer
Summary: more flexible setup to support callback and auto-answer
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-12 09:33 UTC by Unknown
Modified: 2025-06-09 20:48 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jmartin 2001-12-12 09:28:22 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kppp
Version:           KDE 2.2.2 
Severity:          wishlist
Installed from:    Compiled From Sources
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

It's currently pretty difficult to setup kppp for auto-answer or callback:

auto-answer:
- kppp seems to require a phone number. It should offer an answer mode where it just waits for RING and then connects using ATA (or whatever the answer string is - it is already present in the modem setup)

callback:
1. the help describes a situation where the server calls back after an initial connection had been made and the client authenticated. This works fine with kppp however the kppp global modem configuration has to be changed. If only some connections use this callback scheme this won't work.
- if the server does not answer the phone call but rejects it and uses the caller-id of the caller to call back the caller (this saves the cost of the initial phone call) I don't see a way to do the setup with kppp. kppp will get a BUSY string and terminate.

One could tweak the kppp global modem configuration to accept OK instead of CONNECT for the connect string and then append a ; to the phone number but again this won't be a good solution if there are connections that don't use this scheme.

My suggestions:
1. allow for multiple modem configurations
   (even multiple per device)
2. let user choose modem configuration per
   connection
3. make specification of phone number optional
4. when no phone number is specified go right into connect script where users can do their own setup

Either 1+2 or 3+4 would solve the problems both would be best.

(Submitted via bugs.kde.org)
Comment 1 Stephan Kulow 2004-05-24 10:26:54 UTC
Replaced jmartin@csr.csc.uvic.ca with null@kde.org due to bounces by reporter
Comment 2 Christoph Cullmann 2025-06-09 20:48:31 UTC
This project is unfortunately no longer maintained.

If a new maintainer wants to step up and take care, the project is archived here:

https://invent.kde.org/unmaintained/kppp

You can just clone it in your private namespace on invent.kde.org and if you have started to work on it and fixed/implemented something get it reviewed and the project unarchived.

Sorry for the inconveniences.