OverSIP + Kamailio + sipml5

1,456 views
Skip to first unread message

aub...@presenceco.com

unread,
Jul 29, 2013, 9:50:52 AM7/29/13
to ove...@googlegroups.com
Hi all,

I have an environment configured with OverSIP + Kamailio + sipml5. I register successfully extension using websocket to OverSIP and using UDP to Kamailio, but I can not make calls. On Kamailio logs, I see this errors:

Jul 29 13:45:55 ubuntu8911597 /usr/sbin/kamailio[2381]: ERROR: sl [sl_funcs.c:371]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL)
Jul 29 13:45:55 ubuntu8911597 /usr/sbin/kamailio[2381]: NOTICE: acc [acc.c:275]: acc_log_request(): ACC: call missed: timestamp=1375098355;method=INVITE;from_tag=2zHs2iB2XED4wlaUxeuT;to_tag=;call_id=2cf5635a-77c4-90b7-51b3-edab571408c6;code=478;reason=Request Failure;src_user=80002;src_domain=89.1.14.102;src_ip=89.1.14.101;dst_ouser=80001;dst_user=mab68fhc;dst_domain=bb470earpfbd.invalid
Jul 29 13:51:17 ubuntu8911597 /usr/sbin/kamailio[2383]: : <core> [dns_cache.c:2747]: dns_srv_sip_resolvehost(): BUG: sip_resolvehost: unknown proto 5
Jul 29 13:51:17 ubuntu8911597 /usr/sbin/kamailio[2383]: ERROR: <core> [resolve.c:1727]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "df7jal23ls0d.invalid"
Jul 29 13:51:17 ubuntu8911597 /usr/sbin/kamailio[2383]: ERROR: tm [ut.h:337]: uri2dst2(): failed to resolve "df7jal23ls0d.invalid"
Jul 29 13:51:17 ubuntu8911597 /usr/sbin/kamailio[2383]: ERROR: tm [t_fwd.c:1534]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches
Jul 29 13:51:17 ubuntu8911597 /usr/sbin/kamailio[2383]: ERROR: sl [sl_funcs.c:371]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL)
Jul 29 13:51:17 ubuntu8911597 /usr/sbin/kamailio[2383]: NOTICE: acc [acc.c:275]: acc_log_request(): ACC: call missed: timestamp=1375098677;method=INVITE;from_tag=T1s7ovo0TEFegV6sAb3L;to_tag=;call_id=365a882e-b35f-6091-e4ce-edc1cb4abf97;code=478;reason=Request Failure;src_user=80001;src_domain=89.1.14.102;src_ip=89.1.14.101;dst_ouser=80002;dst_user=80002;dst_domain=df7jal23ls0d.invalid

What can be the problem?

Thank you,

Iñaki Baz Castillo

unread,
Jul 29, 2013, 10:34:11 AM7/29/13
to ove...@googlegroups.com
SIPml5 does not announce nor request "Outbound" support (RFC 5626)
which is a terrible bug of the authors. Due to this, you must force it
in OverSIP by calling request.fix_nat() before routing requests.

2013/7/29 <aub...@presenceco.com>:
> --
> You received this message because you are subscribed to the Google Groups
> "OverSIP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to oversip+u...@googlegroups.com.
> To post to this group, send an email to ove...@googlegroups.com.
> Visit this group at http://groups.google.com/group/oversip.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Iñaki Baz Castillo
<i...@aliax.net>

aub...@presenceco.com

unread,
Jul 29, 2013, 10:53:33 AM7/29/13
to ove...@googlegroups.com
Hi Iñaki,

I've implemented the changes and error also happens. In oversip traces the following message:

Jul 29 16:50:19 ubuntu8911597 oversip[2527]:  DEBUG: <ICT d51d587f45ac7ec31a391389f3408780b2d63776> sending ACK for [3456]XX response
Jul 29 16:50:19 ubuntu8911597 oversip[2527]:  DEBUG: <Proxy proxy_out b3ViP4uGDyJTUDURyaVUcPAwVCyrISvo> received response 478
Jul 29 16:50:19 ubuntu8911597 oversip[2527]:   INFO: <SipEvents> [user] on_failure_response: 478 'Unresolvable destination (478/SL)'
Jul 29 16:50:19 ubuntu8911597 oversip[2527]:  DEBUG: <SIP Request b3ViP4uGDyJTUDURyaVUcPAwVCyrISvo> forwarding response 478 "Unresolvable destination (478/SL)"

Thanks,
Agustí

Iñaki Baz Castillo

unread,
Jul 29, 2013, 10:56:38 AM7/29/13
to ove...@googlegroups.com
2013/7/29 <aub...@presenceco.com>:
I don't know how your OpenSISP and your OverSIP are configured and
thus it is very difficult to explain what is happening. Some SIP
traces could help (in plain text with ngrep).

aub...@presenceco.com

unread,
Jul 29, 2013, 11:43:57 AM7/29/13
to ove...@googlegroups.com
Hi Iñaki,

Resume envirnoment (local environment):
  1. Extension 80001
    1. Google Chrome
    2. ws connection to oversip (89.1.14.101)
    3. udp connection (and registration) to kamailio (89.1.14.102)
  2. Extension 80002
    1. Google Chrome
    2. ws connection to oversip (89.1.14.101)
    3. udp connection (and registration) to kamailio (89.1.14.102)
Failed calling between extensions from http://sipml5.org/call.htm.

These are the log files generated in oversip and kamailio.

==================================
OVERSIPS
==================================
Jul 29 17:29:45 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending keep-alive ping frame
Jul 29 17:29:45 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received pong frame: payload_length=10
Jul 29 17:30:08 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending keep-alive ping frame
Jul 29 17:30:08 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received pong frame: payload_length=10
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <SIP WS IPv4 server> connection opened from 89.1.250.120:58058
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <SIP WS IPv4 server> running OverSIP::WebSocketEvents.on_connection()...
Jul 29 17:30:50 ubuntu8911597 oversip[2579]: NOTICE: <WebSocketEvents> on_connection() method is not defined
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <HTTP WS Request> replying 101 "Switching Protocols"
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received text frame: FIN=true, RSV1-3=false/false/false, payload_length=577
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <WsSipApp> received WS message: type=text, length=577
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:   INFO: <SipEvents> [user] REGISTER from sip:80...@89.1.14.102 (UA: IM-client/OMA1.0 sipML5-v1.2013.07.17) to sip:89.1.14.102 via WS 89.1.250.120 : 58058
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request hFuUTmum8pMFQwo7AuCqOCHdz7TPsbVi> applying outgoing Outbound support
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <OutboundMangling module> performing Contact mangling (adding ;ov-ob Outbound param) for SIP Request hFuUTmum8pMFQwo7AuCqOCHdz7TPsbVi
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out hFuUTmum8pMFQwo7AuCqOCHdz7TPsbVi> trying single target: udp:89.1.14.102:5060
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out hFuUTmum8pMFQwo7AuCqOCHdz7TPsbVi> received response 200
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <OutboundMangling module> reverting original Contact value (removing ;ov-ob Outbound param) for response
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <UserAssertion module> user sip:80...@89.1.14.102 asserted to connection
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request hFuUTmum8pMFQwo7AuCqOCHdz7TPsbVi> forwarding response 200 "OK"
Jul 29 17:30:50 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending text frame: payload_length=465
Jul 29 17:30:55 ubuntu8911597 oversip[2579]:  DEBUG: <NICT b9feaa6b12dc04148f96c097828a41c93a0cc99c> timer K expires, transaction terminated
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received text frame: FIN=true, RSV1-3=false/false/false, payload_length=3282
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <WsSipApp> received WS message: type=text, length=3282
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:   INFO: <SipEvents> [user] INVITE from sip:80...@89.1.14.102 (UA: IM-client/OMA1.0 sipML5-v1.2013.07.17) to sip:80...@89.1.14.102 via WS 89.1.250.120 : 58058
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU> applying outgoing Outbound support
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <UserAssertion module> user asserted, adding P-Asserted-Identity for SIP Request ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU> replying 100 "Trying"
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending text frame: payload_length=314
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU> trying single target: udp:89.1.14.102:5060
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <ICT 7a9202183b36a3123cd28a03c909a65aa45dec77> sending ACK for [3456]XX response
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU> received response 404
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:   INFO: <SipEvents> [user] on_failure_response: 404 'Not Found'
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU> forwarding response 404 "Not Found"
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending text frame: payload_length=377
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received text frame: FIN=true, RSV1-3=false/false/false, payload_length=363
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <WsSipApp> received WS message: type=text, length=363
Jul 29 17:31:06 ubuntu8911597 oversip[2579]:  DEBUG: <IST ZCawWpMAlVbaEeBS6IshcKNwiE7FhUBU> ACK received during completed state, now confirmed
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <SIP WS IPv4 server> connection opened from 89.1.250.120:58064
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <SIP WS IPv4 server> running OverSIP::WebSocketEvents.on_connection()...
Jul 29 17:31:13 ubuntu8911597 oversip[2579]: NOTICE: <WebSocketEvents> on_connection() method is not defined
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <HTTP WS Request> replying 101 "Switching Protocols"
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received text frame: FIN=true, RSV1-3=false/false/false, payload_length=578
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <WsSipApp> received WS message: type=text, length=578
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:   INFO: <SipEvents> [user] REGISTER from sip:80...@89.1.14.102 (UA: IM-client/OMA1.0 sipML5-v1.2013.07.17) to sip:89.1.14.102 via WS 89.1.250.120 : 58064
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request ZNWpDfOQTxAoDXkb2aHd4KmMemEorl6C> applying outgoing Outbound support
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <OutboundMangling module> performing Contact mangling (adding ;ov-ob Outbound param) for SIP Request ZNWpDfOQTxAoDXkb2aHd4KmMemEorl6C
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out ZNWpDfOQTxAoDXkb2aHd4KmMemEorl6C> trying single target: udp:89.1.14.102:5060
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out ZNWpDfOQTxAoDXkb2aHd4KmMemEorl6C> received response 200
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <OutboundMangling module> reverting original Contact value (removing ;ov-ob Outbound param) for response
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <UserAssertion module> user sip:80...@89.1.14.102 asserted to connection
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request ZNWpDfOQTxAoDXkb2aHd4KmMemEorl6C> forwarding response 200 "OK"
Jul 29 17:31:13 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending text frame: payload_length=466
Jul 29 17:31:18 ubuntu8911597 oversip[2579]:  DEBUG: <NICT bdcc67dd49719b1fa0b6d443a63e86cc45dce922> timer K expires, transaction terminated
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> received text frame: FIN=true, RSV1-3=false/false/false, payload_length=1788
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <WsSipApp> received WS message: type=text, length=1788
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:   INFO: <SipEvents> [user] INVITE from sip:80...@89.1.14.102 (UA: IM-client/OMA1.0 sipML5-v1.2013.07.17) to sip:80...@89.1.14.102 via WS 89.1.250.120 : 58064
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request 21pr3qF8QTiFOVoWVJfU4liywgO36Zu8> applying outgoing Outbound support
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <UserAssertion module> user asserted, adding P-Asserted-Identity for SIP Request 21pr3qF8QTiFOVoWVJfU4liywgO36Zu8
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request 21pr3qF8QTiFOVoWVJfU4liywgO36Zu8> replying 100 "Trying"
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <WsFraming> sending text frame: payload_length=314
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out 21pr3qF8QTiFOVoWVJfU4liywgO36Zu8> trying single target: udp:89.1.14.102:5060
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <ICT e3125be61d2b0598b30ed1a26f730600f7e692d1> sending ACK for [3456]XX response
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <Proxy proxy_out 21pr3qF8QTiFOVoWVJfU4liywgO36Zu8> received response 478
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:   INFO: <SipEvents> [user] on_failure_response: 478 'Unresolvable destination (478/SL)'
Jul 29 17:31:23 ubuntu8911597 oversip[2579]:  DEBUG: <SIP Request 21pr3qF8QTiFOVoWVJfU4liywgO36Zu8> forwarding response 478 "Unresolvable destination (478/SL)"

==================================
KAMAILIO
==================================
Jul 29 17:31:23 ubuntu8911597 /usr/sbin/kamailio[4481]: ERROR: <core> [resolve.c:1727]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "df7jal23ls0d.invalid"
Jul 29 17:31:23 ubuntu8911597 /usr/sbin/kamailio[4481]: ERROR: tm [ut.h:337]: uri2dst2(): failed to resolve "df7jal23ls0d.invalid"
Jul 29 17:31:23 ubuntu8911597 /usr/sbin/kamailio[4481]: ERROR: tm [t_fwd.c:1534]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches
Jul 29 17:31:23 ubuntu8911597 /usr/sbin/kamailio[4481]: ERROR: sl [sl_funcs.c:371]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL)

Thanks,

Iñaki Baz Castillo

unread,
Jul 30, 2013, 3:53:32 AM7/30/13
to ove...@googlegroups.com
You must add Path support to Kamailio's "registrar" module.

modparam("registrar", "use_path", 1)
modparam("registrar", "path_mode", 1)
modparam("registrar", "path_use_received", 0)



2013/7/29 <aub...@presenceco.com>:
> --
> You received this message because you are subscribed to the Google Groups
> "OverSIP" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to oversip+u...@googlegroups.com.
> To post to this group, send an email to ove...@googlegroups.com.
> Visit this group at http://groups.google.com/group/oversip.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



Soufiane EL HAMCHI

unread,
Feb 14, 2014, 9:52:18 AM2/14/14
to ove...@googlegroups.com
hi :-)
could you tell me .. which tutoriel did you follow to configure OverSIP + sipml5
thanks for help ..

RVN

unread,
Mar 24, 2015, 6:03:25 PM3/24/15
to ove...@googlegroups.com
I apologize for piggy-backing on an older topic, but can someone point me towards the advantage of a setup with OverSIP+Kamailio+sipml5 or jssip?

I fail to grasp the need for oversip in this scenario?  jssip even has a mention of support for connecting straight to kamailio on its site... Is the only advantage of oversip the ruby logic and events? or is oversip doing something else in the middle that kamailio is uncapable of?  Or is it purely a design decision to use oversip as a proxy and not using the proxy functions of kamailio?  I'm trying to figure out an optimum architecture and this udnerstanding would help...

thanks!

hani osamn

unread,
May 2, 2016, 5:08:24 PM5/2/16
to OverSIP
can any one help me on installation and config from a to z kamailio and oversip and will pay to this 
skype: kacknone 
Reply all
Reply to author
Forward
0 new messages