[asterisk-users] AstriCon Approaching, Super Earlybird Pricing Expires In 3 Days

Hey All, So one of the jobs that I get to do as head of the Asterisk project is to help inform people about the yearly conference we have about Asterisk named Astricon. For those who are not familiar with it, AstriCon is a fantastic event for anyone that is serious about Asterisk. This year,

Re: [asterisk-users] How to check modules loading order or force such order ?

On Fri, Apr 27, 2018 at 5:23 AM, Olivier wrote: > Hello, > > From [1], you can read: > "If you don't have an identify section defined, or else you have > res_pjsip_endpoint_*identifier_ip* loading *after* res_pjsip_endpoint_ > *identifier_user*, then ..." > > To remove the

Re: [asterisk-users] Question on PJSIP's endpoint section in wiki

On Fri, Apr 27, 2018, at 11:13 AM, Olivier wrote: > Hello, > > I don't know if this list is the best place to ask such question but here > it is, anyway. > > In page [1], I can read in PJSIP's endpoint section configuration reference: > identify_by username,location Way(s) for

[asterisk-users] Question on PJSIP's endpoint section in wiki

Hello, I don't know if this list is the best place to ask such question but here it is, anyway. In page [1], I can read in PJSIP's endpoint section configuration reference: identify_by username,location Way(s) for Endpoint to be identified Then clicking over identify_by text, you

Re: [asterisk-users] PJSIP global section ignored in Asterisk 13.14.1 [SOLVED]

2018-04-27 14:59 GMT+02:00 Joshua Colp : > On Fri, Apr 27, 2018, at 9:57 AM, Olivier wrote: > > Hello > > > > I've just discovered this [1] invaluable blog post (thank you very much > > Richard for writing it) and its reference to PJSIP's > > endpoint_identifier_order setting. >

Re: [asterisk-users] Explain PJSIP user matching within inbound SIP trunks

On Fri, Apr 27, 2018, at 7:00 AM, Olivier wrote: > Hello, > > I'm setting an Asterisk 13.14.1 box (Debian Stretch with packaged > Asterisk) to implement SIP trunking services ie to both trunk with carrier > trunks and IPBX trunks from various brands. > > For various reasons, I was inclined to

Re: [asterisk-users] PJSIP global section ignored in Asterisk 13.14.1

On Fri, Apr 27, 2018, at 9:57 AM, Olivier wrote: > Hello > > I've just discovered this [1] invaluable blog post (thank you very much > Richard for writing it) and its reference to PJSIP's > endpoint_identifier_order setting. > > On my Debian Stretch box powered with a packaged Asterisk 13.14.1,

Re: [asterisk-users] PJSIP global section ignored in Asterisk 13.14.1

On Fri, Apr 27, 2018, at 9:57 AM, Olivier wrote: > Hello > > I've just discovered this [1] invaluable blog post (thank you very much > Richard for writing it) and its reference to PJSIP's > endpoint_identifier_order setting. > > On my Debian Stretch box powered with a packaged Asterisk 13.14.1,

[asterisk-users] PJSIP global section ignored in Asterisk 13.14.1

Hello I've just discovered this [1] invaluable blog post (thank you very much Richard for writing it) and its reference to PJSIP's endpoint_identifier_order setting. On my Debian Stretch box powered with a packaged Asterisk 13.14.1, I edited a pjsip.conf file with the following content (and

[asterisk-users] How to check modules loading order or force such order ?

Hello, >From [1], you can read: "If you don't have an identify section defined, or else you have res_pjsip_endpoint_*identifier_ip* loading *after* res_pjsip_endpoint_ *identifier_user*, then ..." To remove the above uncertainty coming from modules loading order, how can you either or both : -

Re: [asterisk-users] Explain PJSIP user matching within inbound SIP trunks

May I add the following to my previous question: - When I wrote "only looking at From header", I meant looking at domain part of From header, leaving user part of From header for other purposes. - With a From header such as From: "John Doe" , it would match foobar with a

[asterisk-users] Explain PJSIP user matching within inbound SIP trunks

Hello, I'm setting an Asterisk 13.14.1 box (Debian Stretch with packaged Asterisk) to implement SIP trunking services ie to both trunk with carrier trunks and IPBX trunks from various brands. For various reasons, I was inclined to implement this services with pjsip_wizard.conf and I'm realizing