from SIP pov, the second call leg will be a completely new call, so it is correct that the iptel.org proxy challenges that call with 407.
whether you want to have SEMS autheticate that call leg depends on the application. e.g. if this were a service line type of app, you would usually use IP auth for SEMS at your proxy Hallow calls from SEMS IP:port without authentication). I think (but may be mistaken) you can also set auth credentials on the DSM connectCallee function, check the examples and the docs. i know for sure that you can do that on dlg.dialout() Stefan On 4/4/11, Jason b.a <[email protected]> wrote: > > i still have a problem with connectCallee, i have 2 xlite and sems , all of > them registered with iptel users, am calling > sems from xlite1 , xlite1 enter the digit correctly and go to the state > where am calling : > B2B.connectCallee("sip:[email protected]","sip:[email protected]"); > > SEMS is sending : INVITE sip:[email protected] SIP/2.0 > but receiving a : SIP/2.0 407 Proxy Authentication Required from > xlite 2 > > PS: xlites send outbound via proxy : sip.iptel.org > > so what is the problem here ! > thx ! _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
