search for: local_uri

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\\\" <...

...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: "y...

...5, 2023 at 12:50 PM TTT <lists at telium.io <mailto:lists at telium.io> > wrote: 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\\\" <...

...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" ,...

The following AMI command works well for all of the information I want: action: Getvar actionid: act1 channel: PJSIP/Twilio-NA-W-3-In-00000028 Variable: CHANNEL(pjsip,XXXX) Where XXXX can be one of the many available items. However, when I create a call from A to B, all of the items return properly except: local_addr and remote_addr. More specifically, they return correctly for the A leg (that

On Mon, Jun 26, 2023 at 4:35 PM TTT <lists at telium.io> wrote: > I think that’s getting me close. I’m trying to get (or recreate) the FROM > and TO lines of the header, from a system running PJSIP. I think if I use > CHANNEL to get local_uri and local_tag I can recreate a FROM line like: > > *FROM=<URI>;tag=TAG* > > > > And if I use CHANNEL to get remote_uri and remote_tag I can recreate a > FROM line like: > > *TO=<URI>;tag=TAG* > > > > Would it be correct to assume that with this inf...

I think that’s getting me close. I’m trying to get (or recreate) the FROM and TO lines of the header, from a system running PJSIP. I think if I use CHANNEL to get local_uri and local_tag I can recreate a FROM line like: FROM=<URI>;tag=TAG And if I use CHANNEL to get remote_uri and remote_tag I can recreate a FROM line like: TO=<URI>;tag=TAG Would it be correct to assume that with this info (and ip:port info) I should be able to send a UDP SIP mes...

On Mon, Jun 26, 2023 at 4:04 PM TTT <lists at telium.io> wrote: > It looks like if I call Getvar and pass PJSIP_HEADERS() I can get the > entire SIP header for a channel. I also read (on stackoverflow) that the > PJSIP_HEADER function will only return the headers from the INVITE of the > *inbound* channel. > > > > If that’s correct, how would I get the headers from