.
Issue with MTA: If you are trying to decode 5.2.1sp16.00 MST on switch/DRCCD then you may not get Call Record MST messages decoded properly by MTA.
Solution : Mentioned below is solution using which you can use to decode the same:
On CM:
1. Become root
2. Copy the MTA rpm from DRCCD to CM under /var/disk/rpms/
DRCCD location: /usr/add-on/offer_components/ACP/MessageTracer/MessageTracer-6.4.4.4-5x.i386.rpm
3. Remove the existing MessageTracer version from CM by running:
rpm –e MessageTracer
4. Install the copied MessageTracer rpm by running:
rpm –ivh /var/disk/rpms/MessageTracer-6.4.4.4-5x.i386.rpm
5. Then use mta as normal.
On DRCCD:
1. Set the environment to 5.2.1sp14.00 (not to 5.2.1sp16.00)
Run MTA on MST and you should get Call Records decoded.
We have drafted a KB article in collaboration with CPE to help you folks with MTA and other dcrccd profile issues (As part of ECS / UC collaboration program). The link to the article is as below.
Solution : Mentioned below is solution using which you can use to decode the same:
On CM:
1. Become root
2. Copy the MTA rpm from DRCCD to CM under /var/disk/rpms/
DRCCD location: /usr/add-on/offer_components/ACP/MessageTracer/MessageTracer-6.4.4.4-5x.i386.rpm
3. Remove the existing MessageTracer version from CM by running:
rpm –e MessageTracer
4. Install the copied MessageTracer rpm by running:
rpm –ivh /var/disk/rpms/MessageTracer-6.4.4.4-5x.i386.rpm
5. Then use mta as normal.
On DRCCD:
1. Set the environment to 5.2.1sp14.00 (not to 5.2.1sp16.00)
Run MTA on MST and you should get Call Records decoded.
We have drafted a KB article in collaboration with CPE to help you folks with MTA and other dcrccd profile issues (As part of ECS / UC collaboration program). The link to the article is as below.
