As SEMS will generate initial Register, you won't need any application. Just load reg_agent plug-in and edit reg_agent.conf file according to your needs (see example).
25 марта 2011 г. 16:16 пользователь Karimi-Cherkandi, Bizhan < [email protected]> написал: > Unfortunately the app that generates the Register cannot have knowledge > of credentials, so I prefer your idea of using sems as UAC. > to do this, I would need to load uac_auth library and have > application=uac_auth and what would be the corresponding conf file? I cannot > see any such conf file. > > thanks > > ------------------------------ > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *Alekzander Spiridonov > *Sent:* Friday, March 25, 2011 8:02 AM > > *To:* [email protected] > *Subject:* Re: [Sems] question on SBC module in SEMS 1.4 > > Well, first of all, Kamailio, as a SIP Proxy, must forward 401 to UAC (your > internal app) and UAC should generate Register with credentials. Anyway, my > idea was to put credentials in reg_agent module and let SEMS to work as UAC. > > > Also, I've seen some treads about additional module for Kamailio that > allows it to send both simple Register and Register with credentials on 401. > > But I insist that the app generates initial Register should process 401 > reply from Registrar. > > 25 марта 2011 г. 14:50 пользователь Karimi-Cherkandi, Bizhan < > [email protected]> написал: > >> actually the scenario should be >> my internal entity generates register -----> kamalio forwards it to sems >> ----> sems forwards it to external sipserver >> I cannot have kamailio to send directly to external sipserver since >> external could challenge the Register. >> so kamailio is not generating the Register, it receives it. I already >> tried kamailio to send it to external sipserver, but once the external >> sipserver challenges it with a 401, then I expect kamailio to act like a >> b2bua and answer the 401 with generating the previous Register now with >> credentials, and kamailio cannot generate the previous Register. That is why >> I though of using sems. if sems could receive the Register and forward it to >> external sipserver then problem would be solved. if external sipserver >> challenges it, sems could handle it. >> How would this be solved using sems in UAC? you maybe right, please tell >> me what you have on your mind, >> >> Thanks >> >> ------------------------------ >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Alekzander Spiridonov >> *Sent:* Friday, March 25, 2011 7:41 AM >> >> *To:* [email protected] >> *Subject:* Re: [Sems] question on SBC module in SEMS 1.4 >> >> Kamailio is a SIP-Proxy. Do you use it to generate Register request? >> >> I'm not sure, whether SEMS can process Register requests correctly. >> I'think you'd better use SEMS as an UAC in Register session or send Register >> requests directly from Kamailio to external registrar. >> >> P.S.: Please, reply only to list, not on my own e-mail. Thank you. >> >> 25 марта 2011 г. 14:28 пользователь Karimi-Cherkandi, Bizhan < >> [email protected]> написал: >> >>> here is the scenario: >>> I am using kamailio as a sipserver. now I am trying to define a trunk gw >>> to interface to another sipserver. I need to Register to this second >>> sipserver and kamailio cannot do that since I would need it to act like a >>> b2bua and handle 401 among other things. so I thought I use sems to fullfill >>> the following scenario: >>> >>> kamailio sems external >>> sipserver >>> Register >>> ----------> Register >>> ----------> >>> >>> 401 >>> >>> <--------------------------- >>> Register with credential >>> ----------> >>> >>> 200 OK >>> >>> >>> <--------------------------- >>> 200 OK >>> <-------------- >>> >>> if sems acts as a sbc, it should be able to pass anything through, >>> should it not? >>> >>> >>> Thanks >>> >>> ------------------------------ >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Alekzander Spiridonov >>> *Sent:* Friday, March 25, 2011 7:20 AM >>> >>> *To:* [email protected] >>> *Subject:* Re: [Sems] question on SBC module in SEMS 1.4 >>> >>> I thought, you want SEMS to register on some server. I don't think >>> SEMS is able to be a Registrar server. >>> >>> Why don''t you use your opensips as an registrar server? >>> >>> 2011/3/25 Karimi-Cherkandi, Bizhan < >>> [email protected]> >>> >>>> This seems to be related to the problem I had with sbc, which I tried >>>> to formulate yesterday in a message to this forum. >>>> I reported: >>>> >>>> running sems in sbc mode, when a Register is forwarded to the sems I get >>>> a 501. the debug shows >>>> >>>> [#b6d79b70/15299] [onOoDRequest, AmApi.cpp:104] ERROR: sorry, we don't >>>> support beginning a new session with a 'REGISTER' message >>>> >>>> any idea what I am doing wrong? >>>> >>>> I appreciate your help, >>>> >>>> Thanks >>>> >>>> ------------------------------ >>>> *From:* [email protected] [mailto: >>>> [email protected]] *On Behalf Of *Alekzander Spiridonov >>>> *Sent:* Friday, March 25, 2011 6:54 AM >>>> *To:* [email protected] >>>> *Subject:* Re: [Sems] question on SBC module in SEMS 1.4 >>>> >>>> Hi, >>>> >>>> You may use reg_agent module for registrations at SIP registrar and >>>> terminate calls from it. And yes, sbc module allows to proxy media through >>>> SEMS. As for 2.1 and 2.2 you'll have to think about mapping (both for >>>> app_mapping and sbc profile mapping). >>>> >>>> 2011/3/25 ha do <[email protected]> >>>> >>>>> Hi >>>>> >>>>> can i use sems as: >>>>> 1. media proxy >>>>> 2. register to other sip server >>>>> >>>>> i want to do like this: >>>>> 1. >>>>> caller and called register to opensips >>>>> clients --register--opensips >>>>> caller ---INVITE---opensips---INVITE--SBCmodule(SEMS)--INVITE--opensips >>>>> -----called >>>>> >>>>> so the rtp from caller and called will go to SEMS >>>>> >>>>> 2. >>>>> client -- opensips --- SEMS(register) --- service provider >>>>> 2.1 >>>>> caller --service provider ---SEMS ---opensips---called >>>>> 2.2 >>>>> caller ---opensips ---SEMS --service provider---called >>>>> >>>>> opensips and sems run in same server and have 1 NIC >>>>> opensips run in port 5060 >>>>> sems will be run in port 5080 >>>>> >>>>> >>>>> Thank you >>>>> Ha` >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Sems mailing list >>>>> [email protected] >>>>> http://lists.iptel.org/mailman/listinfo/sems >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Alekzander Spiridonov >>>> >>> >>> >>> >>> -- >>> С уважением, >>> Александр Спиридонов >>> >>> >>> >> >> >> -- >> С уважением, >> Александр Спиридонов >> >> >> >> _______________________________________________ >> Sems mailing list >> [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
