Displaying 2 results from an estimated 2 matches for "calling_num".
2019 Apr 05
2
pjsip endoint woes
...202-aor)
##############
From the pjsip logging:
<--- Received SIP request (798 bytes) from UDP:<obi_ip>:5062 --->
INVITE sip:<gv_num>@<ast_ip>:5060 SIP/2.0
Call-ID: bb384ee02eab7054 at 10.10.11.181
Content-Length: 270
CSeq: 8001 INVITE
From: <sip:+1<calling_num>@<ast_ip>>;tag=SP377bfeeed75f36b8e
Max-Forwards: 70
To: <sip:<calling_num>@<ast_ip>>
Via: SIP/2.0/UDP <obi_ip>:5062;branch=z9hG4bK-fec7c7c4;rport
User-Agent: OBIHAI/OBi202-3.2.2.5921
Contact: <sip:gv-voice@<obi_ip>:5062>
Expires: 60
Supported: replace...
2019 Apr 08
2
pjsip endoint woes
...st (798 bytes) from UDP:<obi_ip>:5062 --->
> >
> > INVITE sip:<gv_num>@<ast_ip>:5060 SIP/2.0
> >
> > Call-ID: bb384ee02eab7054 at 10.10.11.181
> >
> > Content-Length: 270
> >
> > CSeq: 8001 INVITE
> > From: <sip:+1<calling_num>@<ast_ip>>;tag=SP377bfeeed75f36b8e
> > Max-Forwards: 70
> > To: <sip:<calling_num>@<ast_ip>>
> > Via: SIP/2.0/UDP <obi_ip>:5062;branch=z9hG4bK-fec7c7c4;rport
> > User-Agent: OBIHAI/OBi202-3.2.2.5921
> > Contact: <sip:gv-voice@<...