On Mon, Jun 27, 2011 at 9:06 AM, Michael <voip.quest...@gmail.com> wrote: > Hi Kevin, > > Controlling it through the sip.conf peers is sufficient for us for this case > (because this particular provider doesn't support T.38 at all), but I think > it would be a good idea to add the option to enable/disable T.38 from the > dialplan. If I recall correctly, that's how callweaver worked at the time. > > Also, we just checked it, and since for that provider, we have other codecs > in higher priorities (like GSM, for example) than G.711, G.711 was not > chosen as the only codec, so the fax transmission failed. We can not > prioritize G.711 over the other codecs in the sip.conf, for the obvious > reasons, so for this, we need to do it in the dialplan. How can we do it?
Obvious solution is to move this particular number off this particular provider to a provider where you don't require prioritizing GSM and where that provider properly supports T.38. Outside of that idea, you would have to do some edge SIP routing before the call hit asterisk, to deflect this particular call to an asterisk configured differently. You could do that with OpenSIPS for example. Doesn't that sound like a lot more work than just porting the number to a different provider? Or if you insist on keeping the provider, get a second account with them for just this number, and you can apply different rules in sip.conf for just that account. -- _____________________________________________________________________ -- 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
