18 Apr
2007
18 Apr
'07
4:44 a.m.
Hello openser users,
I'm trying to do something with openser but I haven't been able to
figure out how to do this. So I hope somebody on the list knows the
answer:
In my configuration script I use append_hf to add application data to
the SIP messages, this works great until the moment where I do a
parallel branch. The invites work just fine since I can do the append_hf
in the branch_route. The problem arises when one of the branches is
answered, at this point OpenSER will generate CANCEL messages for the
other branches and I have no clue on how to add header fields with
information about the original invite to those messages.
So my question is: Does somebody know how you can add headers with data
to the CANCEL messages generated by SER in a parallel branch? Thanks in
advance.
Kind regards,
Ardjan Zwartjes.
18 Apr
18 Apr
4:51 a.m.
Hi Ardjan,
you cannot do this as the CANCEL is automatically internally generated
and you do not have any access to it.
regards,
bogdan
Ardjan Zwartjes wrote:
Hello openser users,
I'm trying to do something with openser but I haven't been able to
figure out how to do this. So I hope somebody on the list knows the
answer:
In my configuration script I use append_hf to add application data to
the SIP messages, this works great until the moment where I do a
parallel branch. The invites work just fine since I can do the append_hf
in the branch_route. The problem arises when one of the branches is
answered, at this point OpenSER will generate CANCEL messages for the
other branches and I have no clue on how to add header fields with
information about the original invite to those messages.
So my question is: Does somebody know how you can add headers with data
to the CANCEL messages generated by SER in a parallel branch? Thanks in
advance.
Kind regards,
Ardjan Zwartjes.
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
5:04 a.m.
Hi Bogdan,
Thanks for your quick answer, though it's not what I hoped for ;). I
assume you mean that this message is unaccessible from within the
configuration script, do you know how much work it would be to access
this message from within the source code? Is it possible to write a
module that does this or do I really need to modify the core?
Kind regards,
Ardjan.
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro]
Sent: woensdag 18 april 2007 10:51
To: Ardjan Zwartjes
Cc: users(a)openser.org
Subject: Re: [Users] Adding headers to the CANCEL messages
generated by openser
Hi Ardjan,
you cannot do this as the CANCEL is automatically internally
generated
and you do not have any access to it.
regards,
bogdan
Ardjan Zwartjes wrote:
Hello openser users,
I'm trying to do something with openser but I haven't been able to
figure out how to do this. So I hope somebody on the list knows the
answer:
In my configuration script I use append_hf to add
application data to
the SIP messages, this works great until the
moment where I do a
parallel branch. The invites work just fine since I can do
the append_hf
in the branch_route. The problem arises when one
of the branches is
answered, at this point OpenSER will generate CANCEL
messages for the
other branches and I have no clue on how to add
header fields with
information about the original invite to those messages.
So my question is: Does somebody know how you can add
headers with data
to the CANCEL messages generated by SER in a
parallel
branch? Thanks in
advance.
Kind regards,
Ardjan Zwartjes.
_______________________________________________
Users mailing list
Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users
6:55 a.m.
Hi Ardjan,
well...you will need to do some work in TM module because it is
responsible for CANCEL generation, but I cannot make any kind of estimation.
Regards,
bogdan
Ardjan Zwartjes wrote:
Hi Bogdan,
Thanks for your quick answer, though it's not what I hoped for ;). I
assume you mean that this message is unaccessible from within the
configuration script, do you know how much work it would be to access
this message from within the source code? Is it possible to write a
module that does this or do I really need to modify the core?
Kind regards,
Ardjan.
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro]
Sent: woensdag 18 april 2007 10:51
To: Ardjan Zwartjes
Cc: users(a)openser.org
Subject: Re: [Users] Adding headers to the CANCEL messages
generated by openser
Hi Ardjan,
you cannot do this as the CANCEL is automatically internally
generated
and you do not have any access to it.
regards,
bogdan
Ardjan Zwartjes wrote:
Hello openser users,
I'm trying to do something with openser but I haven't been able to
figure out how to do this. So I hope somebody on the list knows the
answer:
In my configuration script I use append_hf to add
application data to
the SIP messages, this works great until the
moment where I do a
parallel branch. The invites work just fine since I can do
the append_hf
in the branch_route. The problem arises when one
of the branches is
answered, at this point OpenSER will generate CANCEL
messages for the
other branches and I have no clue on how to add
header fields with
information about the original invite to those messages.
So my question is: Does somebody know how you can add
headers with data
to the CANCEL messages generated by SER in a
parallel
branch? Thanks in
advance.
Kind regards,
Ardjan Zwartjes.
_______________________________________________
Users mailing list
Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users
8:42 a.m.
Hi Bogdan,
I guess that changing the TM module is a bit too much work for this
purpose. I'll try to find another solution for what I'm doing. Thanks
for the information.
Kind regards,
Ardjan.
-----Original Message-----
From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro]
Sent: woensdag 18 april 2007 12:56
To: Ardjan Zwartjes
Cc: users(a)openser.org
Subject: Re: [Users] Adding headers to the CANCEL messages
generated by openser
Hi Ardjan,
well...you will need to do some work in TM module because it is
responsible for CANCEL generation, but I cannot make any kind
of estimation.
Regards,
bogdan
Ardjan Zwartjes wrote:
Hi Bogdan,
Thanks for your quick answer, though it's not what I hoped
for ;). I
assume you mean that this message is unaccessible
from within the
configuration script, do you know how much work it would be
to access
this message from within the source code? Is it
possible to write a
module that does this or do I really need to modify the core?
Kind regards,
Ardjan.
> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro]
> Sent: woensdag 18 april 2007 10:51
> To: Ardjan Zwartjes
> Cc: users(a)openser.org
> Subject: Re: [Users] Adding headers to the CANCEL messages
> generated by openser
>
>
> Hi Ardjan,
>
> you cannot do this as the CANCEL is automatically internally
> generated
> and you do not have any access to it.
>
> regards,
> bogdan
>
> Ardjan Zwartjes wrote:
>
>> Hello openser users,
>>
>> I'm trying to do something with openser but I haven't been able to
>> figure out how to do this. So I hope somebody on the list
knows the
>> answer:
>> In my configuration script I use append_hf to add
>>
> application data to
>
>> the SIP messages, this works great until the moment where I do a
>> parallel branch. The invites work just fine since I can do
>>
> the append_hf
>
>> in the branch_route. The problem arises when one of the
branches is
>> answered, at this point OpenSER will
generate CANCEL
>>
> messages for the
>
>> other branches and I have no clue on how to add header
fields with
>> information about the original invite to
those messages. So my
>> question is: Does somebody know how you can add
>>
> headers with data
>
>> to the CANCEL messages generated by SER in a parallel
>>
> branch? Thanks in
>
>> advance.
>>
>> Kind regards,
>> Ardjan Zwartjes.
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6282
days inactive
6282
days old
4 comments
2 participants
participants (2)
-
Ardjan Zwartjes -
Bogdan-Andrei Iancu