Before I get ahead of myself with trying to configure a test setup, here is what I want to achieve:
We run two separate SIP platforms, one provides SIP trunking only and the other provides hosted PBX functionality. One of my goals is to have all customers register to the ASR and from there I can point them towards the trunking platform or hosted PBX platform depending on what they are subscribed to.
Both platforms require SIP registration. One of my goals is to allow us to offer trusted IP trunks for customers whose on premise PBX's cannot register or have issues registering. For various reasons to do with billing/credit limits/fraud prevention we can't remove this requirement on the platforms directly. The configuration guide for CUBE SP seems to suggest can do delegate registrations whereby the end customer can just point their PBX at the IP of the CUBE SP, and CUBE SP will handle registration on their behalf. It doesn't seem to say where one provides the credentials for each registration though. Have I misunderstood this feature?
For passthrough registration the configuration guide seems to suggest I need to create an SBE profile for every customer. Can I just create two global profiles tied to loopback interfaces so all customers on a SIP trunk register to the first loopback/SBE profile and all customers on hosted PBX register to the second loopback/SBE profile? All these ones would be using passthrough registration. I'd create specific profiles as required for special cases where a customer cannot support SIP registration.
Below is a link to a video showing how to analyze traceroute output in L3VPN and look up CEF forwarding and MPLS/TE/SR/SR-TE forwarding for labels through a domain. Some basic examples of traffic engineering are used but the concepts lend the...
This document summarises various health checks that can be done on a Cisco VIM pod.
Cloud sanity checks the health status of network, storage and various openstack infrastructure components like mariadb, rabbitmq etc....
The following pre-requisites are necessary for the migration from RSP440 to RSP880-LT to be successful.
Make sure that you have console access to the router.
Verify that the system is running a minimum o...
BGP flowspec in a nutshell is a feature that will allow you to receive IPv4/IPv6 traffic flow specification (source X, destination Y, protocol UDP, source port A .. etc) and actions that need to be taken on that traffic (...
While gNMI is fairly new, it's becoming more and more powerful. Its abilities to simplify network management by the use of protocol buffer files and standard definitions are enabling our customers to integrate a lot better in multi-vendor e...