On 12/28/2009 10:54 AM, Antonio Goméz Soto wrote: Yes. See the cisco_restart() function in the 'kamctl' script. It uses the MI interface to generate a request: http://www.kamailio.org/docs/modules/1.5.x/tm.html#id2531975 Please note that although Kamailio does provide this, this goes beyond the realm of what a proxy is supposed to be able to do. Officially, a proxy is an event-driven state machine; it only forwards requests and replies it receives that are generated by other endpoints. It does have a management interface, but it cannot do all that you're asking. Keep in mind that Kamailio/OpenSER is not really a logical endpoint for calls, except in the case of some exceptions where SIP UAS functionality is provided, as in the registrar and the presence user agent, for example. It is not a user agent, so it cannot actually "transfer" anything[1]. A B2BUA is a client user agent (UAC) on one side and a server user agent (UAS) on the other side. It can generate new logical call legs, connect call legs, and, usually asynchronously initiate requests. A proxy, in contrast, receives logical call leg A in and sends the same logical call leg B to the next destination; the attributes of the call leg that it is allowed to change in either requests or replies are quite limited, compared to a B2BUA, which, by virtue of generating a new leg and cross-connecting the two, can put whatever it wants in the second one, reinterpret / mangle feedback more extensively, etc. More generally, outside the realm of protocol mechanics, I think it is important that you understand that Kamailio doesn't really provide "application-level" functionality. To do that, it would have to be able to answer calls itself, which it cannot do. It is not appropriate to compare it to Asterisk; it is not a PBX or anything like that. There is no analogy between them. So, all discussion of MOH and conferences is irrelevant; the absence of support for them is not simply the result of feature set limitations, but rather conceptual incompatibility with the sort of thing that Kamailio is. Google the list archives for references to the "dispatcher" module. -- Alex [1] Though the dialog module does, as of 1.5.x, provide an interesting hack: http://www.kamailio.org/docs/modules/1.5.x/dialog.html#id2532224 -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671

Antonio Goméz Soto wrote: I do not believe the restart function works on Grandstream devices, but if you are serious about VoIP, you should not be using these devices. David

Antonio Goméz Soto writes: you can make registrar to send the notifies via mi commands. -- juha

On Mon, December 28, 2009 5:57 pm, Antonio Goméz Soto wrote: Hey Antonio, just to give you an example about such an application, take a look to 'siremis', which is a administrative interface for kamailio. Regards, Henning

On Mon, December 28, 2009 6:23 pm, Alex Balashov wrote: Hey Alex, good that you clarified that. Thanks for the pointer to the FOP, i did not know about this, looks neat. Henning

On 12/28/2009 01:50 PM, Antonio Goméz Soto wrote: No. It is not an endpoint. No. It is not an endpoint. No, it is not an endpoint, although it can trigger external media proxy processes via APIs / control sockets (mediaproxy, rtpproxy) that can perform this functionality. No. OpenSER does not inherently support or not support a header; it has nothing to do with them except to pass them along in a request. It can attach them, and it can read their values if they are present and act on them in some user-defined way; this is true of any such header. OpenSER cannot augment, extend or implement any of the PBX-like features you're looking for; that is simply not what it does. SIP messages enter OpenSER and they leave it, the effect of which is to intervene in and direct the establishment of calls to various destinations. It is fundamentally a network element inside a VoIP service delivery platform, not an application server, PBX, feature server, or other type of call endpoint. It's a rather low-level piece of infrastructure. I think you may have misunderstood what it is people mean when they say that they use OpenSER to help horizontally scale their use of Asterisk out. The role is a complementary one, not a substitute. For example, a typical design for application or service delivery using Asterisk + OpenSER involves multiple Asterisk servers that behave identically when they receive an inbound call, regardless of which server the call came into. This is typically done using some sort of database that keeps shared state, and most likely a central point of logic deployment, such as a FastAGI controller. In this type of situation, as an example, an OpenSER-based load balancer in front of this farm of servers to round-robin among them or do other intelligent call distribution can be used to great effect. But Asterisk (or whatever backend) must still provide the fundamental functionality. Think of Kamailio the same way you would think of a Layer 3 IP router. What you are proposing is analogous to saying that a router can be used to scale an HTTP web server / web site operation. A router cannot inherently do that, but it can assist in doing so as an element of a web server and network topology that makes that possible. -- Alex -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671