asterisk users - Jul 2023 - Getvar of CHANNEL not working for a couple of items

On Tue, Jul 4, 2023 at 7:52 PM TTT <lists at telium.io> wrote:
> Building on my last message, I am trying to get CHANNEL data using getvar
> (through the AMI).  And although I'm getting responses, some  values
> returned seem illogical.  For example, phone 111 calls phone 222 via the
> PBX.  Here's the data I get back
>
>
>
>
>
>   Channel A: "1688509741.112" , name: 
"PJSIP/111-00000064" , is
> originator:  Y , call-Id:  "u.l6kcou25cax60 at mydomain.com" ,
local_uri:  "<
> sip:222 at mydomain.com;user=phone>" , local_tag:
> "1734d973-c4da-4ae8-a37d-5f7065f1fe54" , local_addr: 
"172.31.253.4:5060"
> , remote_uri:  "\\\"TestPhone x111\\\" <sip:111 at
mydomain.com>" ,
> remote_tag:  "yinue4v5ufa4" , remote_addr: 
"172.31.253.20:5060"
>
>
>
>
>
>   Channel B: "1688509741.113" , name: 
"PJSIP/222-00000065" , is
> originator:  N , call-Id:  "1f104544-fc1a-4414-ba74-68c526e294de"
,
> local_uri:  "\\\"TestPhone\\\" <sip:111 at
172.31.253.4>" , local_tag:
> "ac5eeb59-f559-4bb7-a3c2-170ca7f05f8b" , local_addr: 
"" , remote_uri:  "<
> sip:222 at 172.31.253.20;line=46922>" , remote_tag: 
"klwqxe1fvt5wk" ,
> remote_addr:  ""
>
>
>
> And here's what seems strange:
>
> Channel A's local_uri looks like Channel B's uri
>
> Channel A's remote_uri looks like channel A's uri
>
> Channel B's local_uri looks like channel A's uri
>
> Channel B's remote_uri looks like channel B;s uri
>
These aren't strange. They look alike because of callerid and target dialed
information. They are still independent call legs.

> Channel B's local_addr is blank
>
> Channel B's remote_addr is blank
>
I don't know why they're blank.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230705/86bedd1f/attachment.html>

Channel A: "1688509741.112" , name:  "PJSIP/111-00000064" ,
is originator:  Y , call-Id:  "u.l6kcou25cax60 at mydomain.com
<mailto:u.l6kcou25cax60 at mydomain.com> " , local_uri: 
"<sip:222 at mydomain.com <mailto:sip%3A222 at mydomain.com>
;user=phone>" , local_tag: 
"1734d973-c4da-4ae8-a37d-5f7065f1fe54" , local_addr: 
"172.31.253.4:5060 <http://172.31.253.4:5060> " , remote_uri: 
"\\\"TestPhone x111\\\" <sip:111 at mydomain.com
<mailto:sip%3A111 at mydomain.com> >" , remote_tag: 
"yinue4v5ufa4" , remote_addr:  "172.31.253.20:5060
<http://172.31.253.20:5060> "

 

 

  Channel B: "1688509741.113" , name:  "PJSIP/222-00000065"
, is originator:  N , call-Id:  "1f104544-fc1a-4414-ba74-68c526e294de"
, local_uri:  "\\\"TestPhone\\\" <sip:111 at 172.31.253.4
<mailto:sip%3A111 at 172.31.253.4> >" , local_tag: 
"ac5eeb59-f559-4bb7-a3c2-170ca7f05f8b" , local_addr:  "" ,
remote_uri:  "<sip:222 at 172.31.253.20 <mailto:sip%3A222 at
172.31.253.20> ;line=46922>" , remote_tag:  "klwqxe1fvt5wk"
, remote_addr:  ""

 

And here's what seems strange:

Channel A's local_uri looks like Channel B's uri

Channel A's remote_uri looks like channel A's uri

Channel B's local_uri looks like channel A's uri

Channel B's remote_uri looks like channel B;s uri

 

These aren't strange. They look alike because of callerid and target dialed
information. They are still independent call legs.

 

 

I’m having trouble understanding your explanation (googling just led me to
generic callerid and target info).  I thought a phone’s local_uri would be how
to reach that phone (not the other party), and vice versa for the remote_uri. 
If the above URI info is correct then I must misunderstand their meaning.  Could
you provide more explanation on how to interpret them (why they seems reversed
to me), or a link?

 

I assumed the remote & local URI where equivalent to the to & from lines
(respectively) in the invite…

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20230705/c36f03e7/attachment.html>