Hi,
I am setting up a DOCSIS test environment with CASA C2200 and some EPC3925 modems.
The DOCSIS provision attempt was a success, however I cannot get the MTA part working.
The modem always complains that the hash at the end of the MTA config file is missing.
Here is the config file I use:
Main
{
MtaConfigDelimiter 1;
SnmpMibObject pktcMtaDevEnabled.0 Integer 1; /* true */
SnmpMibObject saEmtaSipEndPntProxyUsername String "7099004055" ;
SnmpMibObject saEmtaSipEndPntProxyPassword String "12345678" ;
SnmpMibObject saEmtaSipEndPntProxyDisplayName String "7099004055" ;
SnmpMibObject saEmtaSipEndPntProxyAddress String "192.168.251.163" ;
SnmpMibObject saEmtaSipEndPntRegistrarAddress String "192.168.251.163" ;
SnmpMibObject saEmtaSipEndPntProxyPortRemote Gauge32 5060 ;
SnmpMibObject saEmtaSipEndPntRegistrarPortRemote Gauge32 5060 ;
SnmpMibObject saEmtaSipEndPntPacketization Integer 20; /* twenty */
SnmpMibObject pktcNcsEndPntConfigMWD.9 Integer 10 ;
SnmpMibObject ifAdminStatus.9 Integer 1; /* up */
SnmpMibObject ifAdminStatus.10 Integer 0 ;
SnmpMibObject pktcMtaDevProvConfigHash.0 HexString 0xbc51a6b31d84ea6098eebb0c6afb1a94200b9190 ;
MtaConfigDelimiter 255;
}
I tried the sha1sum method and also the patch for the "docsis" apllication, because I thought one of the method is failing, but both method generates the very same hash.
The modem's log specifically say that the hash (pktcMtaDevProvConfigHash.0) is missing and it is mandatory for BASIC flow, and not telling that the hash is invalid or miscalculated.
The modem runs an ESIP firmware version.
If you guys have any idea what to try, I am open to any suggestions.
Thanks!
Just checking if you are doing it right....
If you are using the linux docsis editor without any patches the sequence is :
1) compile the mta source file (without the pktcMtaDevProvConfigHash.0 line)
2) sha1sum the output file
3) insert pktcMtaDevProvConfigHash.0 line into the source file (From memory it has to be the last line before the MtaConfigDelimiter)
4) compile the source file again
Although if you have already tried both ways, and got the same hash, it sounds like you are probably doing it correctly.
Are you sure that your provisioning sequence is correctly configured for BASIC ?
Are you doing BASIC.1 or BASIC.2? Your example above looks like BASIC.1
For BASIC.1 :
* in the CM offer you should be setting 122.1 to IP of your DHCP server, and 122.6 to BASIC.1
* in the MTA offer you should be setting 122.3 to the FQDN of your DHCP server, and 122.6 to BASIC.1
NOTE : BASIC.1 is very insecure! It is not hard for someone to grab all the MTA config files from your TFTP server, and thus be able to place calls under someone else's account. I would not recommend using this method except for initial testing of your voip service.
Hi mbowe!
I know it is inse cure, but this should be the easiest to try out and yet it is not working. :-)
Anyway, this is a lab environment only.
I attached a printscreen from the MTA DHCP offer, I think it is okay.
Tell me one thing: is it a problem if not only the MTA, but the CM also got these extra option 122 DHCP parameters? Because now the difference between the CM and the MTA DHCP offer is the name of the config file (the CM also gets the option 122 parameters, like the MTA).
Thanks!
Besides the EPC3925 I also tried with an EPC2302 eMTA (SIP firmware also), but the result is the same.
I am kinda clueless at this point.
Hi,
Here is my working konfig, no need pktcMtaDevProvConfigHash.
My modem-sw version is: epc3925-ESIP-16-v302r125574-131129c-CVC060414.p7b,
and i use Basic 1 flow.
Main
{
MtaConfigDelimiter 1;
SnmpMibObject pktcMtaDevEnabled.0 Integer 1;
SnmpMibObject saMtaDevCountryCode.0 Integer 15;
SnmpMibObject saEmtaSipDeviceDigitMap.0 String "your_dial_plan_string" ;
SnmpMibObject saEmtaSipEndPntProxyAddress.1 String "a.b.c.d" ;
SnmpMibObject saEmtaSipEndPntProxyPortRemote.1 Gauge32 5060 ;
SnmpMibObject saEmtaSipEndPntProxyUsername.1 String "1111111" ;
SnmpMibObject saEmtaSipEndPntProxyPassword.1 String "sgghjwegRcR1fpBV6" ;
SnmpMibObject saEmtaSipEndPntProxyPasswordEncrypt.1 Integer 0 ;
MtaConfigDelimiter 255;
}
Feel free to ask if anything is unclear.
Hi szpal!
Thanks for the config file.
I tried it with and without the hash tag, but the result is the same: missing config file parameter error because of the hash tag.
Can you please send me the firmware you used, so I can try it out?
My address is metro4 at freemail dot hu
My fw is slightly different:
HW_REV: 1.0; VENDOR: Cisco; BOOTR: 2.3.0_R1; SW_REV: epc3925-ESIP-16-v302r12911-100506c-STF; MODEL: EPC3925
Thanks!
I tried your CM software version with your config file (with and without the hash tag), and I still got the same error on the modem.
Good news is at least now I know that there must be some other problem, because otherwise this is not possible.
I keep trying.
I concluded some tests with the following result:
There still should be some Cisco specific probelm with the MTA config file, because with and without hash, EPC3925 and other older Cisco CMs are also complaining that the provhash is missing.
In the mean time I got two DOCSIS3 Hitron modem with SIP eMTA firmware and I was able to make them work, they are doing SIP completely fine.
My question is am I missing something? Forexample: despite I send BASIC.1 to the MTA DHCP offer, this provisioning mode is disabledsomehow in the firmware or something and this is the reason my config got rejected by the MTA? Or I need to include something special in the CM config file for Cisco modems to make BASIC flow work?
Thanks!
Make sure the MTA config file has the EURODOCSIS version of pktcMtaDevEnabled.0, rather than DOCSIS version
/* DOCSIS version PKTC-MTA-MIB::pktcMtaDevEnabled.0 */
SnmpMibObject .1.3.6.1.4.1.4491.2.2.1.1.1.7.0 Integer 1;
/* EuroDOCSIS version PKTC-EXCENTIS-MTA-MIB::pktcMtaDevEnabled.0 */
SnmpMibObject .1.3.6.1.4.1.7432.1.1.1.6.0 Integer 1;
Hi Guys,
Thanks for the help!
My EPC3925 runs the following firmware:
Cisco EPC3925 EuroDOCSIS 3.0 2-PORT Voice Gateway HW_REV: 1.0; VENDOR: Cisco; BOOTR: 2.3.0_R1; SW_REV: epc3925-ESIP-16-v302r12911-100506c-STF; MODEL: EPC3925
I also tried with and without the hash and both times the modem complains that there is no hash tag in the mta config file and that is mandatory.
and yes: I am sending the domain name of my prov server and "BASIS.1" in the DHCP offer, otherwise the MTA wouldn't even start to download the file.
Here is the log from the modem:
emta factory agent enabling management.
emta factory agent sending deferred traps...
Done w/ deferred traps.
emta factory agent entering RFC-2576 Coexistence security mode.
emta factory agent setting V1/V2 view to coexistenceView
Opening file 'mta.bin' on 24.27.0.5 for reading...
Tftp transfer complete!
TFTP Settings:
Stack Interface = 6
Server Ip Address = 24.27.0.5
Server Port Number = 69
Total Blocks Read = 1
Total Bytes Read = 359
15:42:34.050 03/07/2014 (PROV) FATAL ERROR: prfTlvConfigFileDownload - Could not find hash in file for BASIC flow...
15:42:34.050 03/07/2014 (SNMP) WARN: CreateOidsErrorEntry: ErrorOid=, ErrorValue=, ErrorReason=pktcMtaDevProvConfigHash MUST be present in MTA cfg file for BASIC flow
15:42:34.050 03/07/2014 (PROV) FATAL ERROR: TFTP task failed. Err=0x11105
BcmSnmpTrapThread beginning to poll for inform retries.
EmtaAgentSendNotify_2573 is sending a notify
EmtaAgentSendNotify_2573 is sending a notify
EmtaAgentSendNotify_2573 is sending a notify
EmtaAgentSendNotify_2573 is sending a notify
CM>
I got the same if I hash the file and the same if I do not hash the file.
Maybe my FW version has some limitations, this modem was previously used by another cable operator.
Dchard