two no call source identification trunks? (VI)

[dandenson]

Hi, I've got a small struggle. I have some t.38 faxing at a site and with VoIP Innovations, I need to have a separate trunk from these on their T.38 rate deck. The problem is that you can't have two trunks with call source identification turned off without some tweaks to make calls go through. VI lets me set up a second endpoint (mapping to my PBX IP) with a different set of IP's, but this call source identification thing is what's getting me.

so, anyone have an idea how I can setup 2 VI trunks and have calls complete?

 

[dandenson]

No ideas here?

 

[Evolute IT]

Are you gonna use an ATA for faxing? Or just the virtual fax to email?

 

[dandenson]

ATA. I think I've got it going. In testing I'm not getting errors for call source identification with two VI trunks (different IPs) but this is testing day so I'll be following it closely.

I really don't know what 3CX is looking at to differentiate these things, I come from asterisk which tracks the src address on the inbound call so doesn't really behave the same.

 

[Evolute IT]

ATA. I think I've got it going. In testing I'm not getting errors for call source identification with two VI trunks (different IPs) but this is testing day so I'll be following it closely.

I really don't know what 3CX is looking at to differentiate these things, I come from asterisk which tracks the src address on the inbound call so doesn't really behave the same.

If the second trunk is only for the ATA, just connect the ATA to your trunk and bypass 3CX.

 

[dandenson]

I have considered that, but there are multiple ATAs used for outbound faxing and with VI I only have 2 'sets' of IP ranges so I can only do this with a single ATA.

 

[Evolute IT]

I have considered that, but there are multiple ATAs used for outbound faxing and with VI I only have 2 'sets' of IP ranges so I can only do this with a single ATA.

Why multiple ATAs? For the same DID/fax? You'll have issues my friend.

And keep in mind that the provider only sees the public IP. If the ATAs are all in the same network, then they technically report only 1 IP for all of them (which is where you get issues, can't filter where the fax is going when coming into the network).

 

[dandenson]

There are multiple fax numbers and multiple ATAs. This is why doing the direct NAT to an ATA wont work and I need to put 3CX in the middle.

The perceived problem here is multiple trunks with call source identification turned off confusing 3CX which I experienced converting from bandwidth.com to voip innovations. Couldn't have both trunks at the same time or calls wouldn't complete.

 

[dandenson]

oh, and VI doesn't mix their standard rate deck with t.38, so I need one trunk for voice and one trunk for t.38 fax.

 

[Evolute IT]

oh, and VI doesn't mix their standard rate deck with t.38, so I need one trunk for voice and one trunk for t.38 fax.

You should be able to filter call source by using DID and gateway address tho.

 

[dandenson]

VI isn't in the media path so setting this makes calls fail. They also send calls from multiple proxies so I have to leave call source unchecked else I get failed calls. Otherwise I have to put in 4 different trunks which makes inbound rules setup a nightmare.

 

[Evolute IT]

VI isn't in the media path so setting this makes calls fail. They also send calls from multiple proxies so I have to leave call source unchecked else I get failed calls. Otherwise I have to put in 4 different trunks which makes inbound rules setup a nightmare.

Hmm, odd. @JohnS_3CX any ideas?

 

[JohnS_3CX]

I would start from here if you haven't read this already: https://www.3cx.com/docs/multi-account-sip-trunks/

Do you have unique Auth ID or is this the same trunk but built twice?

 

[dandenson]

@JohnS_3CX IP auth on voip innovations.