Hi all,
I've some questions about it.
First of all, when I use a SPA-941 with SER, I can do a three way conference with two incoming calls. Why I can't if I use an other product like SPA2100 ?
I can deduce that this service depends on the functionalities of the product, but I'm not sure.
But if I want nevertheless to use this service independently of the product used, how can I do ?
Using SEMS ? In this case, can we install it without reinstallating SER ? Moreover, with SEMS I think I will have to determine a trigger ? (ie. something like a prefix in the URI ?)
Thank for your answers and your support.
Regards,
Adrien .L
inge wrote:
Hi all,
I've some questions about it.
First of all, when I use a SPA-941 with SER, I can do a three way conference with two incoming calls. Why I can't if I use an other product like SPA2100 ?
AFAIK, you can. They should both support three way conferencing.
I can deduce that this service depends on the functionalities of the product, but I'm not sure.
Yes, and it is also based on your ser.cfg being able to handle the message flow that goes through your proxy. You might get a loose routed REFER message with a Refer-To header, as well as NOTIFY etc. The call flow will depend on how you set up the call (i.e. put on hold, call second, then join).
But if I want nevertheless to use this service independently of the product used, how can I do ?
Using SEMS ? In this case, can we install it without reinstallating SER ? Moreover, with SEMS I think I will have to determine a trigger ? (ie. something like a prefix in the URI ?)
Yes, as Sipura will do local mixing (i.e. one of the participant's UA), you are dependent on the UA capability. You also offload resources, as you don't need rtp to go through your server. SEMS can be used to set up a conference. You can for example use **yournumber as a convention for dialing into a conference, where everybody can dial into any conference and join the call. More advanced would be to set up a shared conference number and then use a PIN to identify a conference. Refer to SEMS for how to do that. g-)
Thank for your answers and your support.
Regards,
Adrien .L
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi Greger,
Thanks for your answer.
Yes they support three way conferencing, but not with incomings calls. This only concerns the SPA-941.
So to establish a three way conferencing with 2 incomings calls, only with "flash keys (ie. R)", it's impossible ? Only local mixing linked to the product, or a bridge with SEMS, but we can't handle "R touch", it's a "local" function.
Le vendredi 24 août 2007 à 09:21 +0200, Greger V. Teigre a écrit :
inge wrote:
Hi all,
I've some questions about it.
First of all, when I use a SPA-941 with SER, I can do a three way conference with two incoming calls. Why I can't if I use an other product like SPA2100 ?
AFAIK, you can. They should both support three way conferencing.
I can deduce that this service depends on the functionalities of the product, but I'm not sure.
Yes, and it is also based on your ser.cfg being able to handle the message flow that goes through your proxy. You might get a loose routed REFER message with a Refer-To header, as well as NOTIFY etc. The call flow will depend on how you set up the call (i.e. put on hold, call second, then join).
But if I want nevertheless to use this service independently of the product used, how can I do ?
Using SEMS ? In this case, can we install it without reinstallating SER ? Moreover, with SEMS I think I will have to determine a trigger ? (ie. something like a prefix in the URI ?)
Yes, as Sipura will do local mixing (i.e. one of the participant's UA), you are dependent on the UA capability. You also offload resources, as you don't need rtp to go through your server. SEMS can be used to set up a conference. You can for example use **yournumber as a convention for dialing into a conference, where everybody can dial into any conference and join the call. More advanced would be to set up a shared conference number and then use a PIN to identify a conference. Refer to SEMS for how to do that. g-)
Thank for your answers and your support.
Regards,
Adrien .L
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I'm not sure I understand "not with incoming calls". You get call 1, pick up, get the call waiting beep for call 2, switch with flash, then connect them. It doesn't work? The call flow is oblivious to which side initiated the two calls in the first place. And yes, the only thing you must make sure on "your" side, is to make sure you don't break the call flow in ser.cfg... g-)
inge wrote:
Hi Greger,
Thanks for your answer.
Yes they support three way conferencing, but not with incomings calls. This only concerns the SPA-941.
So to establish a three way conferencing with 2 incomings calls, only with "flash keys (ie. R)", it's impossible ? Only local mixing linked to the product, or a bridge with SEMS, but we can't handle "R touch", it's a "local" function.
Le vendredi 24 août 2007 à 09:21 +0200, Greger V. Teigre a écrit :
inge wrote:
Hi all,
I've some questions about it.
First of all, when I use a SPA-941 with SER, I can do a three way conference with two incoming calls. Why I can't if I use an other product like SPA2100 ?
AFAIK, you can. They should both support three way conferencing.
I can deduce that this service depends on the functionalities of the product, but I'm not sure.
Yes, and it is also based on your ser.cfg being able to handle the message flow that goes through your proxy. You might get a loose routed REFER message with a Refer-To header, as well as NOTIFY etc. The call flow will depend on how you set up the call (i.e. put on hold, call second, then join).
But if I want nevertheless to use this service independently of the product used, how can I do ?
Using SEMS ? In this case, can we install it without reinstallating SER ? Moreover, with SEMS I think I will have to determine a trigger ? (ie. something like a prefix in the URI ?)
Yes, as Sipura will do local mixing (i.e. one of the participant's UA), you are dependent on the UA capability. You also offload resources, as you don't need rtp to go through your server. SEMS can be used to set up a conference. You can for example use **yournumber as a convention for dialing into a conference, where everybody can dial into any conference and join the call. More advanced would be to set up a shared conference number and then use a PIN to identify a conference. Refer to SEMS for how to do that. g-)
Thank for your answers and your support.
Regards,
Adrien .L
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Greger V. Teigre -
inge