[OpenSIPS-Users] Opensips with rtpengine
Sasmita Panda
spanda at 3clogic.com
Fri Feb 17 03:46:09 EST 2017
Hi All ,
I am not able to take incoming call from a gateways with tls
connection in opensips-1.11.
my config file looks like bellow .
listen=udp:107.170.x.y:5508
listen=tls:107.170.x.y:5063
tls_verify_server = 1
tls_verify_client = 1
tls_require_client_certificate = 0
tls_method = TLSv1
tls_certificate = "/usr/etc/opensips/tls/user/user-cert.pem"
tls_private_key = "/usr/etc/opensips/tls/user/user-privkey.pem"
tls_ca_list = "/usr/etc/opensips/tls/user/user-calist.pem"
alias="107.170.x.y"
alias="107.170.x.y:5508"
alias="107.170.x.y:5063"
NOTE: All other necessary modules are loaded here .....
if (is_method("INVITE")) {
if(is_from_gw() || (to_uri=~"@1.1.1.1"))
{
xlog( "L_WARN", "Source IP sas : $Ri To Uri : $tu From
: $fU Request URI: $oU Call ID:$ci" );
# alias_db_lookup("dbaliases");
if ( !lookup("location")){
sl_send_reply("404","NO Match Found");
xlog( "L_WARN", "Source IP : $si To Uri
: $tu From : $fU Request URI: $oU Call ID:$ci: NO Match Found" );
exit;
}
#do lcr
if ( !serialize_branches(1)){
sl_send_reply("500","Internal Server
Error");
exit;
}else{
next_branches();
t_on_failure("3");
route(1);
exit;
}
}
route(10);
}
When I am taking an incoming call from a gateways , with udp its
getting processed properly . But when I am taking call through TLS it not
going inside the is_from_gw() block , Its directly going to the route(10) .
Why this is happening . Am I missing something .
Please help me , I am in middle of my development .
Thanks in advance .
*Thanks & Regards*
*Sasmita Panda*
*Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
On Mon, Feb 13, 2017 at 10:19 PM, Răzvan Crainea <razvan at opensips.org>
wrote:
> Hi, Sasmita!
>
> Did you follow the WS tutorial[1]? You need to use the
> fix_nated_register(); function for REGISTER messages, to overwrite the
> contact with the IP&port the message was received from.
>
> [1] http://www.opensips.org/Documentation/Tutorials-WebSocket-2-2
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
>
> On 02/13/2017 03:15 PM, Sasmita Panda wrote:
>
> I think path is not getting saved in the location table in oepnsips-2.2
> but its getting saved in opensips-1.11 .
>
> Is there any difference saving path in the location table on case of
> opensips-2.2 . If yes then what ?
>
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> On Mon, Feb 13, 2017 at 1:00 PM, Sasmita Panda <spanda at 3clogic.com> wrote:
>
>> Hi All ,
>>
>> The wss authentication is working now . Thank you for your
>> suggestion .
>>
>> But now I am facing another issue . When I am registering a number
>> from SIPML5 in contact the hostname is somehow "df7jal23ls0d.invalid"
>> like this . And when I am dialing that number opensips is giving error . I
>> am getting "476 Unresolvable hostname ". Bellow is the error in opensips
>> logs . What should I do for this . This is coming with version: opensips
>> 2.2.2 (x86_64/linux) .
>>
>> ERROR:core:do_action: next_branches failed
>> ERROR:core:sip_resolvehost: forced proto 6 not matching sips uri
>> CRITICAL:core:mk_proxy: could not resolve hostname: "df7jal23ls0d.invalid"
>> ERROR:tm:uri2proxy: bad host name in URI
>>
>>
>> There is another setup of mine , opensips-1.11 with ovesip for
>> wss gateway . that was working fine . rather the hostname in that case is
>> also the same but there is no such problem .
>>
>>
>> Is this a known issue or I need to set any parameter for this . If
>> yes then what . My usrloc module looks like bellow .
>> loadmodule "usrloc.so"
>> modparam("usrloc", "db_mode", 2)
>> modparam("usrloc", "use_domain", 1)
>> modparam("usrloc", "matching_mode", 1)
>>
>> I have tried with other options also . But yet its not working .
>> Still I am trying . If anybody can help me with this then It will be
>> helpful .
>>
>> Thanks
>>
>>
>>
>>
>>
>>
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> On Fri, Feb 10, 2017 at 7:04 PM, Tito Cumpen <tito at xsvoce.com> wrote:
>>
>>> Sasmita,
>>>
>>> I am using the following which works well with sipml5 and sipjs
>>> loadmodule "proto_wss.so"
>>> modparam("proto_wss", "wss_max_msg_chunks", 8)
>>> modparam("tls_mgm", "certificate","/etc/opensips/tls/domain.com.crt")
>>> modparam("tls_mgm", "private_key","/etc/opensips/tls/domain.com.key")
>>> modparam("tls_mgm", "ca_list", "/etc/opensips/tls/domain.com.pem")
>>>
>>> modparam("tls_mgm", "tls_method", "tlsv1")
>>> modparam("tls_mgm", "verify_cert", "0")
>>> modparam("tls_mgm", "require_cert", "0")
>>>
>>> On Thu, Feb 9, 2017 at 5:37 AM, Sasmita Panda <spanda at 3clogic.com>
>>> wrote:
>>>
>>>> Hi All ,
>>>>
>>>> I am running opensips-2.2 with , tls_mgm , proto_tls , proto_wss
>>>> .
>>>> my config look like bellow .
>>>>
>>>>
>>>> listen=udp:x.x.x.x.:5507
>>>> listen=tcp:x.x.x.x:5060
>>>> listen=tls:x.x.x.x:5061
>>>> listen=wss:x.x.x.x:5062
>>>> listen=ws:x.x.x.x:5063
>>>>
>>>> alias="domain.com"
>>>> alias="domain.com:5507"
>>>> alias="domain.com:5061"
>>>> alias="domain.com:5061"
>>>> alias="domain.com:5062"
>>>>
>>>>
>>>> #### WebSocket and WebSocketSecure protocol
>>>> loadmodule "proto_tls.so"
>>>> loadmodule "proto_wss.so"
>>>> loadmodule "proto_ws.so"
>>>>
>>>> # Certificate management
>>>> loadmodule "tls_mgm.so"
>>>>
>>>> modparam("tls_mgm", "tls_method", "TLSv1")
>>>> modparam("tls_mgm", "certificate", "/usr/local/etc/opensips/tls/u
>>>> ser/user-cert.pem")
>>>> modparam("tls_mgm", "private_key", "/usr/local/etc/opensips/tls/u
>>>> ser/user-privkey.pem")
>>>>
>>>>
>>>> When I am making tls connection with " domain.com:5061 " ,
>>>> then the connection is get established .
>>>>
>>>> But from sipml5 phone when I am making wss connection in browser i am
>>>> getting error
>>>> " failed: Error in connection establishment:
>>>> net::ERR_INSECURE_RESPONSE "
>>>>
>>>> In opensips side I am not getting any error . What should I do to
>>>> resolve the problem .Please help me . I have tried every possible way .
>>>>
>>>>
>>>> Thanks
>>>> Sasmita
>>>>
>>>>
>>>>
>>>>
>>>> *Thanks & Regards*
>>>> *Sasmita Panda*
>>>> *Network Testing and Software Engineer*
>>>> *3CLogic , ph:07827611765*
>>>>
>>>> On Tue, Feb 7, 2017 at 2:34 PM, Sasmita Panda <spanda at 3clogic.com>
>>>> wrote:
>>>>
>>>>> Thank you so much .
>>>>>
>>>>> *Thanks & Regards*
>>>>> *Sasmita Panda*
>>>>> *Network Testing and Software Engineer*
>>>>> *3CLogic , ph:07827611765*
>>>>>
>>>>> On Tue, Feb 7, 2017 at 2:30 PM, Răzvan Crainea <razvan at opensips.org>
>>>>> wrote:
>>>>>
>>>>>> Hi, Sasmita!
>>>>>>
>>>>>> Yes, both proto_ws, proto_wss and rtpengine modules are mature enough
>>>>>> and are ready to use.
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Răzvan Crainea
>>>>>> OpenSIPS Solutionswww.opensips-solutions.com
>>>>>>
>>>>>> On 02/07/2017 10:47 AM, Sasmita Panda wrote:
>>>>>>
>>>>>> Hi All ,
>>>>>>
>>>>>> I am quite intrested to use opensips-2.2 with rtpengine . Is
>>>>>> this working good or there is any open issue till now with this module .
>>>>>>
>>>>>> And what about proto_ws and proto_wss . Are these modules
>>>>>> working fine ? Please let me know if any precausion I need to take before
>>>>>> using this .
>>>>>>
>>>>>> Till now I was using opensips-1.11 . So this will be very new
>>>>>> for me . Please let me know if there is any open issue or any link on which
>>>>>> I will get the details .
>>>>>>
>>>>>>
>>>>>> *Thanks & Regards*
>>>>>> *Sasmita Panda*
>>>>>> *Network Testing and Software Engineer*
>>>>>> *3CLogic , ph:07827611765*
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>> _______________________________________________ Users mailing list
>>>>>> Users at lists.opensips.org http://lists.opensips.org/cgi-
>>>>>> bin/mailman/listinfo/users
>>>>>
>>>>> _______________________________________________ Users mailing list
>>>> Users at lists.opensips.org http://lists.opensips.org/cgi-
>>>> bin/mailman/listinfo/users
>>>
>>> _______________________________________________ Users mailing list
>>> Users at lists.opensips.org http://lists.opensips.org/cgi-
>>> bin/mailman/listinfo/users
>>
>> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170217/40463ea1/attachment-0001.html>
More information about the Users
mailing list