07-11-2018 08:02 AM - edited 03-01-2019 02:07 PM
Hello.
I cannot find any example configuration for CUCME (Express) and CUBE.
Can you please tell me where to find one?
I have an ISR4331 with CUCME and CUBE functionnalities.
Thanks. Best regards.
07-11-2018 08:10 AM
07-11-2018 08:28 AM
Hello Nipun.
Ok. When I search for occurrences of the word CUBE in that document, at page 508, I find this:Associate application CUBEDo I have to do that?
Thanks.
Best regards.
07-11-2018 08:37 AM
07-11-2018 09:00 AM
So, why is there a CUBE in that ISR4331?
isr4331# show cube status CUBE-Version : 11.1.0 SW-Version : 15.5.3.S4b, Platform ISR4331/K9 HA-Type : none Licensed-Capacity : 2
I spent the whole morning with a person working on my problem (the problem we already talked about and for which I sent you my architecture and configuration yesterday).
We couldn't find a solution but he told me:
Him: CUBE acts as a Session Border Controller... basically a SIP proxy and firewall
Me: Could it be blocking the traffic then?
Him: I wouldn't use the word blocking as much as I'd say perhaps misconfigured
The packet capture that we took earlier looked to me like the SIP phone contacted the CUBE to make an outbound call and the call was not made.
That looks like a CUBE issue.
That doesn't mean there are not other problems.
I'm certainly not an expert on these features.
@
So do I have to configure this CUBE or not?
As for the question I asked, in your answer, you are not telling me:
- either "yes run the commands",
- or "no do not run the commands because of this and that..."
I'm not an English speaking native.
Given what you wrote, I don't know what to do.
07-11-2018 09:27 AM
You see a CUBE status and version because you have "mode border-element" command under voice service voip. Check your config. Not required for CUCME.
A CUBE is a stateful proxy (B2BUA) where in the incoming and outgoing calls legs are both IP. Now with CME/ITSP SIP Trunk and SIP IP Phones, both call legs are still IP but the phone call leg in case of CME is considered line side and not trunk. For an IP to IP call flow to be considered CUBE, both call legs needs to be trunk.
So what you have is not CUBE. It is CUCME.
Now, regarding the commands, you need to see what you are configuring. Just searching for "CUBE" keyword in a document does not mean it needs to be configured for your network even if you have a CUBE. That command like I said is for LTI transoding. If you need a transcoder on your CME to fix codec mismatch calls, then yes you need that command and all the other commands in that section if you have CME 11.6 or higher. CUBE in that command is referencing a IOS API irrespective of the fact whether you have a CME or CUBE.
07-12-2018 01:11 AM - edited 07-12-2018 01:12 AM
Hello.
I am very confused.
When I received my delivery a long time ago, the only "official" papers that were in the box were two pieces of paper with this printed on them:
Right to Use Notification Product Name: FL-CUBEE-5 Production Description : Unified Border Element Enterprise License - 5 sessions Entitlement Qty: 2
That's why I thought I had to configure that CUBE.
I ran the "mode border-element" command recently when I was trying to solve my problem.
It's not easy for me to understand what you are writing but, are you saying that I do not have to configure the CUBE that is in my ISR4331?
If it is activated shall deactivate it and how?
Would a "no mode border-element" command do the trick?
Thanks and best regards.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide