why

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well, I received a clear message from digium about G729, no support for 
trunk or pre-releases of asterisk...
Even if I have paid licences.

Wait and see, I'll have soon E1 cards with hardware echo canccellation, 
hope it will helps :)

Thx for all anyway,

Olivier

Matthew Fredrickson a ?crit :
> olivier taylor wrote:
>> what do you mean by a better software echo canceller?
>> I use the standard one in dahdi, wich is better?
>> Oslec doesn't seems available for dahdi.
>
> OSLEC was what I was thinking of... although whether or not there is a 
> patch for DAHDI to use OSLEC I do not know.
>
>> In fact the problem came when I needed G729, not supported and not 
>> available by Digium for trunk and 1.6
>
> 1.6.0 will be released soon, so you definitely will have one then.  
> I'm not sure whether or not they have a 1.6 pre-release of the g.729 
> binary.  I'll look into this.
>
> Matthew Fredrickson
> Digium, Inc.
>
>> I tried to install the last version of asterisk, libss7, and dahdi.
>> Since, I have echo problem I didn't had before.
>>
>>
>> Olivier
>>
>> Matthew Fredrickson a ?crit :
>>> olivier taylor wrote:
>>>> echocancel is set, the exact message is :
>>>
>>> Ok, this means that you either need to try to use a different/better 
>>> software echo canceller or you need to get a hardware echo canceller 
>>> that will perform better.  Thanks for checking that, we just had a 
>>> problem a while ago where the echo canceller wasn't being turned 
>>> when calls came in (in a particular scenario) and I wanted to make 
>>> sure that that wasn't happening again.
>>>
>>> Matthew Fredrickson
>>> Digium, Inc.
>>>
>>>>
>>>> uu212-190-xx-xxx*CLI> dahdi show channel 2
>>>> Channel: 267-183*CLI>
>>>> File Descriptor: 22
>>>> Span: 1
>>>> Extension: 7-183*CLI>
>>>> Dialing: no
>>>> Context: default
>>>> Caller ID:
>>>> Calling TON: 0
>>>> Caller ID name:
>>>> Mailbox: none
>>>> Destroy: 0
>>>> InAlarm: 0
>>>> Signalling Type: SS7
>>>> Radio: 00-67-183*CLI>
>>>> Owner: DAHDI/2-1
>>>> Real: DAHDI/2-1 (Linear)
>>>> Callwait: <None>
>>>> Threeway: <None>
>>>> Confno: -1
>>>> Propagated Conference: -1
>>>> Real in conference: 0
>>>> DSP: yes
>>>> Busy Detection: no
>>>> TDD: no
>>>> Relax DTMF: no
>>>> Dialing/CallwaitCAS: 0/0
>>>> Default law: alaw
>>>> Fax Handled: no
>>>> Pulse phone: no
>>>> DND: no
>>>> Echo Cancellation:
>>>>    128 taps
>>>>    currently ON
>>>> CIC: 2
>>>> Actual Confinfo: Num/0, Mode/0x0000
>>>> Actual Confmute: No
>>>> Hookstate (FXS only): Onhook
>>>>
>>>>
>>>> Matthew Fredrickson a ?crit :
>>>>> olivier taylor wrote:
>>>>>>
>>>>>>
>>>>>> Matthew Fredrickson a ?crit :Well, I am quite happy with libss7, 
>>>>>> no real reasons to change for me.
>>>>>> But, I can't be sure and this is another problem, since I use 
>>>>>> chan_dadhi, I have big echo problems, it wans't the case with 
>>>>>> zaptel.
>>>>>> I am buying E1 cards with hardware echo canceller to avoid this 
>>>>>> problem because I didn't find any solution with Dahdi.
>>>>>> Tuning by rxgain/txgain makes the echo a bit better, but an echo 
>>>>>> still remain.
>>>>>
>>>>> I think I might have mentioned this in another email, so please 
>>>>> forgive me if I did, but when you have a call up with echo on it, 
>>>>> can you check `dahdi show channel x` where is is the DAHDI channel 
>>>>> that you are connected to and tell me if the echocancel: option is 
>>>>> set to something besides no?
>>>>>
>>>>> Thanks,
>>>>> Matthew Fredrickson
>>>>> Digium, Inc.
>>>>>
>>>>>>
>>>>>> Dunno if I am the only to have that problem.
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Olivier
>>>>>>> Krzysztof Drewicz wrote:
>>>>>>>  
>>>>>>>> Oakland, Alan napisa?(a):
>>>>>>>>  
>>>>>>>>> To further clarify, libss7 is developed by Digium, where 
>>>>>>>>> chan_ss7 is
>>>>>>>>> developed by a company called Dicea, more information on 
>>>>>>>>> chan_ss7 can be
>>>>>>>>> found on it's voip-info page
>>>>>>>>> http://www.voip-info.org/wiki/view/Asterisk+ss7+channels
>>>>>>>>>         
>>>>>>>> Also:
>>>>>>>>
>>>>>>>> chan_ss7 by Dicea has a cluster/failover capability where you 
>>>>>>>> have one SPC for you asterisk (one point code in SS7, just like 
>>>>>>>> one IP), and if used with 2 hosts, each one having at least one 
>>>>>>>> E1 to your SS7 peer , then (if your peer understands changeover 
>>>>>>>> and emergency changeover messages it's 99.99%)  one of your 
>>>>>>>> asterisk machines could do a reboot, and a second one will go on.
>>>>>>>>     
>>>>>>>
>>>>>>>
>>>>>>>  
>>>>>>>> libss7 has (am i correct) no official support, in other words: 
>>>>>>>> you cannot expect Digium Support (even with Asterisk Premium 
>>>>>>>> Edition) to solve your problems with libss7, they will help, 
>>>>>>>> but the response time etc... for ss7 is not in the contract.
>>>>>>>>     
>>>>>>>
>>>>>>> Regarding the current "official" support channel for libss7, 
>>>>>>> this is certainly no worse off than the lack of an official 
>>>>>>> support channel for chan_ss7.  And with libss7 you get the 
>>>>>>> benefit that the original author (myself) is still actively 
>>>>>>> maintaining and supporting it, as well as working with many of 
>>>>>>> you in the community with any problems you run into.
>>>>>>>
>>>>>>> There are still some policies and decisions we have to make 
>>>>>>> about how we're going to officially support libss7 though.  I 
>>>>>>> believe that when we make the official release of Asterisk-1.6.0 
>>>>>>> (Open source) installation support will be something you can 
>>>>>>> call support about (although it'll probably end up coming back 
>>>>>>> to me for a while, while the technical support staff are 
>>>>>>> learning how to support it).
>>>>>>>
>>>>>>> With regards to BE, I was asked a while ago about including 
>>>>>>> libss7 support in it.  At the time (this was probably a year or 
>>>>>>> year and half ago), I thought it wouldn't be a good idea, due to 
>>>>>>> maturity issues.  Now though, I feel that libss7 is to the point 
>>>>>>> where I would feel good about putting it in BE since, IMHO, it 
>>>>>>> has been proven as far as stability and performance goes.
>>>>>>>
>>>>>>> If there is enough interest in getting support for libss7 (i.e. 
>>>>>>> people would be willing to buy copies of it to use with libss7) 
>>>>>>> I can look into what it would take to get it in.
>>>>>>>
>>>>>>> -- 
>>>>>>> Matthew Fredrickson
>>>>>>> Digium, Inc.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>>>>>>
>>>>>>> asterisk-ss7 mailing list
>>>>>>> To UNSUBSCRIBE or update options visit:
>>>>>>>    http://lists.digium.com/mailman/listinfo/asterisk-ss7
>>>>>>>
>>>>>>>   
>>>>>>
>>>>>> ------------------------------------------------------------------------ 
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>>>>>
>>>>>> asterisk-ss7 mailing list
>>>>>> To UNSUBSCRIBE or update options visit:
>>>>>>    http://lists.digium.com/mailman/listinfo/asterisk-ss7
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>




[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite Backpacking]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux