Thanks!
----- Original Message -----
From: Andrzej Ciarkowski
To: Roee Vulkan
Cc: [email protected]
Sent: Wednesday, January 03, 2007 9:15 AM
Subject: Re[2]: [sipxtapi-dev] SIP/SIMPLE "MESSAGE"
>
Thanks!
Can you please elaborate on the workarounds you mentioned?
(implementation guidelines for a newbie).
>
Is there a way to use sipxtapi/sipxtacklib to create a new type of sip
message or to override the headers and body of existing messages?
In the attached patches you will find workarounds for the following issues:
- failure on proxy authorization (ignoring the 407 response)
- added "callback user data" pointer
- support for "Subject" header in both inbound and outbound messages - you
can use similar code to override the headers and body of your messages.
Hovewer, I didn't solve the problem of possible blocking in
sendPagerMessage().
Regards,
Andrzej Ciarkowski
>
----- Original Message -----
From: Andrzej Ciarkowski
To: Roee Vulkan
Cc: [email protected]
Sent: Wednesday, January 03, 2007 8:48 AM
Subject: Re: [sipxtapi-dev] SIP/SIMPLE "MESSAGE"
>
Is there a way to use sipXtapi to send SIMPLE "MESSAGE" primitive?
Hello,
there is a class SipPimClient in sipXtack which could be used for this
purpose, however be warned that in some scenarios it won't work properly. The
main problem is that many SIP proxies will ask for authorization before sending
a MESSAGE. In such case SipPimClient will (incorrectly) return failure. Other
deficiency is the blocking nature of sendPagerMessage() function. If for any
purpose you don't get the answer for your MESSAGE request, the function will
block infinitely. Another problem is that you can't set the "user data" for the
callback used for receiving incoming messages, which forces you to use global
variables. However, it's not very hard to write some workarounds for most of
these problems.
Best Regards,
Andrzej Ciarkowski
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
