The attr2uri problem can be fixed, if I use:
attr_destination ("$tmp");
after attr2uri.
Now, I only have to find out, how SER cancel the additional branch, if the
first one will reject the call.
Idea: If one branch answers (200 Ok), SER will send a CANCEL. Maybe I can patch
the source code at this point, so that every status code > 200 (not only ==200)
send a CANCEL?
Philipp
Am 05.01.2014 um 20:38 schrieb Philipp Hoffmann <[email protected]>:
> Hello Carsten,
>
> I run SER 2.0.0, no Kamailio. As far as I remember, you cannot use SER
> configuration on Kamailio without several changes.
>
> Is there no way to forward the reject SIP message from one of the branches to
> the caller and cancel the other branch without the tmx-module, if SER gets
> one?
>
> Philipp
>
> Am 05.01.2014 um 20:20 schrieb Carsten Bock <[email protected]>:
>
>> Hi,
>>
>> what Version of SER are you using? The recent versions have an
>> "tmx"-module, which might have the function you're looking for:
>>
>> t_cancel_branches("all");
>> http://kamailio.org/docs/modules/4.1.x/modules/tmx.html#idp1881656
>>
>> You just have to trigger this upon the according reply.
>>
>> Kind regards,
>> Carsten
>>
>> 2014/1/5 Philipp Hoffmann <[email protected]>:
>>> I think the problem is to call t_relay() in onreply route after
>>> append_branch().
>>>
>>> Furthermore, SER needs to cancel the additional branch, if the subscriber
>>> does not accept the call (e. g. with 404 Not found) AFTER sending 180
>>> Ringing. Normally, SER ignores 404 Not found in this case, because the
>>> additional branch still rings.
>>> Can I send a CANCEL to the second branch if we receive a 4xx or 5xx message
>>> from the first one?
>>>
>>> If I set up the additional branch with append_branch() and attr2uri(…), SER
>>> sends the first AND second INVITE to the subscriber, even the second has got
>>> another request uri. If I use append_branch() and seturi(…) all works fine.
>>> Maybe this is a bug in attr2uri()?
>>>
>>> Philipp
>>>
>>> Am 05.01.2014 um 11:29 schrieb Philipp Hoffmann <[email protected]>:
>>>
>>> if(t_check_status(„180“)) {
>>> append_branch ("sip:early_announce@localhost:5080");
>>> }
>>>
>>> If I do so in on reply route, SER does not correctly set up the additional
>>> branch. I cannot see any SIP message to SEMS in trace.
>>>
>>> Regards
>>> Philipp
>>>
>>> Am 05.01.2014 um 10:30 schrieb Juha Heinanen <[email protected]>:
>>>
>>> Stefan Sayer writes:
>>>
>>> create an additional branch on SER to SEMS, and use the early_announce
>>> (without continue_b2b) or early_dbprompt or
>>> doc/dsm/examples/early_media.dsm application in SEMS. You might also
>>> want to loop the ringtone.
>>>
>>>
>>> If callee is busy or not available, then this additional branch might
>>> still ring giving wrong signal to caller. Caller should hear ringing
>>> sound only after callee responds with 180 ringing. So the additional
>>> branch should be added in reply route when SER receives 180.
>>>
>>> might even be possible with the new sbc/dsm call control if you need
>>> to have 200 for the ring back tone already, but for other uses, the
>>> above method is far easier and cleaner.
>>>
>>>
>>> I too noticed a couple of weeks ago that dsm/mods/mod_sbc was
>>> introduced. It sounds like a very useful module possibly allowing
>>> implementation of a more flexible sbc than what sbc application offers.
>>>
>>> It would be nice to have a Readme.mod_sbc.txt or an example dsm where
>>> mod_sbc is used.
>>>
>>> -- Juha
>>>
>>>
>>> _______________________________________________
>>> Sems mailing list
>>> [email protected]
>>> http://lists.iptel.org/mailman/listinfo/sems
>>>
>>>
>>>
>>> _______________________________________________
>>> Sems mailing list
>>> [email protected]
>>> http://lists.iptel.org/mailman/listinfo/sems
>>>
>>
>>
>>
>> --
>> Carsten Bock
>> CEO (Geschäftsführer)
>>
>> ng-voice GmbH
>> Schomburgstr. 80
>> D-22767 Hamburg / Germany
>>
>> http://www.ng-voice.com
>> mailto:[email protected]
>>
>> Office +49 40 34927219
>> Fax +49 40 34927220
>>
>> Sitz der Gesellschaft: Hamburg
>> Registergericht: Amtsgericht Hamburg, HRB 120189
>> Geschäftsführer: Carsten Bock
>> Ust-ID: DE279344284
>>
>> Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
>> http://www.ng-voice.com/imprint/
>
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
