Need Inbound Call Source Identification help (Voip Innovations)

[dandenson]

I'm really struggling trying to find appropriate settings. I'm using VoipInnovations. I have multiple trunks setup and I need to use call source identification to select the remote parties caller ID as how to identify the call so inbound call routing works.

So it seems that I really want the "To:" field in the sip INVITE, and it seems like that should in the "To: User Part"

but I can't get that to work no matter how many toggles I hit.

Ultimately, I want inbound rules to route based on called number from any trunk they come in on. Ideas?

 

[dandenson]

note the logs say:
Failed to identify source: several trunks matched by DID only. SI-Err Recv Req INVITE from

 

[nub]

This is in the trunk setup, this will make callerid work with voipin and 3cx.

 

[dandenson]

3cxnub, testing...

 

[dandenson]

3cxnub, what do you have in call source idenfication?

 

[jmitch11]

We use VI so I'm familiar with the setup. They have 5 IP addresses for inbound calls so you should have at least 5 trunks. Add each DID in your VI account to the DID tab on the trunk, then use your inbound rules to divert them to the correct extension. These are my inbound trunk settings.

 

[dandenson]

I'm having trouble getting the inbound rules to work with the additional DIDs.

@vizualpro do you put every DID in every trunk?

 

[nub]

 

[nub]

You have to make a new rule for each did, and each trunk.

 

[jmitch11]

I'm having trouble getting the inbound rules to work with the additional DIDs.

@vizualpro do you put every DID in every trunk?

Yes, every DID needs to go on every trunk.

 

[jmitch11]

See attached

 

[jmitch11]

Once you get all the DID numbers put on each trunk, you can go to the users extension and assign the DID to them, which will automatically create the Inbound Rules for you. Remember that rules are processed from top to bottom, so make sure you don't have a "Catch-All" at the top, move your user DIDs to the top of the list.

 

[dandenson]

This isn't working. I have 5 VI trunks setup with 2 DIDs each. The first trunk (64.136.173.31) picks up the call every time so here's that config.



Here are the associated inbound rules.


When I call each one, the routing is that assigned to the individual trunk. So VI-IN-1 points to the 91947 pre-ringer 1947 destination. EITHER number I call hits that and the Inbound routes are ignored.


This seems to make sense because the trunk says 'call source identification/contact : host part/GWHostPort' ie that came in trunk 1 so let's route it there.


Does this make sense? This is my problem, I can't get the second call to use the inbound rules, only the individual trunk rules.

 

[jmitch11]

Add a CID rule with * as a "catch-all" and put it at the top before the DID rules. Tell me if that inbound routing works.

 

[dandenson]

yes, the CID matcher works. ie, it's different from the trunk's default and the inbound routing wins.

I feel like the 'GWHostPort has to play a role here.

 

[dandenson]

weird, I deleted all but one trunk. both DIDs there, 2 DID rules to different destinations and it works.

going to add the second trunk identically and see what happens.

 

[jmitch11]

In your VI endpoint settings do you have it stripping the + and country code?

 

[dandenson]

yes, stripping both, INVITE has areacodeNPANXX, I'm entering in the DID same format.

 

[jmitch11]

Oh okay, I was starting to think it might be how the numbers is coming in. Let us know

 

[dandenson]

second trunk, identical except IP and it works. Going to add an outbound and see if that's the kink.