[asterisk-users] RPM updates

2013-01-28 Thread Steven Howes
Hi All, Who do I need to poke to get the yum repository / RPM files updated? The dahdi RPMs are not up to date with the CentOS kernel versions any more, it's making doing an installation a bit tricky due to dependancies, I'd rather not roll back / remove new kernels if I don't have to.. Cheers

Re: [asterisk-users] RPM updates

2013-01-28 Thread Anthony Messina
On Monday, January 28, 2013 01:55:09 PM Steven Howes wrote: > Who do I need to poke to get the yum repository / RPM files updated? The > dahdi RPMs are not up to date with the CentOS kernel versions any more, > it's making doing an installation a bit tricky due to dependancies, I'd > rather not rol

Re: [asterisk-users] RPM updates

2013-01-28 Thread Tzafrir Cohen
On Mon, Jan 28, 2013 at 01:55:09PM +, Steven Howes wrote: > Hi All, > > Who do I need to poke to get the yum repository / RPM files updated? The > dahdi RPMs are not up to date with the CentOS kernel versions any more, it's > making doing an installation a bit tricky due to dependancies, I'd

[asterisk-users] Configuration Required for Remove Queue Member

2013-01-28 Thread Ahmed Munir
I would like to know, is there a method in which we can define the timeout value for a member who already login to the queue but after quite a while if he didn't answer the 3-4 calls (not going to member pause queue) but automatically remove the member from the queue? Please advise. -- Regards,

Re: [asterisk-users] Asterisk 11- Answer with [m=image 0 udptl t38] and Call Drop

2013-01-28 Thread Matthew Jordan
On 01/26/2013 07:26 AM, Andreas Sikkema wrote: > On 1/18/13 13:24 , Matthew Jordan wrote: >> 1) Contact your carrier and ask why they are rejecting the 200 OK. >> >> 2) Assuming they won't change their behaviour, find out what they want >> in a response that declines an image media format. Without

Re: [asterisk-users] Asterisk 11- Answer with [m=image 0 udptl t38] and Call Drop

2013-01-28 Thread Andreas Sikkema
Matthew, > A part of me wonders is if you're really running into the issue > described on ASTERISK-20908 [1]. Do you mind trying the patch on there > to see if it helps? The problem is that some customers of mine (erm ours) who are running an Asterisk based sot PBX are having some issues that are