[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnokii --hangup callid

From: BORBELY Zoltan
Subject: Re: gnokii --hangup callid
Date: Wed, 25 Feb 2004 00:27:00 +0100
User-agent: Mutt/1.4.1i


On Tue, Feb 24, 2004 at 10:03:55PM +0100, Gaute Amundsen wrote:
> On Monday 23 February 2004 20:27, BORBELY Zoltan wrote:
> > You have to specify the low level call id. If you run gnokii --monitor
> > you will see as "(callid: xxx".
> I now uppgraded to 0.6.0, and now it woks.

Good to hear.

> However the callid seems to increment form one call to the next, 
> but sometime reset itself, and start from 1 again.
> In other words, I can think of no simple way to hangup "the one current call".

Some historical info to make things more clear:
The low level call id is assigned by the phone, so we cannot predict
it. The API provided by the phone can be quite limited, so we added
the high level call API in the past. The high level call API uses a
different value to create an unique identifier (think about two
parallell phones which are using the same low level id).

The message sent by GN_OP_GetActiveCalls was found some months ago.
Before this we had to run gnokii --monitor when the phones dials out
or rings to catch the call setup message (there was no known way to
list the active calls). This is the reason why we cannot use the high
level call id with gnokii --hangup or gnokii --answercall.

> I guess a small perl script could fetch the callid out of the --monitor 
> output, but this seems a very slow and roundabout way to do it.
> Any other ideas?

I'd like to clean up this mess caused by mixing low level and high
level call API. The other solution is to write a little C program,
or add the missing calls to Konstanin's perl module.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]