Hybrid Calling Outbound Calls media

[Support Albakom]

Hi,

we have an exisiting Expressway-C-E pair for MRA. We configured it additional with the hybrid callling zones,search rules and so on.

We configured complete webex hybrid calling with the cloud, cucm and expressway.

I call from a webex teams app inbound to a user on CUCM. Answer the call with the desk phone. Call connected, video and audio fine.

Make an outbound call from deskphone to a DN and a associated directory URI.

SIP route pattern is targeted to a non encrypted SIP trunk to Expressway C (the default zones added by expc with CUCM).

Call is established and immediatly end after connect. I see on Expressway C, that the call comes via the Expressway MRA trunk (no TLS encryption). 

Call history show me this:

Session 1

Status	Replaced
Media routed	True
Call routed	True
Participant 1	Leg 1
Participant 2	Leg 2
Bandwidth allocated	0 kbps
Bandwidth requested	0 kbps

Session 2

Status	Completed
Media routed	False
Call routed	True
Participant 1	Leg 1
Participant 2	Leg 3
Bandwidth allocated	384 kbps
Bandwidth requested	384 kbps
Route	CEtcp-CUCM10.albakom.de -> Zone003ToTraversalSZ -> TraversalSubZone -> Zone009ToTraversalSZ -> Webex Hybrid traversal client

Maybe the wrong zone?

If I set the routing on the SIP Route Pattern on CUCM to a TLS encrypted SIP trunk to Expressway neighbor zone, no uri dilaing is possible. get fast busy. Trunk and zone are active.

Somebody can give some hints? First, dialing uri via TLS seems not work. 2nd, media seems not transport via expressway?

[akshay techimply]

Hello,

I have a question that can we integrate it with the hybrid cloud telephony & IVR software?

[nithyagupta]

i have doubt and also have question that can i use this software at our online store website.

[rembes99]

It seems you're experiencing call drops when making outbound URI calls from desk phones through Expressway-C. This issue may stem from misrouted calls via the Expressway MRA trunk instead of the intended path. To address this:

1. SIP Trunk Configuration: Ensure your SIP route patterns in CUCM direct URI calls to a TLS-encrypted SIP trunk targeting the correct Expressway-C neighbor zone. Misconfigurations can lead to routing issues.

2. Zone and Search Rules: Verify that Expressway-C's zones and search rules are correctly set up to handle URI dialing. Proper configuration ensures calls are routed through the appropriate zones.

   Cisco

3. Media Encryption Settings: Align media encryption settings between CUCM and Expressway-C. Mismatched settings can cause call drops.

4. Firewall and Certificates: Confirm that necessary ports are open and that valid certificates are installed on both CUCM and Expressway-C. This is crucial for establishing secure TLS connections.

   https://dekom.com

By reviewing and correcting these configurations, you should resolve the call drop issues during outbound URI dialing.

Priyanka Patil

https://sleekbill.in

[sleekbill]

Here are some key areas to check:

1. SIP Trunk Configuration:

   • Ensure that your non-TLS SIP trunk to Expressway-C is properly handling URI dialing.
   • If TLS is required, verify that the certificates are correctly exchanged between CUCM and Expressway.

2. Expressway Zones & Routing:

   • Your call is routing through the MRA traversal client, which suggests that Expressway might be treating it as an external call.
   • Check if Expressway C has the correct search rules for Hybrid Calling vs. MRA.

3. Media & Bandwidth Issues:

   • In Session 1, bandwidth is 0 kbps, meaning media isn’t flowing. This could be due to firewall/NAT traversal issues.
   • Make sure ICE and MRA settings are correct, as Expressway must facilitate media traversal correctly.

4. TLS Issues with URI Dialing:

   • If URI dialing fails over a TLS trunk, verify that CUCM SIP Route Patterns support TLS and that Expressway recognizes it.
   • Ensure that Expressway’s neighbor zone to CUCM supports secure SIP signaling.

Since this issue involves hybrid calling and Expressway traversal, it's crucial to check logs on both CUCM and Expressway to identify SIP 4xx or 5xx errors.

Prashant Nikose

https://www.billingsoftware.in