Marketing Company Using Twilio Cant Forward Calls to DID with Flowroute v20

[mygeeknc]

Hello! I am wanting to get a better understanding of a problem that I'm having with a client and their marketing company. I've already engaged both 3CX support and Flowroute support on this matter and both have not really given great solutions.

The problem: A client that we have is using a marketing company that has setup some "tracking" numbers which they use to advertise with and then essentially they just forward the call over to the DID we have with Flowroute. Normal calls come through just fine but for some reason, these calls don't connect.

3CX Support: I opened a case with 3CX about this issue and the solution they gave was to make a chance to the Flowroute template and then re-upload it but the solution would break SMS messaging on the system, which is something the client wants to use. Support says that the main issue is Twilio isn't sending over the request line uri in a E164 format.

Flowroute Support: Support here says that they are getting a "407 Proxy Authentication Required" when these forwarded calls comes in. They suggest that I make a change to the Request Line URI: User Part as well but I fear that this will break SMS messaging as well.

All of the forwarded calls come directly from Twilio. Has anyone seen this before or does anyone know if there is a resolution to this issue that WILL NOT break SMS messaging?

Thanks!

 

[Charles_3CX]

When calls are forwarded, the dialled number appears in the SIP Invite header's 'To User' part. Since this number is not listed under the SIP trunk's configured DIDs, the call is rejected with a Source Identification error, resulting in a 407 response sent back to the provider.

To resolve this, the SIP trunk template should be modified to match an SIP field that includes the DID entered under the trunk, such as the Request Line URI user part. We recommend confirming with FlowRoute whether the Request Line URI user part can be configured to arrive with the "+" prefix.

If so, you can safely keep your DIDs in E.164 format within 3CX to avoid disrupting other features, such as SMS functionality, while resolving the Source ID mismatch for forwarded calls.

 

[paulodagraca]

Hi,

What about getting another (extra) SIP trunk all together, only used for receiving the forwarded calls.
I guess that it should not be expensive to do, or would this setup 'break' something?

Paulo