RE: [reSIProcate] Need info on SipMessage.addHeader() arguments
i have mentioned this before and nobody seems to pay any
attention.
i needed it to implement the cisco specific NOTIFY for
dtmf.
I just maintain
my own little fork for this feature, but i think it would be useful enough to
add this flexibility into the DUM.
Im not asking to implement the functionality, just the
flexibility to the DUM.
i call onReadyToSend for both requests and
responses... I also added another virtual method to handle implied
subscriptions ( which the current DUM will reject )
Now i know im not the only person in the world that sees
value in this, at least the adorning of the Responses.
Jason,
Thanks for the link but I guess what I am really trying to
do is add a header to a response message while staying in DUM. Apparently
DialogUsage::onReadyToSend() would be perfect except that it only works for
requests. Is there a comparable way to add Call-Info to a
response?
BTW: You mentioned looking at Feature in DUM for adding
Call-Info,but I can't seem to understand what to do with it. Are there any or
details or sample code around??
Bill Kovar
Avaya Inc.
(732) 852-2609
http://wiki.resiprocate.org/wiki/index.php?title=Use_Overview
On 5/18/06, Kovar,
William (Bill) <bkovar@xxxxxxxxx> wrote:
Jason,
Thanks!
I looked
in the wiki and found nothing. Do you have a link to something
specific?
What's
h_CallInfo and where's it defined?
You wouldn't use the addHeader method directly. Have you looked at
http://wiki.resiprocate.org?
Here's how you would
add a Call-Info header.
SipMessage msg;
msg.header (h_CallInfo) =
Data("foobar");
On 5/18/06, Kovar,
William (Bill) <bkovar@xxxxxxxxx> wrote:
I'm looking to add a Header into a SIP
msg before sending it out and assume addHeader() is the right way to go.
However, the signature is confusing to me. Can someone explain the method
args??
SipMessage::addHeader(
Headers::Type header, // what's this??
Would it be GenericUri
const char*
headerName, // what's this?? Would it be
"Call-Info"
int
headerlen, //
I assume this is the length of headerName
const char*
start, // points to
header data, a.k.a. the 'info' part as per RFC3261
int
len) //
length of start
I'm not sure about the first 2 args. Can
someone set me right?
Also, if I'm adding a Call-Info header,
is everything that I want to add after the "Call-Info:" part in the 'start'
argument, including the info-param(s)? Or is there some special way to add
them in.
Thanks!!
Bill Kovar
_______________________________________________
resiprocate-devel
mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel