PIAF middleman, want to reverse DID & CallerId on PRI

[hmonroe]

I have my PIAF in between a Merlin Legend and the outside world. The phone company PRI is coming into PIAF and another PRI from my Merlin Legend is attached to PIAF (PIAF is between the phone company and the Legend).

Phone Co. <--PRI--> PIAF <--PRI--> Merlin Legend Phones

This allows us to continue to use our old deskphones, but take advantage of some PIAF features.

I wrote a couple "Custom Destinations" to transfer calls between the PRIs. It works fine, BUT for outgoing calls from the Legend:
1. The DID is now the number I'm calling
2. The CallerId is seen as the DID.
3. Additionally the CDR is incorrect, showing my main number as the number dialed

In Zapata.conf I put in
signalling=pri_net

Is there a way to tell a PRI port to reverse or swap the DID & Caller ID?

 

[merk]

I did a similiar setup before about 3 years ago.

Phone Company PRI|\
Bandwidth SIP |/both went to Elastix at the time -> PRI -> Panasonic System

Custom Extensions I had was
[panasonic]
exten => _X.,1,Dial(zap/g0/${EXTEN})
exten => _X.,2,Hangup
exten => _X.,102,Playback(all-circuits-busy-now&pls-try-call-later)
exten => _X.,103,hangup
exten => _X.,h,hangup

Can you post your custom extensions?

I am trying to look for the Zapata config file but yea i remember it to be pri_net on the pri connecting to the Panasonic.

 

[blanchae]

I believe the term for putting PiaF in the middle like that is called a tandem PBX.

One trick that I've done is instead of context=from-pstn, I've used context=from-internal for the trunk to the legacy PBX.

This way PiaF uses the outbound routes to route the legacy extension's calls just as if they were an extension in PiaF. Otherwise if you use context=from-pstn, it treats the legacy PBX extensions to the PiaF inbound rules.