[OpenSIPS-Users] handling a 422
Alex Balashov
abalashov at evaristesys.com
Tue Aug 18 15:10:50 CEST 2009
The SST module is designed for a scenario in which the proxy serves as
the endpoint of the SST negotiation. Otherwise, SST is up to the UA
endpoints to negotiate amongst themselves. So, SST does not deal with a
situation in which the proxy *receives* a 422; it only equips the proxy
to *send* a 422 if the Min-SE value from the request initiator does not
meet *its* desiderata.
Jeff Pyle wrote:
> It seems very strange to me to have to manually manipulate headers that an
> Opensips module added in the first place. Seems like bad things could
> happen if the modules expects them to be there with certain values and they
> have different values or gone altogether. If these headers are added in the
> request route does the same rule apply as with append_hf(), that is, they
> cannot be removed?
>
> The whole thing just seems odd.
>
>
> - Jeff
>
>
>
> On 8/18/09 9:01 AM, "Alex Balashov" <abalashov at evaristesys.com> wrote:
>
>> If I'm understanding the documentation correctly, you'd probably have to
>> do this with manual header manipulation.
>>
>> Jeff Pyle wrote:
>>
>>> On 8/18/09 8:51 AM, "Alex Balashov" <abalashov at evaristesys.com> wrote:
>>>
>>>> Sure, use a failure route and append_branch().
>>> Ok, but how do I adjust the timer value so it doesn't get 422'd again? Or
>>> is this handled automatically? The SST module documentation doesn't appear
>>> to cover this.
>>>
>>>
>>>
>>> - Jeff
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Alex Balashov - Principal
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
More information about the Users
mailing list