[Spce-user] Fwd: Re: Blacklist t.38 fax codec

Daniel Grotti dgrotti at sipwise.com
Thu Jun 26 04:44:13 EDT 2014


Ok,
What client is that which is not support T38 negotiation.
Sorry, but you have to fix a client issue on server side, this is
something awkward.

So you should remove that T38 codecs then.
The following module may help:

http://kamailio.org/docs/modules/4.0.x/modules/sdpops.html

Try to have a look at this.

Daniel



On 06/26/2014 10:18 AM, Leopoldo Iglesia wrote:
> When the proxy answer the 488, next packet is other invite.. and no more.
>
> The problem is that the SDP packet comes withh all codecs like this
>
>
>
> El 20/06/2014 14:09, Daniel Grotti escribió:
>> Hi,
>> If you want to discard all INVITEs with T38, you can try to add
>> something like that in your
>> /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.customtt.tt2:
>>
>>
>> if(is_method("INVITE") && search_body("udptl"))
>> {
>>    sl_send_reply("488", "Not Acceptable Here");
>>    exit;
>> }
>>
>> before to send the invite to ROUTE_INVITE.
>> Then run "ngcpcfg apply".
>>
>> So, each INVITE/REINVITE with udpl in their body will be discarded.
>>
>>
>> Daniel
>>
>>
>>
>>
>> On 06/20/2014 01:35 PM, Daniel Grotti wrote:
>>> I have nothing ready to give you right now.
>>> Basically on kamailio proxy you should match a Re-invite (using the
>>> "has_totag") and check if SDP contains t38 headers/codec (just have
>>> a look how the T38 reinvite looks like).
>>> So, if you receive a re-invite with T38 headers into SDP, just send
>>> back a 488 reply.
>>>
>>> Daniel
>>>
>>>
>>>
>>>
>>>
>>> On 06/20/2014 01:28 PM, Leopoldo Iglesia wrote:
>>>> Fine, how can I do this hack? cause endpoints is impossible to mod
>>>> config, so they are rented and provisioned by an ftth operator.
>>>>
>>>> El 20/06/2014 13:23, Daniel Grotti escribió:
>>>>> Hi,
>>>>> I think you need to avoid to forward the T38 Re-INVITE, so you
>>>>> should hack your SPCE in order to reply to the T38 re-invite with
>>>>> a "488 Not acceptable here", for example.
>>>>> So the sender SHOULD fallback to G711.
>>>>> Anyway, the best solution if you have endpoint with t38 enabled
>>>>> but they don't work well, is to disable t38.
>>>>>
>>>>>
>>>>> Daniel
>>>>>
>>>>>
>>>>>
>>>>> On 06/20/2014 01:15 PM, Leopoldo Iglesia wrote:
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>> 	
>>>>>>
>>>>>>
>>>>>> > But both endpoints support it, that is the problem and the only
>>>>>> > scenario when it fails, so i want SPCE not to send Fax
>>>>>> negotiation to > endpoint,.
>>>>>>
>>>>>>
>>>>>>
>>>>>>  El 20/06/2014 12:12, Daniel Grotti escribió: >> Hi, >> that's
>>>>>> strange, if one of the endpoints try to switch to t38 and the >>
>>>>>> other endpoint doesn't support it, they should fallback to G711.
>>>>>> >> >> Daniel >> >> >> >> >> >> >> On 06/20/2014 01:33 AM,
>>>>>> Leopoldo Iglesia wrote: >>> How can I, blacklist t.38 to avoid
>>>>>> endpoints to try t38 negotiation? >>> >>> When i call from
>>>>>> ericcson ont to fax capable endpoint, it try to >>> connect t38
>>>>>> fax and There is no voice. >>> >>> Thanks >>> >>> Leopoldo
>>>>>> iglesia >>> >>> _______________________________________________
>>>>>> >>> Spce-user mailing list >>> Spce-user at lists.sipwise.com >>>
>>>>>> http://lists.sipwise.com/listinfo/spce-user >> >>
>>>>>> _______________________________________________ >> Spce-user
>>>>>> mailing list >> Spce-user at lists.sipwise.com >>
>>>>>> http://lists.sipwise.com/listinfo/spce-user > >
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Spce-user mailing list
>>>>>> Spce-user at lists.sipwise.com
>>>>>> http://lists.sipwise.com/listinfo/spce-user
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> http://lists.sipwise.com/listinfo/spce-user
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> http://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140626/91d30181/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 228494 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140626/91d30181/attachment-0001.png>


More information about the Spce-user mailing list