On 18.03.11 10:48, Alekzander Spiridonov wrote:
> No, not at the moment.
Is it in roadmap?
Not either :-(
We have lots of sip-gateways that put some random values in SIP
contact field in SIP 200 OK, so we're unable to send a Re-Invite on
such request uri.
This quite bad... Where is the BYE sent then?
Thank you for suggesting a solution.
P.S.: Is there a full list of predefined variables (such as@user, #key)?
For which application / API ? Do you mean in DSM?
-Raphael.
2011/3/18 Raphael Coeffic <[email protected] <mailto:[email protected]>>
On 18.03.11 10:16, Alekzander Spiridonov wrote:
Sorry, the question was about B2B.connectCallee
No, not at the moment. In fact, unless you want to process the
audio on both sides (transcoding might be needed), you want both
endpoints to agree on a common codec.
If you want to connect any endpoints together, without having to
ever re-invite anyone, you could also (mis-)use the conference
mixer for this purpose.
But be aware that each and every call will be decoded and
re-encoded afterwards in SEMS.
Cheers
Raphael.
2011/3/18 Alekzander Spiridonov <[email protected]
<mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>
Hi again =)
Is there any way to forbid sems to do Re-Invite
during B2BconnectCallee()? Can't find any mentions in docs.
-- Best regards,
Alekzander Spiridonov
--
С уважением,
Александр Спиридонов
_______________________________________________
Sems mailing list
[email protected] <mailto:[email protected]>
http://lists.iptel.org/mailman/listinfo/sems
--
С уважением,
Александр Спиридонов
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
