o Alex Mikh on 06/23/2011 05:15 PM:
> the DSM B2B.connectCallee() action does not support authentication for
> the second call leg.
>
> You can either place an outgoing call using dlg.dialout from mod_dlg
> and connect the two calls by joining the audio.
>
> Or you can route the call through the sbc module (in the same SEMS
> instance or in another), which can do SIP authentication - use the
> auth_sbc profile (auth_b2b.sbcprofile.conf) which works with the way
> you set the headers; you would possibly use something like:
>
> B2B.setHeaders("P-App-Param:
> u=myuser;d=iptel.org;p=mypass\r\nP-App-Name: sbc",true)
> B2B.connectCallee("sip:[email protected]:5080",
> "sip:[email protected]:5080")
>
> hth
I am using DSM, is it possible to use sbc too, i didnt find this
module in the plugins folders.
upgrade to newer sems version, e.g. 1.4.1
However, in auth_b2b application it is written that
the account App-Param (user/domain/pwd) can be set in auth_b2b.conf.
and in auth_b2b.conf : If this is not set, the account is taken from
P-App-Param header.
so should'nt work if we load the module and put the info in! it is
you need to route the call once through sems itself to activate the
sbc appliciation with auth_b2b sbcprofile, or the auth_b2b application.
that's why I added the P-App-Name: sbc header, and sent it to localhost.
Stefan
sending the frist invite, but not the second!
and if wont work, how can i load auth_sbc profile .
Best Regards,
Alex
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
