IPTV System Configurations - Edited
IPTV System Configurations - Edited
Current Configuration:
---- Single option to change the STB with 0 charges as the invoice for the STB change as the
invoice for the STB change cannot be generated from the IPTV system.
---- Multiple options to change the STB with various charges option according to the
warranty of the STB box in which the warranty period is validated in the IPTV System
i. If the CSR applies for 0 invoice for the STB within warranty period AND if the STB is
within warranty in the IPTV side, then the STB is changed with 0 invoice in IPTV side
and the old invoice is attached with the new STB for the same customer in IPTV
side and the process is completed successfully in CRM system as well.
ii. If the CSR applies for 0 invoices for the STB within warranty period BUT if the STB is
not within warranty in the IPTV side, then the STB is change is failed in CRM the
process is not completed successfully in CRM system as well with no pending
order.
iii. If the CSR applies for charged invoices for the STB not within warranty period AND if
the STB is not within warranty in the IPTV side, then STB change with charged
invoice in IPTV side is successful and the process is completed successfully in CRM
system as well.
iv. If the CSR applies for charged invoices for the STB not within warranty period BUT if
the STB is within warranty in the IPTV side, change is failed in CRM the process is
not completed successfully in CRM system as well with no pending order.
v. In cases if the warranty is already expired and need to change the STB with 0
charges then it can be done only by ADMIN user.
2. Installation VAS Unsubscription:
Current Configuration:
---- Installation VAS can be cancelled anytime from the CRM and related STB invoice in the
IPTV side will also be cancelled.
Current Configuration:
---- Operations like New user creation, STB assignment, STB replacement, Package removal,
Installation VAS addition and Installation VAS removal will be have PENDING ORDER in the
CRM system if there are some issues in the IPTV system.
---- Operations like Package subscription WILL NOT HAVE PENDING ORDER even if there are
some issues in the IPTV system.
All other operations like STB Replacement, Installation VAS addition, Installation VAS
removal, Package subscription will NOT HAVE ANY PENDING ORDER in CRM system, the
process will either be completed or failed.
4. User Creation from CRM to IPTV Side:
Current Configuration:
---- When user is created from CRM system in IPTV system for each IPTV number created in
the CRM system following API from IPTV system is invoked:
i. createSubscriber4Ipt
In current configuration, NTTVID is passed as the user identifier in the request XML
of createSubscriber4Ipt such that new user is created under that ID in TV side.
ii. assignStb4Ipt
In current configuration , assignStb4Iptv is invoked after Createsubscriber4Iptv for
Add-On offer even within same CPE as NTTV ID is used as identifier and system
treats the Add-On offer as new user .
ii. assignStb4Ipt
For updated configuration with user signified by Customer_Id, all other IPTV Add-On
Offer within SAME CPE AND SAME ACCOUNT, ONLY assignStb4Ipt is
invokedassignStb4Ipt
i. Createsubscriber4Iptv
a. Request XML
Current configuration Updated configuration
<soapenv:Envelope <soapenv:Envelope
xmlns:xsi="http://www.w3.org/2001/XMLSchema- xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema xmlns:xsd="http://www.w3.org/2001/XMLSchema
" "
xmlns:soapenv="http://schemas.xmlsoap.org/soa xmlns:soapenv="http://schemas.xmlsoap.org/soa
p/envelope/" p/envelope/"
xmlns:urn="urn:iptv.model"> xmlns:urn="urn:iptv.model">
<soapenv:Header> <soapenv:Header>
<api-key xsi:type="xsd:string">exkUoXvRPG</api- <api-key xsi:type="xsd:string">ex90oXvRP</api-
key> key>
<api-secret <api-secret
xsi:type="xsd:string">GCc5T2Qj2CuhgAdw7cQtSEq xsi:type="xsd:string">grc5T2Qj2CuhgAdw7cQtSEq
RIJXLTuQs</api-secret> RIJeLTuo</api-secret>
</soapenv:Header> </soapenv:Header>
<soapenv:Body> <soapenv:Body>
<urn:createSubscriber <urn:createSubscriber
soapenv:encodingStyle="http://schemas.xmlsoap. soapenv:encodingStyle="http://schemas.xmlsoap.
org/soap/encoding/"> org/soap/encoding/">
<request> <request>
<username <username
xsi:type="xsd:string">NTTV461009564</username xsi:type="xsd:string">NTTV401015774</username
> >
<password <password
xsi:type="xsd:string">12345678</password> xsi:type="xsd:string">12345678</password>
<email xsi:type="xsd:string"></email> <email xsi:type="xsd:string"></email>
<status xsi:type="xsd:string">1</status> <status xsi:type="xsd:string">1</status>
<fname xsi:type="xsd:string">JANAK</fname> <fname xsi:type="xsd:string">AFIVE</fname>
<lname xsi:type="xsd:string">THAPA</lname> <lname xsi:type="xsd:string">ZFIVE</lname>
<address <address xsi:type="xsd:string">test-
xsi:type="xsd:string">Kaski,Gandaki,Bhairahawa</ 5,test,Kathmandu,Bagmati,Kathmandu</address>
address> <city xsi:type="xsd:string">12</city>
<city xsi:type="xsd:string">null</city> <district xsi:type="xsd:string">12</district>
<district xsi:type="xsd:string">140102</district> <province xsi:type="xsd:int">1</province>
<province xsi:type="xsd:int">1</province> <country xsi:type="xsd:int">156</country>
<country xsi:type="xsd:int">156</country> <mobile_no
<mobile_no xsi:type="xsd:string">9851100006</mobile_no>
xsi:type="xsd:string">061521232</mobile_no> <cust_id
</request> xsi:type="xsd:string">10133948481_1</cust_id>
</urn:createSubscriber> </request>
</soapenv:Body> </urn:createSubscriber>
</soapenv:Envelope> </soapenv:Body>
</soapenv:Envelope>
IPTV side update
The main idea for use of Customer_Id as main identifier for flow of IPTV system is to ensure
the hierarchical relationship/dependency of Main and Add-On TV offer of same customer. In
current configuration, the user is determined by NTTV_ID which treats both the Main and
Add-On TV offer of same customer as individual primary packages. However now, after this
update, all the Main and Add -on TV offer can be encapsulated under Customer_Id as
primary and secondary packages.
subscribePackage4IptvVas XML