[asterisk-users] Cisco IP Phones and Skinny in asterisk 1.8.4.2 "tooooooooooooooooo"

[Alexandre Rodrigues]

Solve it. :)
Found this link: http://www.voip-info.org/wiki/view/SCCP-HOWTO2

Cheers,
Alex

2012/3/22 Alexandre Rodrigues <alex454 at gmail.com>:
> Hello,
>
> Facing the same problem with the following debug skinny log:
>
>   -- Asked to indicate 'Stop tone' condition on channel Skinny/500 at duba-23
>  Received Alarm Message: 32: Name=SEP001XXXXX Load= SCCP11.8-3-4SR1S :
> Invalid SCCP message! : ID :83
>  Received Alarm Message: 32: Name=SEP001XXXXX Load= SCCP11.8-3-4SR1S :
> Invalid SCCP message! : ID :83
>
> Did you solved the problem?
>
> Thanks in advance,
>
> Alex,
>
> 2011/6/25 bilal ghayyad <bilmar_gh at yahoo.com>:
>> Hi All;
>>
>> Again, the Cisco IP Phones 7942G and using Skinny:
>>
>> I upgraded the firmware to version 8.5 (skinny) and I am using skinny channel (chan_skinny) and the skinny.conf file.
>>
>> The phones are registering, but when we use them to place a call, we only hear tooooooooooo in the handset and we do not hear voice (even when we dial the digits, we only hear toooooooo .. but it dials and destination answer).
>>
>> Also if we call to these phones, and we pickup handset of the 7942G, I am hearing toooooooooo and no voice (no one hear voice .. source and destination are not hear).
>>
>> What about be? Is it related to skinny channel that does not work?
>>
>> In that case, skinny channel is not working fine and that means, I have to use SIP !
>>
>> Did any one face like this problem?
>>
>> Another problem, if I did changes in the extensions.conf and I need to reload, then I can not reload only the extensions.conf, I have to do reload and that will cause a reset for the Phones.
>>
>> Any advise? Did anyone tried skinny and faced those problems?
>>
>> Regards
>> Bilal
>>
>>
>> ----------------
>>> wow I think someone needs to just spend some time reading
>>> and playing. Getting these phones working is not rocket
>>> science and there are similarities with how to do firmware /
>>> config pushes.
>>>
>>> Not to sound mean but RTFM
>>>
>>> Sent from my iPhone
>>>
>>> On Jun 21, 2011, at 7:45 PM, Warren Selby <wcselby at selbytech.com>
>>> wrote:
>>>
>>> > On Tue, Jun 21, 2011 at 5:35 PM, bilal ghayyad <bilmar_gh at yahoo.com>
>>> wrote:
>>> > Dear Warren;
>>> >
>>> > Please, keep all discussions to the list.
>>> There's no need to email me personally about this.
>>> >
>>> > <snip>
>>> >
>>> > cmterm-7942_7962-sip.9-2-1.cop.sgn (which is written
>>> that it is SIP IP Phone load) and
>>> cmterm-7942_7962-sip.9-2-1.zip which is written that it is
>>> SIP IP Phone firmware files only. So what is the difference
>>> between them "the load and the firmware"?
>>> >
>>> > The .sgn file is basically just a zip container that
>>> the Cisco Call Manager uses.  You'll want to grab the
>>> zip file, extract the contents of the file into your tftp
>>> root directory.  The latest firmware that I've used was
>>> 8.5.2, in which most everything I needed worked for
>>> me.  I don't know specifics about the later versions of
>>> Cisco's SIP releases.
>>> >
>>> > Now, when I need to do the upgrade for the Phone, then
>>> I have to determine in the xml files the needed firmware?
>>> >
>>> > You should have, at least with firmware 8.5.2, the
>>> following files in your tftproot directory after unzipping
>>> the zip file:
>>> >
>>> > apps41.8-5-2TH1-9.sbn
>>> > cnu41.8-5-2TH1-9.sbn
>>> > cvm41sip.8-5-2TH1-9.sbn
>>> > dsp41.8-5-2TH1-9.sbn
>>> > jar41sip.8-5-2TH1-9.sbn
>>> > SIP41.8-5-2S.loads
>>> > term41.default.loads
>>> > term61.default.loads
>>> > XMLDefault.cnf.xml
>>> > SEP[_MAC-ADDR_].cnf.xml
>>> >
>>> > I provide samples of the last two files on the blog
>>> post mentioned earlier.  The last file, that starts
>>> with SEP, should contain the actual mac address of the phone
>>> you are trying to provision.  So, for example, it would
>>> be SEP0003C9DD5624.cnf.xml, if the mac address of your phone
>>> was 0003.C9DD.5624.  The example files are pretty much
>>> all you need, just go through them and change any location
>>> specific variables (such as _USER_, _IPADDR_, or _PASSWD_)
>>> to the proper values for your environment.
>>> >
>>> > Once you've got your tftp server setup properly with
>>> all of the appropriate config files, plug your phone in and
>>> follow the instructions at the bottom part of my blog post
>>> that explain how to get the phone reflashed to the SIP image
>>> and registered to your asterisk server.
>>> >
>>> >
>>> > --
>>> > Thanks,
>>> > --Warren Selby, dCAP
>>> > http://www.SelbyTech.com
>>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> New to Asterisk? Join us for a live introductory webinar every Thurs:
>>               http://www.asterisk.org/hello
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-users