No subject

message. The required bits such as RURI and SDP all work as expected.

Group, feel free to correct me there. Depending on your specific setup
and network architecture, it should work. However, you may not be able
to do anything with the ISUP components of the messaging.

-Brett



On Thu, Feb 19, 2009 at 11:14 AM, Daviramos Roussenq Fortunato
<daviramosrf at gmail.com> wrote:
> Hi Alex.
>
> If a different protocol is not to say that you can connect directly to
> Asterisk and will work, just taking the resources of ISUP?
>
> SIP-T is not talking with SIP protocol are different, after all SIP-T
> carries information that the SIP can not interpret.
>
> The Problem is the following I get a SIP-T trunk and Asterisk to deliver
> precise, how best to do.
>
> 2009/2/19 Alex Balashov <abalashov at evaristesys.com>
>>
>> Not possible, Asterisk doesn't understand SIP-T.
>>
>> What do you mean by that, anyway?  Only a device that supports ISUP
>> interworking will support SIP-T.
>>
>> Secondly, as is often repeated here, SIP-T is a specification for a
>> _PAYLOAD_ - an extension - of SIP.  It is not a different protocol.
>>
>> Daviramos Roussenq Fortunato wrote:
>>
>>> Hi List.
>>>
>>>  I have a trunk SIP-T must deliver it to the Asterisk in SIP. The Opens
>>> is that?
>>> How should be my opensip.cfg?
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> --
>> Alex Balashov
>> Evariste Systems
>> Web    : http://www.evaristesys.com/
>> Tel    : (+1) (678) 954-0670
>> Direct : (+1) (678) 954-0671
>> Mobile : (+1) (678) 237-1775
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>