| Attachment | Size |
|---|---|
 arris.log_.txt | 13.43 KB |
Hi,
after trying too long to provision the mentioned SIP-MTA (with Firmware Revision: 9.1.103S1), some kind of frustration comes up. CM is operational and the MTA goes online and loads the appropriate config file - written like:
Main
{
MtaConfigDelimiter 1;
SnmpMibObject pktcMtaDevEnabled.0 Integer 1; /* true */
SnmpMibObject sipCfgDigitMap.0 String "x.T";
SnmpMibObject ifAdminStatus.9 Integer 1; /* up */
SnmpMibObject sipCfgPortUserName.1 String "0123456789";
SnmpMibObject sipCfgPortDisplayName.1 String "0123456789";
SnmpMibObject sipCfgPortLogin.1 String "0123456789";
SnmpMibObject sipCfgPortPassword.1 String "abcd";
SnmpMibObject ifAdminStatus.10 Integer 2; /* down */
SnmpMibObject sipCfgProxyAdr.0 String "sip.server.net";
SnmpMibObject sipCfgProxyType.0 Integer 1; /* dns */
SnmpMibObject sipCfgRegistrarAdr.0 String "sip.server.net";
SnmpMibObject sipCfgRegistrarType.0 Integer 1; /* dns */
SnmpMibObject pktcMtaDevProvConfigHash.0 HexString 0xa27f8212a72c9d82465b7dcfaaf33f7f1a2a249d;
MtaConfigDelimiter 255;
}
In my opinion this should be a minimum configuration that works. (i replaced the correct phonenr, password and proxy server)
The MTA logs say provisioning successful, but it's not correctly registered on the Call Management Server.
I attached the whole logging i got from the telnet session.
I appreciate any help.
here is the one i use for testing
TelephonyConfigFileBeginEnd = 1
SnmpMib = ppCfgMtaCallpFeatureSwitch.0 hexstr: 00.00.00
SnmpMib = pktcMtaDevEnabled.0 true
SnmpMib = arrisMtaDoc30EmergencyNumber.0 "911"
SnmpMib = sipCfgEmergencyNumber.0 "911"
SnmpMib = arrisMtaDevRtcpTosValue.0 46
SnmpMib = pktcSigTosFormatSelector.0 dscpCodepoint
SnmpMib = pktcSigDefCallSigTos.0 26
SnmpMib = pktcSigDefMediaStreamTos.0 46
SnmpMib = sipCfgDomainOverride.0 "sip.server.com"
SnmpMib = sipCfgPortUserName.1 "1235556789"
SnmpMib = sipCfgPortDisplayName.1 "1235556789"
SnmpMib = sipCfgPortLogin.1 "1235556789"
SnmpMib = sipCfgPortPassword.1 "password"
SnmpMib = ifAdminStatus.9 up
SnmpMib = pktcNcsEndPntConfigMWD.9 10
SnmpMib = sipCfgProxyAdr.0 "123.456.789.123:5060"
SnmpMib = sipCfgProxyType.0 ipv4
SnmpMib = sipCfgRegistrarAdr.0 "123.456.789.123:5060"
SnmpMib = sipCfgRegistrarType.0 ipv4
SnmpMib = sipCfgSipFeatureSwitch.0 hexstr: 0.83.2.0
SnmpMib = sipCfgProvisionedCodecArray.0 "G729;PCMU;PCMA;telephone-event"
SnmpMib = sipCfgPacketizationRate.0 twentyMilliSeconds
TelephonyConfigFileBeginEnd = 255
i tried it with:
SnmpMibObject enterprises.4115.11.1.3.0 String "123.456.789.123;5060" ; /* Proxy Address */
SnmpMibObject enterprises.4115.11.1.4.0 Integer 0 ; /* Proxy Adr Type: (0: IPv4) */
SnmpMibObject enterprises.4115.11.1.5.0 String "123.456.789.123;5060" ; /* Registrar Address */
SnmpMibObject enterprises.4115.11.1.6.0 Integer 0 ; /* Registrar Adr Type: (0: IPv4) */
but with the same result (log attached). Does anyone recognize an error message in the log that i don't see and that could give another hint?
Make sure that you replace the IP address in those strings with your own SIP server IP address... I figured you would notice thats not even a valid IP 0_0
lol ... i did that ;)
good, did you mean to have a semicolon in before the port or is that a typo on the sanitize, also, if you don't need a domain override, make sure you take the sip.server.com line out (or make sure it matches your sip domain)
Seems a bit strange
Might be worth looking in the modem event log to see if any hints (although the telnet console generally gives a lot more useful information).
Also could try tcpdump/wireshark the MTA IP on the CMS server
Does the failure happen for only this 862, or any you try?
What MTA provisioning method are you using?
I don't actually know why, but it's working now with the following config:
SnmpMibObject ifAdminStatus.9 Integer 1;
SnmpMibObject enterprises.4115.11.1.1.1.2.1 String "0123456789" ;
SnmpMibObject enterprises.4115.11.1.1.1.3.1 String "0123456789" ;
SnmpMibObject enterprises.4115.11.1.1.1.4.1 String "0123456789" ;
SnmpMibObject enterprises.4115.11.1.1.1.5.1 String "password" ;
SnmpMibObject enterprises.4115.11.1.2.0 String "x.T" ; /* Digit Map */
SnmpMibObject enterprises.4115.11.1.3.0 String "sip.server.net;5060" ; /* Proxy Address */
SnmpMibObject enterprises.4115.11.1.4.0 Integer 0 ; /* Proxy Adr Type: IPv4 */
SnmpMibObject enterprises.4115.11.1.5.0 String "sip.server.net;5060" ; /* Registrar Address */
SnmpMibObject enterprises.4115.11.1.6.0 Integer 0 ; /* Registrar Adr Type: IPv4 */
SnmpMibObject enterprises.4115.11.1.7.0 HexString 0x04002000 ;
SnmpMibObject enterprises.4115.10.1.14 Integer 7 ; /* germany */
SnmpMibObject enterprises.4115.10.1.20 Integer 16384 ;
SnmpMibObject .1.3.6.1.4.1.7432.1.1.1.6.0 Integer 1; /* true, the MTA/voice feature is enabled (Excentis mib) - working */
Guess I didn't notice before thats the eurodocsis model, ...subtle differences
Ha!
I had considered whether to ask if it was EuroDOCSIS, but because you said it had provisioned OK I assumed this was not the case
Yeah with Euro, some of the MIBs in the MTA config file are different
This can be very confusing with the linux docsis compiler, as it doesn't really know how to switch between DOCSIS and EuroDOCSIS
Easiest way is like you did, change the couple of key entries to the Euro versions
Off the top of my head, you have to change this one :
SnmpMibObject pktcMtaDevEnabled.0
to
SnmpMibObject 1.3.6.1.4.1.7432.1.1.1.6.0
And depending on your provisioning method, may also need this one :
SnmpMibObject pktcMtaDevProvConfigHash.0
to
SnmpMibObject 1.3.6.1.4.1.7432.1.1.2.9.0
1. Careful, that telnet looks to have real usernames/passwords in it.
2. If the MTA provisions OK, but does not register, then perhaps you need to check routing / firewall etc between MTA <-> CMTS <-> SIP server
1. thx for the advise
2. routing and firewall shouldn't be the problem - every other device (FritzBox, Thomson, Technicolor) in the same net registers correctly. The error message on calling is also not that the number not exists, but "the person you've called is temporarily not available". So i think the CMS should be informed, but sth is missing!?
it looks like a DSX issue. remember that SIP registration goes into the SF based on classification, otherwise into the first SF present in the config file. RTP should go into a Dynamic SF, you will need a feature switch configuration for that. I did not check in advance you config, it might be there.
Hi Roee
could I please get a copy of the new firmware for the TG862 Sip
Carl
Hello roee,
If you have still problems you can contact me directly, i am located in Germany. ICQ 635134345.