On 3.3.2010 16:36, Jarod Neuner wrote:
> Calls to nua_respond, or any other method that sends or receives a response,
> should always be considered an async operation. A reasonable approach would
> be to use the memory home associated with that handle (nua_handle_home) to
> allocate the data -
Hello,
the culprit was a deadlock in my code that got freed only after a call
termination. The problem is solved now.
Thanks to anybody who spent time reading / thinking about the previous mail.
Regards
Martin
--
Downloa
Hello all,
As you might have noticed I've not spent much time with Sofia SIP
lately. However, Sofia SIP has not been abandoned completely. From now
on, I have reserved some time specifically to maintaining Sofia SIP
and following this mailing list.
--
Pekka.Pessi mail at nokia.com
-
2010/3/11 Trevor Nunes :
> I'm trying to send encapsulated 3GPP2 MO-SMS ( CDMA text message ). To do
> this the first byte of the payload must be 0x00, if I use SIP_PAYLOAD_STR(
> data ) and first byte is zero it seems to truncate assuming the 0x0 is a
> NULL terminator.
>
> I've tried using SIP_PA
2010/3/12 Martin Drasar :
> On 3.3.2010 16:36, Jarod Neuner wrote:
>> Calls to nua_respond, or any other method that sends or receives a response,
>> should always be considered an async operation. A reasonable approach would
>> be to use the memory home associated with that handle (nua_handle_h
The problem is I can send any type of content I want as long as the first
byte is not 0x00 ... If this byte is 0x00 it will send a 0 byte SIP message
out. So for example here is a short message that works perfectly, If I
change the payload[0] = 0x02 line to payload[0] = 0x00 an empty Content
Lengt
2010/3/8 Ronny Aruch :
> I use sofia 1.12.8.
> How can I suppress Content Disposition header from being sent.
> I added SIPTAG_CONTENT_DISPOSITION(NULL)to NUA_INVITE but the header is
> still sent.
It seems to me that there is no way to do that above the API, you have
to hack inside the stack.
2010/3/9 Aleksander Morgado :
> My humble request is then, please make the sigcomp plugin for sofia-sip
> free software, publicly available for everyone, so that we can keep on
> developing applications using the sofia-sip stack also including SigComp
> support.
I'll have a peek on the libraries a
Dne 12.3.2010 17:50, Pekka Pessi napsal(a):
> 2010/3/12 Martin Drasar :
>> On 3.3.2010 16:36, Jarod Neuner wrote:
>>> Calls to nua_respond, or any other method that sends or receives a
>>> response, should always be considered an async operation. A reasonable
>>> approach would be to use the mem
