Jaze ISP Manager
Where Jaze sits in an ISP network.
Jaze runs alongside the network you already operate. It does not sit in the traffic path: it authenticates against your BRAS, collects what your edge already exports, and provisions the devices at the subscriber end.
Reference architecture
Five layers, and the protocols between them.
Each connector carries the protocol used between the tiers either side of it.
Subscriber premises
CPE
Router or ONT
GPON ONT
TR-069 managed
Subscriber devices
Behind the CPE
Access and aggregation
OLT
Fibre access
Aggregation switches
Backhaul
Wireless controllers
Cisco, Aruba, Ruckus, Cambium
Edge
Cisco ASR
1000 and 9000 series
Juniper MX
MX series
Huawei NE
NE and ME series
ZTE
BNG
MikroTik
BRAS
Jaze ISP Manager
AAA
RADIUS engine, CoA
Billing
Triple-play billing and payments
CRM
Leads, helpdesk and inventory
IPFIX
Flow collection and logs
TR-069
Auto-configuration server
External systems
Payment gateways
Indian and international
Messaging
SMS, email, WhatsApp
OTT and IPTV
Bundled services
Accounting
Tally, QuickBooks
Backup storage
S3, GCS, Azure, MinIO
Traffic paths
What travels where.
Authentication path
Session to policy
- The BRAS forwards a RADIUS Access-Request to the Jaze AAA engine
- Jaze resolves the subscriber's plan and returns vendor-specific attributes
- Accounting is kept against the session for its lifetime
- Change of Authorization applies policy changes or disconnects mid-session
Provisioning path
Platform to device
- The CPE reaches the TR-069 auto-configuration server on first connect
- Configuration is applied against the subscriber's plan profile
- Configuration changes are pushed remotely to deployed devices
- Tx and Rx optical power is reported back to the platform
Logging path
Network to searchable record
- Edge devices export IPFIX or NetFlow v9 records to Jaze
- NAT translations are logged, and source NAT logs can go over FTP compressed
- Records are stored for query through the log interface
- SNMP supplies per-user and per-interface traffic statistics
Deployment
Cloud or on your own infrastructure.
Cloud
Hosted and managed by Jaze
- Accessed at isp.jazenetworks.com
- No infrastructure to run for the platform itself
- Same module set as the on-premise deployment
On-premise
Running on your own infrastructure
- Accessed on the application server over HTTPS on port 8000
- Deployed within your own network
- Same module set as the cloud deployment
Map this against your own network.
Bring your topology, vendor mix and deployment preference and we will walk through the fit.