Webex Calling - Inbound calling - On-premise trunk to Webex extension

[blair-keeley]

Hi,

I have configured an SBC as a managed on-premise trunk. Everything works perfectly except calling inbound to Webex extensions. There are some Webex users that have extension numbers only, the SBC has another PBX connected and the idea is those PBX users can call Webex users by the extension number to have desk to desk calling.

If I use the Verify Call Routing check for the SBC trunk to call to a users extension number it does show as successfully routed to the user but when a SIP call arrives from the trunk to the extension number Webex Calling responds with 604 Does Not Exist Anywhere. Calling to a users full phone number works fine.

Is this a limitation? are inbound calls from a peered SBC only possible to a users full active phone number and it is not possible to call a non DID user who has an extension number only?

[Guillermo_PY]

How does this story continue? I am in the same situation

[blair-keeley]

My final findings on this were.

If the calling number in the From or Diversion header is less than 6 digits the call was allowed.

If the calling number in the From or Diversion header matches the trunk dial plan the call was allowed.

Makes sense and allowed the integration I needed to test.

[Guillermo_PY]

I don't understand when you say: 

If the calling number in the From or Diversion header matches the trunk dial plan the call was allowed.

Could you please explain it to me?

[blair-keeley]

Yes, so that is the scenario where the call has been forwarded or blind transferred by the system on the opposite side of the trunk to Webex.

ie A user on a PBX has a PSTN call and blind transfers across the calling trunk to a Webex user, the From will be the original caller and the Diversion header will be the PBX user number.
The original caller may not match a dial plan but because the Diversion header matches as less than 6 digits or the dial plan the call is successful and the Webex user will receive the call as forwarded by the PBX user.

[Guillermo_PY]

Excellent @blair-keeley  

[Alan Batres]

Hi Guillermo! For me the solution is to modify the calling party transform mask to XXXX, you need adjust the wildcard to your extension lenght plan

[Guillermo_PY]

Excellent, I made that and it works. But what happens with the calling real number?

[blair-keeley]

I have found some info in documents, looks like the from component for the invite to WxC should match the dial plan configured to call the other PBX and then the call will be seen as a same premise call and not receive 604. I was sending long number E164 cli with the outbound calls from the other party PBX side. Going down that path and will log support issue if needed. Cheers for feedback.

[johnsnow53334]

The issue you're facing with Webex Calling's response of "604 Does Not Exist Anywhere" when trying to inbound calls from an SBC trunk to users with extension numbers only could be due to a limitation in Webex Calling's handling of such scenarios. Inbound calls to Webex users may require the use of full active phone numbers rather than extension numbers alone. It's recommended to check Webex Calling's documentation or contact their support for specific guidance on handling inbound calls to users with extension numbers only.

The Capitec branch code is 470010, and with this code, you can make quick money transfers while the corresponding banks can quickly identify it.

[blair-keeley]

Thankyou @Vaijanath Sonvane for the response.

This is a lab setup with an AudioCodes SBC and a FreeSWITCH instance as the other PBX side of the SBC.

Outbound 78xxx to FreeSWITCH (working)

Example WebEx user has phone number and extension, this user is in the same Webex location as the trunk

I have these routes set in audiocodes to route to WxC

Call +19155550101 works.

Call to 1004 or 881004 receives Does Not Exist Anywhere

Is there a particular requirement for an invite to an extension number to be matched over an invite to the full phone number?

Here is the verify routing check which suggests the routing should work from the trunk so possibly the invite is not being associated with this trunk?

[Vaijanath Sonvane]

Hi @blair-keeley

You can do extension to extension calls from PBX to WxC and vice version without any issue. You need to perform dial plan manipulation on Local Gateway. Can you post your SBC configuration and your dial pattern from PBX to WxC and vice versa. 

[Alan Batres]

What do you need to manipulate in order to reach an extension only user?