Re: [SR-Users] Sip routing
Do you want from your classic skype client or from former lync (now skype for business) -- just to avoid confusions given the close naming they have these days? Integration with Lync should work given you use tcp or tls. To route to a Jabber server you will have to use Asterisk or FreeSwitch as a SIP-Jingle gateway. Cheers, Daniel On 03/02/16 18:49, David Bakker wrote: > > I want to be able to route sip invites from my on prem skype to either > an on prem jabber server or out to office 365. It depends on who the > recipient is. I am sure Kamailio can do this but I am absolutely at a > loss on where to start. > > I have tried a few different configs but I basically have to break our > office communication to test. I am looking for some guidance on what > to do. Thanks in advance! > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Sip routing
I want to be able to route sip invites from my on prem skype to either an on prem jabber server or out to office 365. It depends on who the recipient is. I am sure Kamailio can do this but I am absolutely at a loss on where to start. I have tried a few different configs but I basically have to break our office communication to test. I am looking for some guidance on what to do. Thanks in advance! ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] SIP routing configuration howto
Folks,
I'm working on a 5 node network in the following topology:
Host1 - Edge Proxy 1 --- Core Proxy - Edge Proxy 2 - Host2
The proxy machines contain SIP Server installations, the hosts contain user
agent software. I am able to make a call end to end between the hosts, but when
I look at the traffic in wireshark, the core proxy is actually just forwarding
the messages at the IP-layer. I would like actual SIP routing to occur, where a
host would send the INVITE to the edge, and the edge has to forward it to the
core etc, with these messages actually being processed at the SIP layer for all
proxy nodes. I've been trying to use the dynamic routing module, thought I'm
not sure this is really right for what I need, simple static routing would
likely work as well. Is it necessary for me to rewrite the route{} functions of
a proxy script? I'm not sure if I'm approaching this problem the right way.
Eventually I would like to have multiple core servers and be able to failover
between them, but trying to keep it simple for now.
Thanks,
Mike
Michael A. Kaplan
Senior Research Scientist
Applied Communication Sciences
732-699-3805 (office)
973-699-6775 (cell)
mkap...@appcomsci.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Routing Logic in Lua
On 11/19/10 8:27 PM, Iñaki Baz Castillo wrote: 2010/11/17 Daniel-Constantin Mierlamico...@gmail.com: I made an easy-to-do tutorial where all the SIP routing logic is implemented in a Lua script (including authentication, accounting, registrar, user location). You can read it at: http://asipto.com/u/h sr.tm.t_check_trans() sr.sl.send_reply(404, Not here) sr.tm.t_relay() sr.rr.loose_route() [...] I'd strongly would like that kamailio config file uses namespaced functions as well, as it's an ellegant way to realize of which module each function belongs to. There are more and more modules and new functions, and it's becoming rather difficult to understand a kamailio/SR script with so many functions sharing the same/unique namespace. function_name= module.function_name It's cool, it's easy, it's sexy :) This should not be that complex, there is no function name that has '.' in order to have current conflicts to solve. My concern is related to modules with very long names, but seems that most of such cases do not export lot of functions (e.g., presence_*). Alternative is to introduce a short id for modules, eg,: ps = presence rp = rtpproxy to be used only when module name is too long. Btw, this option can speed up a bit the startup, as now resolving a function in config means going through all modules and all functions in a row. Knowing the module, then the search will be only within the list of functions exported by that module. Just a side note, not big influence over all, this being done at startup. Cheers, Daniel BTW the article showing the LUA usage is brilliant :) -- Daniel-Constantin Mierla Kamailio (OpenSER) Advanced Trainings Nov 22-25, 2010, Berlin, Germany Jan 24-26, 2011, Irvine, CA, USA http://www.asipto.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Routing Logic in Lua
Daniel-Constantin Mierla wrote: On 11/19/10 8:27 PM, Iñaki Baz Castillo wrote: 2010/11/17 Daniel-Constantin Mierlamico...@gmail.com: I made an easy-to-do tutorial where all the SIP routing logic is implemented in a Lua script (including authentication, accounting, registrar, user location). You can read it at: http://asipto.com/u/h sr.tm.t_check_trans() sr.sl.send_reply(404, Not here) sr.tm.t_relay() sr.rr.loose_route() [...] I'd strongly would like that kamailio config file uses namespaced functions as well, as it's an ellegant way to realize of which module each function belongs to. There are more and more modules and new functions, and it's becoming rather difficult to understand a kamailio/SR script with so many functions sharing the same/unique namespace. function_name= module.function_name It's cool, it's easy, it's sexy :) This should not be that complex, there is no function name that has '.' in order to have current conflicts to solve. My concern is related to modules with very long names, but seems that most of such cases do not export lot of functions (e.g., presence_*). Alternative is to introduce a short id for modules, eg,: ps = presence rp = rtpproxy to be used only when module name is too long. Btw, this option can speed up a bit the startup, as now resolving a function in config means going through all modules and all functions in a row. Knowing the module, then the search will be only within the list of functions exported by that module. Just a side note, not big influence over all, this being done at startup. Cheers, Daniel BTW the article showing the LUA usage is brilliant :) As an aside, is there a current index of functions available? i.e. given a function what module is it from and what it does? ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Routing Logic in Lua
On 11/20/10 10:24 AM, Jeremya wrote: Daniel-Constantin Mierla wrote: On 11/19/10 8:27 PM, Iñaki Baz Castillo wrote: 2010/11/17 Daniel-Constantin Mierlamico...@gmail.com: I made an easy-to-do tutorial where all the SIP routing logic is implemented in a Lua script (including authentication, accounting, registrar, user location). You can read it at: http://asipto.com/u/h sr.tm.t_check_trans() sr.sl.send_reply(404, Not here) sr.tm.t_relay() sr.rr.loose_route() [...] I'd strongly would like that kamailio config file uses namespaced functions as well, as it's an ellegant way to realize of which module each function belongs to. There are more and more modules and new functions, and it's becoming rather difficult to understand a kamailio/SR script with so many functions sharing the same/unique namespace. function_name= module.function_name It's cool, it's easy, it's sexy :) This should not be that complex, there is no function name that has '.' in order to have current conflicts to solve. My concern is related to modules with very long names, but seems that most of such cases do not export lot of functions (e.g., presence_*). Alternative is to introduce a short id for modules, eg,: ps = presence rp = rtpproxy to be used only when module name is too long. Btw, this option can speed up a bit the startup, as now resolving a function in config means going through all modules and all functions in a row. Knowing the module, then the search will be only within the list of functions exported by that module. Just a side note, not big influence over all, this being done at startup. Cheers, Daniel BTW the article showing the LUA usage is brilliant :) As an aside, is there a current index of functions available? i.e. given a function what module is it from and what it does? I mentioned it in the tutorial: http://kb.asipto.com/kamailio:usage:k32-lua-routing#references But should be added also in app_module readme, you have the available API at: http://sip-router.org/wiki/api/lua/devel Cheers, Daniel -- Daniel-Constantin Mierla Kamailio (OpenSER) Advanced Trainings Nov 22-25, 2010, Berlin, Germany Jan 24-26, 2011, Irvine, CA, USA http://www.asipto.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Routing Logic in Lua
On 11/20/10 10:27 AM, Jon Bonilla (Manwe) wrote: El Sat, 20 Nov 2010 10:15:27 +0100 Daniel-Constantin Mierlamico...@gmail.com escribió: This should not be that complex, there is no function name that has '.' in order to have current conflicts to solve. My concern is related to modules with very long names, but seems that most of such cases do not export lot of functions (e.g., presence_*). Alternative is to introduce a short id for modules, eg,: ps = presence rp = rtpproxy Both of them could be used. One short version for expert people and the long, full format for newbies or in didactical examples. On a second thought, just module name should be enough, because will still be the current version for experts, at least several releases from now on. Introducing short alias will just complicate things, adding confusion. In the future we can review the concept and added if many people want it. Also, we encourage people to find nice short names from beginning of development :-) when only the module name can be used. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio (OpenSER) Advanced Trainings Nov 22-25, 2010, Berlin, Germany Jan 24-26, 2011, Irvine, CA, USA http://www.asipto.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Routing Logic in Lua
2010/11/17 Daniel-Constantin Mierla mico...@gmail.com: I made an easy-to-do tutorial where all the SIP routing logic is implemented in a Lua script (including authentication, accounting, registrar, user location). You can read it at: http://asipto.com/u/h sr.tm.t_check_trans() sr.sl.send_reply(404, Not here) sr.tm.t_relay() sr.rr.loose_route() [...] I'd strongly would like that kamailio config file uses namespaced functions as well, as it's an ellegant way to realize of which module each function belongs to. There are more and more modules and new functions, and it's becoming rather difficult to understand a kamailio/SR script with so many functions sharing the same/unique namespace. function_name=module.function_name It's cool, it's easy, it's sexy :) BTW the article showing the LUA usage is brilliant :) -- Iñaki Baz Castillo i...@aliax.net ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] SIP Routing Logic in Lua
Hello, during last days I spent some time to extend the native API exported to Lua. Many more functions exported by core and modules can be called from embedded Lua scripts. Note that you get also access to psedo-variable operations and you can call all functions exported by modules that have no fixup pretty safe, via sr.modf(...), without a need to be exported natively. I made an easy-to-do tutorial where all the SIP routing logic is implemented in a Lua script (including authentication, accounting, registrar, user location). You can read it at: http://asipto.com/u/h Therefore, if the configuration file language is not offering everything you need to route your SIP traffic, look at app_lua module and its API, it is a real option right now. Lua is a small and fast embeddable language, the interpreter is linked to and loaded by Kamailio at statup, therefore the performance penalty is not significant (Lua project site is: http://www.lua.org). It is also popular among other SIP telephony projects. Any kind of feedback is appreciated! Cheers, Daniel -- Daniel-Constantin Mierla Kamailio (OpenSER) Advanced Trainings Nov 22-25, 2010, Berlin, Germany Jan 24-26, 2011, Irvine, CA, USA http://www.asipto.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP Routing Logic in Lua
Definitely cool! Thanks, Carsten 2010/11/17 Daniel-Constantin Mierla mico...@gmail.com: Hello, during last days I spent some time to extend the native API exported to Lua. Many more functions exported by core and modules can be called from embedded Lua scripts. Note that you get also access to psedo-variable operations and you can call all functions exported by modules that have no fixup pretty safe, via sr.modf(...), without a need to be exported natively. I made an easy-to-do tutorial where all the SIP routing logic is implemented in a Lua script (including authentication, accounting, registrar, user location). You can read it at: http://asipto.com/u/h Therefore, if the configuration file language is not offering everything you need to route your SIP traffic, look at app_lua module and its API, it is a real option right now. Lua is a small and fast embeddable language, the interpreter is linked to and loaded by Kamailio at statup, therefore the performance penalty is not significant (Lua project site is: http://www.lua.org). It is also popular among other SIP telephony projects. Any kind of feedback is appreciated! Cheers, Daniel -- Daniel-Constantin Mierla Kamailio (OpenSER) Advanced Trainings Nov 22-25, 2010, Berlin, Germany Jan 24-26, 2011, Irvine, CA, USA http://www.asipto.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Carsten Bock Schomburgstr. 80 22767 Hamburg Germany Mobile +49 179 2021244 Home +49 40 34927217 Fax +49 40 34927218 mailto:cars...@bock.info ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] SIP routing problem when kamailio uses 2 interfaces
I think you have multiple issues: (not sure if I am right as I have to guess your network setup) 1. If Kamailio is an Application Layer Gateway between the public and the internal network, then of course Asterisk should listen only on the internal interface. Thus in sip.conf add: udpbindaddr = internal.ip.add.ress Further you can tweak if Asterisk should use internal or public IP addresses inside the SIP message headers by playing around with externip = ... localnet = ... 2. Regardless of the Via header inserted by Kamailio Asterisk should respond to the IP address from which Kamailio sent the request. Thus I guess Kamailio sent the request with the public IP address as source IP. To have Kamailio acting correctly you have to make sure that Kamailio is listening on both interfaces (http://sip-router.org/wiki/cookbooks/core-cookbook/devel#listen): listen=udp:public.ip.add.ress:5060 listen=udp:internal.ip.add.ress:5060 and activate multihoming feature of Kamailio to have proper IP addresses in Via and Record-Route headers (http://sip-router.org/wiki/cookbooks/core-cookbook/devel#mhomed) mhomed=1 regards Klaus Am 22.08.2010 04:46, schrieb Gnaneshwar Gatla: Hello All, I'm using Kamailio as a Border controller for my VoIP Research project at my school. The problem I'm facing is Kamailio routes the traffic to the private network where my asterisk machine is listening. The asterisk machine responds to the Kamailio using the public network but not the private. Is this an issue with Asterisk? If so how do I resolve it? client kam_publicKam_pvt Ast_pvtAst_public | | | | | | | | | | |INVITE | | | | || |INVITE | | | | |--|| | | | | | | | | | | | | | | | | | | 404 | | | |--|---|---| | | | | | | | | ACK | | | | |--|| | | | | | | 404 | | | | || | | | | | | | | | ACK | | | | || | | | | | | | | | | | | | Regards Gnaneshwar ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] SIP routing problem when kamailio uses 2 interfaces
Hello All, I'm using Kamailio as a Border controller for my VoIP Research project at my school. The problem I'm facing is Kamailio routes the traffic to the private network where my asterisk machine is listening. The asterisk machine responds to the Kamailio using the public network but not the private. Is this an issue with Asterisk? If so how do I resolve it? clientkam_publicKam_pvt Ast_pvtAst_public | | | | | | | | | | |INVITE | | | | || |INVITE | | | | |--| | | | | | | | | | | | | | | | | | | | 404 | | | |--|---|---| | | | | | | | | ACK | | | | |--| | | | | | | | 404 | | | | || | | | | | | | | | ACK | | | | || | | | | | | | | | | | | | Regards Gnaneshwar ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
