dual SIP and dual PRI

[Anonymous]

I have a setup where I have a customer who has dual PRI's.  One is used for outbound calling and the other is used for incoming DID's.  I am thinking that the best way to set this up is to assign one SIP trunk to the outgoing calls PRI and then register all of the DID's in the TA908e and tie those to the PRI that is used for incoming calls.  Am I on the right track of how this should be setup?  I found a guide online on how to setup a SIP trunk to two PRI's, but not sure how you would do it with separate SIP trunks and two PRI's.

Jeff

[jayh]

Unless there is a need for two SIP trunks, no reason to not use one for both directions.  They could, of course, do the same with their PRIs.

You could use two SIP trunks one inbound and one outbound if you need to.  Assign the outbound one to a grouped-trunk with a match-all pattern.  The other has no grouped-trunk for inbound.  Then the inbound PRI has a grouped-trunk with the PBX DIDs and the outbound doesn't.

You should probably use SABR to avoid hairpinning SIP calls from one trunk to another (unless that is the goal).

But for me unless there's a business reason, one trunk will do.

Typically we see this type of setup on a legacy customer that has a "local" and a "toll" PRI from back in the old days.  You may find that the PRIs aren't strictly inbound and outbound.

Typically the "local" PRI is inbound-mostly but 911 and toll-free and maybe 7-digit local calls use it outbound. 

Typically the "toll" PRI is outbound-mostly but if the customer has dedicated toll-free numbers these may be inbound on it.

These days it's easier to just give them two PRIs that both do everything and a single SIP trunk.  Then they have 46 talk-paths that can be a mix of anything, in or out, local or toll.

The fun ones are when the PBX is ancient, nobody knows anything about it, and everyone is afraid to touch it because the only vendor is miles away and charges a small fortune.  Sometimes you just need to wait for it to die and sell them Polycoms. 

[Anonymous]

That is what this situation is.  Customer has a legacy Avaya PBX w/ 2 PRI's....one handles inbound DID's and one handles outgoing LD calls and incoming 800 calls.  They are migrating from their old provider to us, and the only way for me to deliver them PRI's at this location is via SIP trunking.  The best way I can think of doing this, is setting up one SIP trunk for their outgoing calls (local and LD) and assign their published number to that SIP trunk.  Then setup all of their DID numbers (100 of them) as SIP trunks and tie them to the second PRI to inbound calling. 

[jayh · Accepted solution]

jkesting wrote:

That is what this situation is.  Customer has a legacy Avaya PBX w/ 2 PRI's....one handles inbound DID's and one handles outgoing LD calls and incoming 800 calls.  They are migrating from their old provider to us, and the only way for me to deliver them PRI's at this location is via SIP trunking.  The best way I can think of doing this, is setting up one SIP trunk for their outgoing calls (local and LD) and assign their published number to that SIP trunk.  Then setup all of their DID numbers (100 of them) as SIP trunks and tie them to the second PRI to inbound calling.

That's fairly common, but you can easily do it with only one SIP trunk.

Create a grouped-trunk for the SIP trunk with the standard local, LD, international, N11 patterns.

Create two ISDN trunks and put one PRI in each, and bind each to a grouped-trunk, call them LOCAL and LD.

On the local grouped-trunk accept all of their local DIDs.

On the LD grouped-trunk accept all of their 800 numbers.

Point both their local and 800 numbers down the one SIP trunk, and accept anything outbound from them on it.

[Anonymous]

Hello,

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

Geoff