On Fri, Mar 1, 2019, at 5:09 PM, Brian J. Murrell wrote:
> On Fri, 2019-03-01 at 15:54 -0500, Joshua C. Colp wrote:
> >
> > That's correct. You'd either need to retrieve the line parameter from
> > the outbound registration or forge the source IP address,
>
> Can I eliminate the identify by IP
On Fri, 2019-03-01 at 15:54 -0500, Joshua C. Colp wrote:
>
> That's correct. You'd either need to retrieve the line parameter from
> the outbound registration or forge the source IP address,
Can I eliminate the identify by IP address then, given that my ITSP is
supporting the line parameter? Or
On Fri, Mar 1, 2019, at 4:51 PM, Brian J. Murrell wrote:
> On Fri, 2019-03-01 at 15:41 -0500, Joshua C. Colp wrote:
> >
> > I don't understand what you mean. Your ITSP has stated that they
> > don't want you to do authentication with them, so you can't.
>
> They are implying, as I am
On Fri, 2019-03-01 at 15:41 -0500, Joshua C. Colp wrote:
>
> I don't understand what you mean. Your ITSP has stated that they
> don't want you to do authentication with them, so you can't.
They are implying, as I am understanding them, that somehow SIP packets
they send me shouldn't need to be
On Fri, Mar 1, 2019, at 4:33 PM, Brian J. Murrell wrote:
> On Fri, 2019-03-01 at 14:15 -0500, Joshua C. Colp wrote:
> > you can try line functionality on the outbound registration which
> > may or may not work[2] (requires the upstream to adhere to the RFC,
> > which not all do).
>
> My provider
On Fri, 2019-03-01 at 14:15 -0500, Joshua C. Colp wrote:
> you can try line functionality on the outbound registration which
> may or may not work[2] (requires the upstream to adhere to the RFC,
> which not all do).
My provider seems to implement this.
However even with the line=... in the:
SIP
On Fri, Mar 1, 2019, at 3:56 PM, Brian J. Murrell wrote:
> On Fri, 2019-03-01 at 14:15 -0500, Joshua C. Colp wrote:
>
> [itsp-endpoint](!)
> type=endpoint
> transport=transport-udp
> context=from-itsp
> message_context=messages
> disallow=all
> allow=ulaw
> from_user=XXX
>
On Fri, 2019-03-01 at 14:15 -0500, Joshua C. Colp wrote:
>
> You either configure IP based matching using an identify section[1]
That's what I did:
[itsp]
type=registration
transport=transport-udp
outbound_auth=itsp-auth
server_uri=sip:pop1.itsp.example.com
On Fri, Mar 1, 2019, at 3:05 PM, Brian J. Murrell wrote:
> I'm being told by my ITSP that my Asterisk shouldn't be challenging
> their system to authenticate (i.e. a 401 response) when they send me a
> SIP MESSAGE (or I suppose a SIP INVITE for that matter).
>
> But I'm not sure what a pjsip.conf
I'm being told by my ITSP that my Asterisk shouldn't be challenging
their system to authenticate (i.e. a 401 response) when they send me a
SIP MESSAGE (or I suppose a SIP INVITE for that matter).
But I'm not sure what a pjsip.conf configuration for that looks like.
How does one associate an
10 matches
Mail list logo
