Hi All,
We have a new batch of Arris MTAs, TM602B/DM, that we upgraded to SIP firmware v6. We are using them with a Cisco VXR 7246 , an asterisk server, and docsis_server 1.2.1 with a simple patch to return DHCP option 12 (the hostname).
The problem is that although the cable modem registers well, the MTA can take between 3 and 5 minutes, sometimes 20 to register.
We are using on the cable modem cm file SnmpMibObject arrisMtaDevProvMethodIndicator.0 Integer 4; /* gupi */.
As for our MTA file, I am including it bellow. Does anyone has any idea why it takes so long?
TIA,
Rui Ribeiro
Main
{
MtaConfigDelimiter 1;
SnmpMibObject tComLabs.1.1.1.6.0 Integer 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 "999999999" ;
SnmpMibObject sipCfgPortDisplayName.1 String "9999999" ;
SnmpMibObject sipCfgPortLogin.1 String "9999999" ;
SnmpMibObject sipCfgPortPassword.1 String "xxxxxxxxx" ;
SnmpMibObject ifAdminStatus.9 Integer 1; /* up */
SnmpMibObject sipCfgPortDisplayName.2 String "0" ;
SnmpMibObject sipCfgPortUserName.2 String "0" ;
SnmpMibObject sipCfgPortLogin.2 String "0" ;
SnmpMibObject sipCfgPortPassword.2 String "xxxxxxxxxx" ;
SnmpMibObject ifAdminStatus.10 Integer 0 ;
SnmpMibObject sipCfgProxyAdr.0 String "xxx.xx.xxx.xx" ;
SnmpMibObject sipCfgProxyType.0 Integer 0; /* ipv4 */
SnmpMibObject sipCfgRegistrarAdr.0 String "xxx.xx.xxx.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;
}
That behavior is usually intentional. It's a back-off timer to prevent all the MTAs from registering at once (flooding the SIP server) in the event of a commercial power failure. The backoff timer is a random figure that's between 0-15 minutes.
One note: It should function in a manner that will force registration immediately if a user picks up the phone while the MTA is waiting to register. You should be able to test and verify.
I have some Arris TM402G EMTA loaded with the packet cable software , i have been trying to get then to register to my trixbox without any luck.
Can someone that have setup these devices successfully send me an email so we can discuss an opportunity to get them integrated.
velgroup@aol.com
From memory it's controlled by this setting
SnmpMibObject pktcNcsEndPntConfigMWD.9 Integer X ;
Unless you set this the initial registration attempt will take a random amount of time (up to 20 min or somesuch sounds about right). As previous posted said the design is to prevent SIP server from getting overloaded after a mass outage has been fixed.
But you have MWD set to 10 (seconds) so not sure why you are seeing a delay.
Maybe next time have someone try picking up the handset. This forces the to register straight away. This might help prove whether its a MWD problem, or some other problem causing the initial registration delay. You could also look in the advanced trouble shooting pages of the modem to see whether the delay is MTA provisioning, or whether the MTA is provisioned quickly but sitting waiting for MWD.