cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
237
Views
1
Helpful
4
Replies

Configuration Assistance Multi Tenant CUBE

glenthms
Level 1
Level 1

We need to convert off of an existing PRI to a SIP service.  Im relatively new to the configuration so be gentle on me.  Our SIP trunk to our hosted service is working fine (tenant 200).  I've built a 2nd tenant 300 with the new SIP service based off the following information that was provided to us.  Keep in mind I've replaced sensitive information in the output and information provided that isn't usable in the real world so look over that if you can.

Service Provider gave us the following:

Domain/realm: siprealm.cm
SIP proxy/signaling IP: 172.22.97.133
Media: 172.22.97.134

SIP Trunk name: SIP_TRUNK_IOT
Authentication User Name: 5552795060
Authentication Password: ConnectToMe123

 

The configuration attached is what I've come up with so far however Im stuck at the moment and want to be able to test this.  

I need help validating my configuration as we are getting the below errors when we are testing.  Again ignore the 555 unreal number I only masking it due to sensitive info.  This was a call I made from behind the router on a phone out to the SIP provider to someone's cell phone.  

 

Jul 10 18:33:25.127 ADT: //53173/DF89A55585C6/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden
From: "user1caller"<sip:5552795060@10.50.63.82>;tag=303DEEFB-5B6
To: <sip:5557531297@172.22.97.133>;tag=125d0e03-66192099-aef9bb-7f15dcdec9d8-876116ac-13c4-764
Call-ID: DF8ADDA5-3E3A11EF-85CCABF0-7E944F91@10.50.63.82
CSeq: 101 INVITE
Warning: 399 172.22.97.133:5060 "Registration Cache Entry Not Found"
Reason: SIP;cause=403;text="Subsystem Id: ICALLLEG Cause Code: Forbidden_403"
Via: SIP/2.0/UDP 10.50.63.82:5060;branch=z9hG4bK5C76204C
Content-Length: 0

 

 

4 Replies 4

From what I can tell you don’t have an outbound dial peer that uses tenant 300 and you have not turned on the Cube functionality in your router. Please have a look at this document for how to configure a Cisco router to act as an SBC using the Cube functionality. Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards 



Response Signature


Thanks for the reply, however your document says for 17.6 and onwards I am on 17.3.  Will it still apply?   

UPDATE, found the doc that applies to my version.  Can you tell me why you think that CUBE is not on?

Because "mode border-element" is missing under "voice service voip"

Like @b.winter wrote you're missing the command “mode border-element" under the voice service voip section. Without that you’re not having the Cube feature turned on.



Response Signature