Hello Stefan,

thanks for your reply.

I create an additional branch like this:

append_branch ("sip:[email protected]:5080“);

I have built a loop feature in EarlyAnnounce.cpp to repeat our alerting.wav 
every time.

But, if the subscriber sends 404 Not found, SER does not cancel the call to 
SEMS. The caller is still connected to SEMS. Do you have a hint to solve this 
problem?

Another question:

If I create the additional branch like this ...

append_branch ();
attr2uri ("$t.parallel");

... SER sends the first and second INVITE to the subscriber, even if the second 
invite contains a different SIP-URI.

How can I correct this?

Regards
Philipp


Am 04.01.2014 um 23:29 schrieb Stefan Sayer <[email protected]>:

> 
> Hello,
> 
> 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.
> 
> o Philipp Hoffmann on 01/04/2014 09:41 PM:
>> Maybe SEMS can send a ReINVITE if it gets 200 Ok to the class IV network?
> 
> 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.
> 
> Stefan
> 
>> 
>> Regards,
>> Philipp.
>> 
>>> Am 04.01.2014 um 21:34 schrieb Juha Heinanen <[email protected]>:
>>> 
>>> Philipp Hoffmann writes:
>>> 
>>>> we have SER, which is connected to our PSTN class IV switching
>>>> plattform. The class IV plattform is unable to provide a ringtone to
>>>> callers. This means, if a PSTN subscriber calls a customer on our SER,
>>>> the PSTN subscriber do not hear a ringtone. Is there a way to set up
>>>> the ringtone using SEMS in front of SER?
>>> 
>>> it might be possible to use sems to turn 180 ringing from phone behind
>>> ser to 188 session progress with early media, but sems would not know
>>> what the codecs supported by the phone are before it gets 200 ok from
>>> the phone.
>>> 
>>> -- 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

Reply via email to