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
