asterisk users - Apr 2016 - Is it possible to have two trunks between two Asterisk boxes ?

Hello,

For lab testing, I'm trying to build two differents PJSIP trunks between
two  Asterisk 13.8.0enabled boxes.
I thought I could set up both trunks like this:
Box A/port 5060  <------ Trunk1 -----> Box B/port 5060
Box A/port 5062  <------ Trunk2 -----> Box B/port 5062

and declare trunks like this:

[foobar1]
type=endpoint
transport=simpletrans
context=from-customer
aors=foobar1
allow=!all,alaw

[foobar1]
type=identify
endpoint=foobar1
match=100.66.1.104:5060

[foobar1]
type=aor
contact=sip:100.66.1.104:5060

(In my above example,simpletrans is one of the two configured UDP
transports).


When giving this a try, the Asterisk box receiving incoming calls cannot
make a difference between calls using Trunk1 from those using Trunk2.

Before digging deeper, I would be very curious to get opinions if this is
possible in the first place.
What do you think ?

Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20160404/7a25edd6/attachment.html>

Olivier wrote:
> Hello,
>
> For lab testing, I'm trying to build two differents PJSIP trunks
between
> two  Asterisk 13.8.0enabled boxes.
> I thought I could set up both trunks like this:
> Box A/port 5060 <------ Trunk1 -----> Box B/port 5060
> Box A/port 5062 <------ Trunk2 -----> Box B/port 5062
>
> and declare trunks like this:
>
> [foobar1]
> type=endpoint
> transport=simpletrans
> context=from-customer
> aors=foobar1
> allow=!all,alaw
>
> [foobar1]
> type=identify
> endpoint=foobar1
> match=100.66.1.104:5060 <http://100.66.1.104:5060>
>
> [foobar1]
> type=aor
> contact=sip:100.66.1.104:5060 <http://100.66.1.104:5060>
You would need to use From user based matching to differentiate the two 
trunks. This can be accomplished by specifying the remote endpoint name 
to match using the from_user parameter on an endpoint. Example:

[trunk1]
type=endpoint
from_user=trunk2

When an outbound call is initiated using the trunk1 endpoint then the 
 From user will be 'trunk2'. If this is received by another chan_pjsip 
it will attempt to look for an endpoint named 'trunk2'.

This will allow you to differentiate.

-- 
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

2016-04-05 17:12 GMT+02:00 Joshua Colp <jcolp at digium.com>:
> Olivier wrote:
>
>> Hello,
>>
>> For lab testing, I'm trying to build two differents PJSIP trunks
between
>> two  Asterisk 13.8.0enabled boxes.
>> I thought I could set up both trunks like this:
>> Box A/port 5060 <------ Trunk1 -----> Box B/port 5060
>> Box A/port 5062 <------ Trunk2 -----> Box B/port 5062
>>
>> and declare trunks like this:
>>
>> [foobar1]
>> type=endpoint
>> transport=simpletrans
>> context=from-customer
>> aors=foobar1
>> allow=!all,alaw
>>
>> [foobar1]
>> type=identify
>> endpoint=foobar1
>> match=100.66.1.104:5060 <http://100.66.1.104:5060>
>>
>> [foobar1]
>> type=aor
>> contact=sip:100.66.1.104:5060 <http://100.66.1.104:5060>
>>
>
> You would need to use From user based matching to differentiate the two
> trunks. This can be accomplished by specifying the remote endpoint name to
> match using the from_user parameter on an endpoint. Example:
>
> [trunk1]
> type=endpoint
> from_user=trunk2
>
> When an outbound call is initiated using the trunk1 endpoint then the From
> user will be 'trunk2'. If this is received by another chan_pjsip it
will
> attempt to look for an endpoint named 'trunk2'.
>
> This will allow you to differentiate.
>
So basically, I then must use an other header (than From header) to pass
Caller IDs between the two boxes, no ?
Which header is then recommanded ? P-Asserted-Identity ?
Is this commonly supported and configurable by non-Asterisk PBX ?

> --
> 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
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20160405/e6a7549e/attachment.html>