Olivier
2018-Apr-27 10:00 UTC
[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 I still have some remaining questions. For the moment, letting registration questions aside, which of the following sentences is correct for Asterisk's PJSIP stack: 1. it would identify an incoming call only looking at From header ignoring IP settings (both IP address and port), 2. it would identify an incoming call only looking both at From header and IP settings (both IP address and port), 3. it would identify an incoming call only looking both at IP settings, ignoring From header for identification but using it for other things (setting CallerID, ...). Best regards -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180427/20c768f0/attachment.html>
Olivier
2018-Apr-27 10:14 UTC
[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" <sip:123456789 at foobar>, it would match foobar with a [foobar] endpoint, and then set CALLERID(name) to John Doe and CLAARID(num) to 123456789 2018-04-27 12:00 GMT+02:00 Olivier <oza.4h07 at gmail.com>:> 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 I still have some remaining questions. > > For the moment, letting registration questions aside, which of the > following sentences is correct for Asterisk's PJSIP stack: > > 1. it would identify an incoming call only looking at From header ignoring > IP settings (both IP address and port), > 2. it would identify an incoming call only looking both at From header and > IP settings (both IP address and port), > 3. it would identify an incoming call only looking both at IP settings, > ignoring From header for identification but using it for other things > (setting CallerID, ...). > > Best regards > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20180427/67335d03/attachment.html>
Joshua Colp
2018-Apr-27 13:01 UTC
[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 implement this services with > pjsip_wizard.conf and I'm realizing I still have some remaining questions. > > For the moment, letting registration questions aside, which of the > following sentences is correct for Asterisk's PJSIP stack: > > 1. it would identify an incoming call only looking at From header ignoring > IP settings (both IP address and port), > 2. it would identify an incoming call only looking both at From header and > IP settings (both IP address and port), > 3. it would identify an incoming call only looking both at IP settings, > ignoring From header for identification but using it for other things > (setting CallerID, ...).It depends on configuration, but ultimately it can only be identified using a single endpoint identifier - so not in combination, thus by From OR IP. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org