On Boarding Steps (Prime VoIP Monitoring)
Go-live essentials for Prime VoIP Monitoring. Start with customer deliverables, then scopes.
NMS Prime is a CRM, BSS and OSS platform for ISPs and Telcos.
App hub: Prime VoIP Monitoring
Top customer deliverables
Prio | Deliverable | Owner (customer) |
|---|---|---|
1 | Capture point — where voipmonitor sniffs SIP/RTP | Network |
2 | DB placement — local vs dedicated sniffer host | IT |
3 | Retention — how long CDRs are kept | Legal / ops |
4 | Access — who may view CDRs | Security / care |
Scopes
# | Scope | Goal |
|---|---|---|
1 | Access & enable | Package + DB connected |
2 | Main decisions | Retention and who can view |
3 | Initial wiring | Test calls produce CDRs |
4 | Acceptance | CDR detail + phonenumber match signed off |
1. Access & enable
NMS Prime brings | Customer brings |
|---|---|
| voipmonitor host / DB credentials |
Firewall path if remote |
2. Main decisions
NMS Prime brings | Customer brings |
|---|---|
Default ~14-day cleanup | Retention policy |
3. Initial wiring
NMS Prime brings | Customer brings |
|---|---|
Match job to phonenumbers | Test numbers from OS VoIP Provisioning |
4. Acceptance
NMS Prime brings | Customer brings |
|---|---|
NOC tester |
Decide: blocking rows — DB connect, one CDR detail, one matched phonenumber.