Hi all,
We have just received 2 MTA test modems TM602B/DM with the firmware TS050254_032808_NA-MODEL_4_5_6.SIP.TELNET_ON.img.
The point is that our old Arris MTA models worked with our CM file and an asterisk server, and the new models dont work. I verified the configuration, and I am quite a loss of what is the problem. The cable DOCSIS part is still working fine.
We are suspecting that it should be some minor tweak to the file that we have bellow.
If someone has some clue, we would appreciate it.
Regards,
Rui
Main
{
MtaConfigDelimiter 1;
SnmpMibObject pktcMtaDevEnabled.0 Integer 1; /* true */
SnmpMibObject ppCfgMtaFeatureSwitch.0 HexString 0x00000006 ;
SnmpMibObject ppCfgMtaCountryTemplate.0 Integer 10; /* portugal */
SnmpMibObject ppCfgMtaCallpFeatureSwitch.0 Integer 16416 ;
SnmpMibObject sipCfgSipFeatureSwitch.0 HexString 0x04160000 ;
SnmpMibObject sipCfgPortT38Mode.0 Integer 2; /* t38Loose */
SnmpMibObject sipCfgPortUserName.1 String "276000XXX" ;
SnmpMibObject sipCfgPortDisplayName.1 String "276000XXX" ;
SnmpMibObject sipCfgPortLogin.1 String "276000XXX" ;
SnmpMibObject sipCfgPortPassword.1 String "XXXXX" ;
SnmpMibObject ifAdminStatus.9 Integer 1; /* up */
SnmpMibObject sipCfgPortUserName.2 String "" ;
SnmpMibObject sipCfgPortDisplayName.2 String "" ;
SnmpMibObject sipCfgPortLogin.2 String "" ;
SnmpMibObject sipCfgPortPassword.2 String "XXXX" ;
SnmpMibObject ifAdminStatus.10 Integer 1; /* up */
SnmpMibObject sipCfgProxyAdr.0 String "xx.xx.xx.xx" ;
SnmpMibObject sipCfgProxyType.0 Integer 0; /* ipv4 */
SnmpMibObject sipCfgRegistrarAdr.0 String "xx.xx.xx.xx" ;
SnmpMibObject sipCfgRegistrarType.0 Integer 0; /* ipv4 */
SnmpMibObject sipCfgProvisionedCodecArray.0 String "G729;G729E;telephone-event" ;
SnmpMibObject pktcNcsEndPntConfigMWD.9 Integer 10 ;
SnmpMibObject sipCfgDialFeatName.1 Integer 70; /* callWaitTempDisable */
SnmpMibObject sipCfgDialFeatCode.1 String "*43" ;
SnmpMibObject sipCfgDialFeatTone.1 Integer 1; /* stutterTone */
SnmpMibObject sipCfgDialFeatActive.1 HexString 0x00000003 ;
VendorSpecific
{
VendorIdentifier 0x0000ca;
GenericTLV TlvCode 69 TlvStringZero "x.t|#21#|#61#|#67#|#31#x.t|*#xx#|*xxx#|*xx*x.[#t]|*xx*x.*xx[#t]"; /* tlv length = 64 */
}
MtaConfigDelimiter 255;
}
What exactly is not working? Is the MTA failing to register? What part in the process does the MTA think it is getting to?
That firmware looks quite old they are at 6.1.77 or higher currently, that is 5.2.54? Could be a firmware compatibility problem.
Exactly, MTA is not registering.
I´ve tried to upgrade the firmware with the sample file the provider sent me, but it turned out it didnt work. The modem refused to register with the following CM file they sent us.
Main
{
NetworkAccess 1;
SnmpMibObject docsDevSwAdminStatus.0 Integer 2; /* allowProvisioningUpgrade */
SwUpgradeServer x.x.x.x;
SwUpgradeFilename "TS060151D_033009_EU.MODEL_6.EURO.SIP.TELNET_ON.img";
ClassOfService
{
ClassID 1;
MaxRateDown 10000000;
MaxRateUp 2500000;
PriorityUp 1;
PrivacyEnable 0;
}
MaxCPE 8;
MfgCVCData 0x308203823082026aa00302010202107387a57fba00657f0267442476a9d2c0300d06092a864886f70d0101050500306f310b3009060355040613024245311f301d060355040a131674436f6d4c616273202d204575726f2d444f4353495331153013060355040b130c4361626c65204d6f64656d73312830260603550403131f4575726f2d444f43534953204361626c65204d6f64656d20526f6f74204341301e170d3031313231323030303030305a170d3133313231313233353935395a306f310b300906035504061302555331223020060355040a1319417272697320496e7465726163746976652c204c2e4c2e432e31143012060355040b130b45;
MfgCVCData 0x75726f2d444f43534953312630240603550403131d436f646520566572696669636174696f6e20436572746966696361746530820122300d06092a864886f70d01010105000382010f003082010a0282010100a8d75608634bf7b065dd7c5f71ace3b4b2c9955b567b41e8834b44950fa61e2c68ffbecd6b5830566cef5737a4f36093690bd1357cfe346bb149c6b6848012581849a207fa588435e40c01a5fea58e37947af09b4a56251e794d8c8d20a10d44a4e8bf6f68f6ef29f8902c581fae5b59d6527ea5b890fd61618c13f018f67f48cfa96ce5fd33c08577e4c4310b9c12c830d13018cd776df2d69ea4fb605f8700a85b694bcfe83ce077eeb4;
MfgCVCData 0x41808a19395e43b020b4b08cfbdee065586c36595bd4b6d06fb910bbcc2c6a3371981deb64b626ee2ec8146c3392645655c762920b5aed82a9783500c276136079d6573b2ff7d423bd6c7f54ba7df88c822998a5630203010001a31a301830160603551d250101ff040c300a06082b06010505070303300d06092a864886f70d01010505000382010100699926a57be6c02398837b6a00b6ca4ec37fd20965d9e06d26a01d50372fcda100396040fc2efc844a3f09045ed2ee3628428d40b41167f8d2d639eeac7d68e377bfbe9f772455c0b425a958ae54a9694af94f9fb41748f513fe1fdbb1b6fcccfedd1863edb87454beb41477794b5689fb5f069a;
MfgCVCData 0x43cc160dafb7627f8938100dc3e19ff851b7850ddbf635da8b68bdce63fb6a315fcef64d792fd0b523deb83dd24027baaced61b83f76d5eb08d65c5fda9f1a6b48cb2f933b8fdec3d0140be069b0e2b7e21a8d4c734a6670309a1a5064919bae99a5b0c2d6b90682eecd4e326585a28e3b760e3016f63ddccdc6bdf56b5b43c468ab31ef09adfd755a25baa2;
/* CmMic 0c21284e2856ce1a8de3a99f6a8ba4ed; */
/* CmtsMic 8dae222e00a74fab3b8be0c93aa4c3a1; */
/*EndOfDataMkr*/
}
Why modem doesn't register? Is DHCP sequence completed? ToD ok? Is TFTP working? Is firmware in root of /tftpboot? And so on.. DHCPdump, syslog etc.
Actually we have the same situation, but we know our problem.
Our provisioning system works still with static cm files. Now we're trying to place new dynamic cm files and the first results are positive. Internet provisioning is ok, telephony not yet.
arsene, we are using docsis_server and for Internet provisioning, we have a different static file for each level of service. For Telephony, we generate the file once we configure the customer, as the phone number is encoded on the file and they are different. In fact, with the old version of the Arris modems we have on site with the version 5 firmware everything works ok, it is just that the new batch a new model with a more recent firmware (6), takes too long too register.
Rui
Hi,
I do know that the 402s and 502s take one file and th 602s take a different firmware file. Make sure you're giving the right one to the modem. If you're still stuck, let me know.
emkowale
A couple of troubleshooting techniques.
1. Login to 192.168.0.1 locally via ethernet plugged into the eMTA. Click on CM Configuration and check the registration state of the CM.
2. Are you using Secure MTA provisioning with a KDC or using BASIC.1 with a SHA1 hash in the eMTA config file?
3. What type of CMTS are you using and what state is the modem reporting on the CMTS?
4. If the modem is registering on the CMTS and the MTA side is NOT, check and see if you have the end point terminated on the CMS.
5. The 402 and the 502 use 1 flavor of software hence the name in the image 4_5 and the 6 uses a different software image, hence the _6.
Let me know whats going on.
Regards,
Will
As you can see this image:
TS0601101_052010_NA.MODEL_6.EURO.SIP.TELNET_ON.img
Is strictly for the 602 and NOT for the 402 or 502.
You will need to use:
TS0601101_052010_NA.MODEL_4_5.EURO.SIP.TELNET_ON.img
For the 402 and 502 devices.
If you have access to snmp to the modem use the following OID to query the software upgrade state of the modem.
snmpwalk -v 2c -c COMMSTRING 10.10.10.10 .1.3.6.1.2.1.69.1.3 (docsDevSw) found in the Cable Device MIB. aka RFC2669 depreciated and now RFC4639
http://www.oidview.com/mibs/0/DOCS-CABLE-DEVICE-MIB.html
You can also query .1.3.6.1.2.1.69.1.5.8.1.7 to see the Event Log of the modem and see if there is a CVC validation failure or image corruption problem.
Let me know.
Regards,
Will
Hi hinzoo,
We have been doing debugging for days, seeing logs and sniffing packets at the DHCP and SIP server. Everything seems alright at the DHCP side, the data part registers properly, and as far as the DHCP server is aware, the MTA too. However, the lights of the MTA just keep on blinking for several minutes, during which the SIP server keeps on sending malformed packets to it(?). Still havent managed to see the initial packet that initiates all that dialog with tcpdump pointing to the IP of the modem, which is rather strange. Only after several minutes does the MTA registers on the SIP server with a good packet, and the SIP keeps on sending malformed packets after it registers.
Will send logs later on.
Best regards,
Rui
Hi hinzoo,
We have been doing debugging for days, seeing logs and sniffing packets at the DHCP and SIP server. Everything seems alright at the DHCP side, the data part registers properly, and as far as the DHCP server is aware, the MTA too. However, the lights of the MTA just keep on blinking for several minutes, during which the SIP server keeps on sending malformed packets to it(?). Still havent managed to see the initial packet that initiates all that dialog with tcpdump pointing to the IP of the modem, which is rather strange. Only after several minutes does the MTA registers on the SIP server with a good packet, and the SIP keeps on sending malformed packets after it registers.
Will send logs later on.
Best regards,
Rui