11-16-2016 01:10 PM - last edited on 03-25-2019 08:41 PM by ciscomoderator
Has anyone managed to get this phone (8831) or perhaps some similar cisco SIP phone working with Asterisk?
Regards.
Solved! Go to Solution.
11-17-2016 02:47 PM
Hold on ... Just looked at the SEPmacaddress.xml.cnf, and I've noticed a lot of missing information.
For example, one of the most glaring configuration issue is the "proxy". Depending on the firmware of the phone, by the way the phone firmware information is also missing from the configuration, means the line could be wrong.
I have attached a known working SEPmacaddress.cnf.xml which can be quickly modified to work with phones like 9951/9971, 8800 phones.
Alternatively, you can look at this old thread (HERE).
11-16-2016 10:24 PM
Which part are you stuck with?
11-17-2016 12:40 AM
Hi Leo,
Well at the moment I'm looking for an xml file to configure the phone.
I found one and the phone seems to be downloading the file but it's not working. It doesn't even try to connect to the asterisk.
11-17-2016 12:56 AM
I found one and the phone seems to be downloading the file but it's not working.
I'm not familiar with 8831 but I am familiar with getting some Cisco phones to Asterisk.
So what error message(s) do you see after the XML file has been downloaded?
11-17-2016 05:53 AM
Well I don't see any error messages. I found the xml example in this forum and tried to adapt it and in it there are some locale and ringtones mentioned and I see the phone trying to also download those files meaning it is getting the original file and trying to apply it but nothing more than that. It doesn't even try to connect to the PBX.
Do you have an example of a xml for this or similar phone?
11-17-2016 06:08 AM
This is the content of the xml file:
<?xml version="1.0" ?>
<device>
<deviceProtocol>SIP</deviceProtocol>
<sshUserId>cisco</sshUserId>
<sshPassword>cisco</sshPassword>
<devicePool>
<dateTimeSetting>
<dateTemplate>D.M.Y</dateTemplate>
<timeZone>W. Europe Standard/Daylight Time</timeZone>
<ntps>
<ntp>
<name>us.ntp.org</name>
<ntpMode>Unicast</ntpMode>
</ntp>
</ntps>
</dateTimeSetting>
<callManagerGroup>
<members>
<member priority="0">
<callManager>
<processNodeName>10.8.1.13</processNodeName>
<ports>
<sipPort>5060</sipPort>
</ports>
</callManager>
</member>
</members>
</callManagerGroup>
</devicePool>
<sipProfile>
<natEnabled>false</natEnabled>
<natAddress></natAddress>
<sipProxies>
<registerWithProxy>true</registerWithProxy>
<outboundProxy>10.8.1.13</outboundProxy>
<outboundProxyPort>5060</outboundProxyPort>
<backupProxy>10.8.1.13</backupProxy>
<backupProxyPort>5060</backupProxyPort>
</sipProxies>
<preferredCodec>alaw</preferredCodec>
<phoneLabel>Conference</phoneLabel>
<sipLines>
<line button="1">
<featureID>9</featureID>
<featureLabel>308</featureLabel>
<proxy>10.8.1.13</proxy>
<port>5060</port>
<name>308</name>
<displayName>308</displayName>
<autoAnswer>
<autoAnswerEnabled>2</autoAnswerEnabled>
</autoAnswer>
<callWaiting>3</callWaiting>
<authName>308</authName>
<authPassword>PASsWORD16</authPassword>
<sharedLine>false</sharedLine>
<messageWaitingLampPolicy>1</messageWaitingLampPolicy>
<messagesNumber>*97</messagesNumber>
<ringSettingIdle>4</ringSettingIdle>
<ringSettingActive>5</ringSettingActive>
<contact>308</contact>
<forwardCallInfoDisplay>
<callerName>true</callerName>
<callerNumber>true</callerNumber>
<redirectedNumber>true</redirectedNumber>
<dialedNumber>true</dialedNumber>
</forwardCallInfoDisplay>
</line>
</sipLines>
<dialTemplate>dialplan.xml</dialTemplate>
</sipProfile>
<userLocale>
<name>English_United_Kingdom</name>
<langCode>en</langCode>
</userLocale>
<networkLocale>Germany</networkLocale>
<networkLocaleInfo>
<name>Germany</name>
</networkLocaleInfo>
</device>
11-17-2016 02:47 PM
Hold on ... Just looked at the SEPmacaddress.xml.cnf, and I've noticed a lot of missing information.
For example, one of the most glaring configuration issue is the "proxy". Depending on the firmware of the phone, by the way the phone firmware information is also missing from the configuration, means the line could be wrong.
I have attached a known working SEPmacaddress.cnf.xml which can be quickly modified to work with phones like 9951/9971, 8800 phones.
Alternatively, you can look at this old thread (HERE).
11-30-2016 04:00 AM
Thank you Leo. Got it working.
The only "problem" is that it's not showing the correct time. It shows -1 hour.
I'm in CET and I tried changing the timezone settings and in the web interface of the phone I can see that thay are accepted but the thime difference does not change.
Any idea why?
11-30-2016 05:50 PM
The only "problem" is that it's not showing the correct time. It shows -1 hour.
-1 hour and you are CET? This means the phone has defaulted into GMT/UTC/Zulu.
The only reason why the phone has defaulted to UTC is, possibly, because the data inside the <timeZone> could be incorrect. In the configuration file, what is the <timeZone> tag set to?
11-30-2016 11:15 PM
I tried several settings for the tag:
W. Europe Standard/Daylight Time
E. Europe Standard/Daylight Time
Central Europe Standard/Daylight Time
In the web interface of the phone I could see that the time zone was changing but the time shown was always the same.
12-01-2016 12:06 AM
Could be a bug with the choice of firmware version.
02-20-2020 08:24 AM
Hi, I've got an 8821 wifii phone working with Swithvox (the paid version of Asterisk). But there is no menu option for hold or transfer. Is there a setting for that in the .cnf.xml file?
Thanks!
11-30-2016 03:55 AM
So thanks to the files provided by Leo Laohoo I managed to get it working.
Thank you Leo!
I had to remove some stuff so in case someone else is having the same issue, trying to connect Cisco 8831 to an Asterisk server I'm attaching a working xml file (actually it's two files that you need).
Notes:
The file SEPmacaddress.cnf.xml needs to include the mac address of your phone in the name of the file.
In the file you need to change:
<processNodeName>IP_ADDRESS_OF_YOUR_ASTERISK_SERVER</processNodeName>
<phoneLabel>Conference</phoneLabel>
<featureLabel>Conference</featureLabel>
<authName>AUTH_FOR_INSTANCE_NUMBER_OF_EXTENSION</authName>
<authPassword>PASSWORD_FOR_AUTH</authPassword>
05-29-2018 10:09 PM
is there no need of SIPDefault.cnf file ?
07-12-2018 06:48 AM
I got this working kind of if anyone is still having an issue with the 8831,
One thing weird that's happening is that it gets synced to the exact minute and second, but hour stays at UTC/Zulu just like op.
I looked at your file and it has some entries for tzudpdater and its version? do you use this as is, or does one need to populate these fields for timezone to update.
My CTL and ITL are just blank 0 kb files if that matters, someone was mentioning that I might need to make these files for it to work, anyone with experience with timezone on this device have any info why only the hour is stuck, I can see a time 1/1/00 go to the correct date and but to UTC timezone instead of whats in there. Pacific Standard/Daylight Time or PST8PDT is what CUCM uses or anything at this point. Its using the latest firmware.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide