Hi Matt,
Thank you for your explanation, it's clear to me.
Nevertheless, it doesn't help me in my use case: I'm trying to collect all
SIP callid and store that with cdr_adaptive_odbc.
The business use case is to link Asterisk CDRs with logs from our operators
via their API and our capture tool
On Mon, Sep 19, 2016 at 8:34 AM, Jonas Kellens wrote:
> Hello
>
> I can confirm that the variable DIALEDPEERNAME contains the information that
> I would expect in the variable BRIDGEPEER.
>
> But I read nowhere that DIALEDPEERNAME has replaced BRIDGEPEER as of
> Asterisk
Hello
I can confirm that the variable DIALEDPEERNAME contains the information
that I would expect in the variable BRIDGEPEER.
But I read nowhere that DIALEDPEERNAME has replaced BRIDGEPEER as of
Asterisk version 13 ?!
So if this is not the intention, then yes this is probably a bug and
Hi,
You might use DIALEDPEERNAME instead of BRIDGEPEER.
Nevertheless, I've the same issue with another BRIDGE prefix variable:
I never retrieve at one moment BRIDGEPVTCALLID variable, even if it's
documented in Asterisk wiki:
Hello
a call goes out and is answered :
[Sep 17 11:29:52] VERBOSE[23420][C-0051] app_dial.c:
SIP/myprovider-010b is making progress passing it to
SIP/mysippeer-0108
[Sep 17 11:30:05] VERBOSE[23420][C-0051] app_dial.c:
SIP/myprovider-010b answered SIP/mysippeer-0108