MacmillaN
On our wavelength
Joined 13 years ago
User Profile
User Widgets
Contributions
Connection Issues Hub 5.
Good Afternoon, I have been expericaing connection issues, I have bad pixelation on tv channels and now the connection seems to be dropping randomly from modem. I read a post about faulty firmware, not sure if hats the cause, but the hub is on : cmreg-vmdg660-bbt078+voc-b.cm Time Priority Description 23-01-2026 18:01:05 notice CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:01:04 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:17 notice CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:13 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:11 notice CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:09 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:09 warning MDD message timeout;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:06 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 18:00:03 notice US profile assignment change. US Chan ID: 12; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 17:59:55 notice REGISTRATION COMPLETE - Waiting for Operational status 23-01-2026 17:59:45 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 17:59:43 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 17:59:40 notice Honoring MDD; IP provisioning mode = IPv4 23-01-2026 17:59:37 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 17:59:33 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 17:59:31 critical Cable Modem Reboot because of - kernel-panic 23-01-2026 13:13:20 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 13:13:15 critical Cable Modem Reboot because of - kernel-panic 23-01-2026 13:13:15 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 11:35:56 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 11:35:52 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 11:35:50 critical Cable Modem Reboot because of - kernel-panic 23-01-2026 09:58:48 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 09:58:45 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 09:58:43 critical Cable Modem Reboot because of - kernel-panic 23-01-2026 05:32:07 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 23-01-2026 05:32:02 critical Cable Modem Reboot because of - kernel-panic 23-01-2026 05:32:02 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 22-01-2026 20:53:50 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 22-01-2026 20:53:47 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1; 22-01-2026 20:53:45 critical Cable Modem Reboot because of - kernel-panic 22-01-2026 19:24:30 critical No Ranging Response received - T3 time-out;CM-MAC=a4:22:49:f1:d6:d4;CMTS-MAC=00:01:5c:9c:3a:4f;CM-QOS=1.1;CM-VER=3.1;104Views0likes2CommentsRe: Hub 5 Connection issues.
Good Evening @Matthew_ML as mentioned previously in the comments, other users are saying it’s unusual to have 'Post RS Errors'. Possibly a bad hub and those stats usually indicate noise ingress, my hub was before posting the stats experiencing random connection drops! Thanks for your time!32Views0likes1CommentHub 5 Connection issues.
We are experiencing random connection drops during the day, here are the modem stats, for you to hopefully spot something, all connections are tight! 3.0 Downstream channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 227000000 6.1 41 QAM 256 12 2 139000000 5.9 40 QAM 256 1 3 147000000 6 40 QAM 256 2 4 155000000 6.1 40 QAM 256 3 5 163000000 6.3 40 QAM 256 4 6 171000000 6.3 41 QAM 256 5 7 179000000 6.3 41 QAM 256 6 8 187000000 6.3 41 QAM 256 7 9 195000000 6.7 41 QAM 256 8 10 203000000 6.6 41 QAM 256 9 11 211000000 6.7 41 QAM 256 10 12 219000000 6.4 41 QAM 256 11 13 235000000 6.1 41 QAM 256 13 14 243000000 6.1 41 QAM 256 14 15 251000000 6.1 41 QAM 256 15 16 259000000 6.2 41 QAM 256 16 17 267000000 6.7 41 QAM 256 17 18 275000000 7.2 41 QAM 256 18 19 283000000 7.1 41 QAM 256 19 20 291000000 6.8 41 QAM 256 20 21 299000000 6.3 41 QAM 256 21 22 307000000 5.9 41 QAM 256 22 23 315000000 5.8 41 QAM 256 23 24 323000000 6 41 QAM 256 24 25 331000000 6.2 41 QAM 256 25 26 339000000 6.3 41 QAM 256 26 27 347000000 6.3 41 QAM 256 27 28 355000000 6.3 41 QAM 256 28 29 363000000 6.2 41 QAM 256 29 30 371000000 5.8 41 QAM 256 30 31 379000000 5.7 41 QAM 256 31 3.0 Downstream channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 41 88 133 2 Locked 40 177 112 3 Locked 40 1211 2327 4 Locked 40 4789 3549 5 Locked 40 823 2207 6 Locked 41 1000 3602 7 Locked 41 617 2528 8 Locked 41 617 2852 9 Locked 41 489 2228 10 Locked 41 645 3200 11 Locked 41 672 3449 12 Locked 41 694 1707 13 Locked 41 821 2983 14 Locked 41 717 2432 15 Locked 41 760 2656 16 Locked 41 995 3452 17 Locked 41 1068 3772 18 Locked 41 996 2712 19 Locked 41 1008 2884 20 Locked 41 755 2888 21 Locked 41 1093 4135 22 Locked 41 762 2533 23 Locked 41 913 3062 24 Locked 41 621 2442 25 Locked 41 770 2886 26 Locked 41 104635 65748 27 Locked 41 651 3161 28 Locked 41 1061 4119 29 Locked 41 837 4413 30 Locked 41 749 3469 31 Locked 41 675 3266 3.1 Downstream channels Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz) 33 94 4K 1840 QAM 4096 1108 3.1 Downstream channels Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile) 33 Locked 40 0.1 3378310427 139269 3.0 Upstream channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 0 49600000 45.5 5120 QAM 64 1 1 43100000 45.5 5120 QAM 64 2 2 36600000 45.5 5120 QAM 64 3 3 30100000 45.5 5120 QAM 64 4 4 23600000 45.8 5120 QAM 64 5 3.0 Upstream channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0 ATDMA 0 0 0 0 1 ATDMA 0 0 0 0 2 ATDMA 0 0 0 0 3 ATDMA 0 0 1 0 4 ATDMA 0 0 0 0 3.1 Upstream channels Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation 12 10.4 40.7 2K QAM 256 3.1 Upstream channels Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts 12 OFDMA 208 74000000 24 0306Views0likes6CommentsRe: Can't upgrade to 360
Good afternoon Vikki_M, So as stated above i received my two new V360 remotes, for two V6 boxes, so i attempted the upgrade on the first box within the property, everything was going smoothly, untill a few moments into the update! (This is just a thought does the hard drive need to be cleared before the update?!) I received the attached error. I never proceeded to attempt the update on box two, due to reading the instructions it stated the 2nd box should update automatically! Hope you can help! Thanks1.1KViews0likes0CommentsRe: (Hub 5) CM-STATUS messages 16 & 24 showing in Network Log.
Just realised i forgot to post the actual log. 09-08-2024 02:34:48 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 01:13:24 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 01:11:07 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:42:57 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:40:17 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:38:29 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:27:36 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:21:00 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:13:19 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:09:12 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 09-08-2024 00:05:11 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:48:59 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:46:49 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:33:01 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:30:59 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:13:47 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:10:09 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:08:30 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 23:06:39 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:55:40 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:25:23 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:21:35 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:18:52 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:18:17 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:15:15 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:12:51 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 22:05:22 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 21:57:23 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 21:55:04 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 21:47:20 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 21:44:44 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 08-08-2024 21:39:06 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;437Views0likes1Comment
