12 Jan
2009
12 Jan
'09
11:25 a.m.
Hi,
I have not experience doing this so I want to ask you what is the best
approach to instruct a media server about what announcement to play to
the user.
For example, if I use asterisk, should I define one extension per
announcement type? Is this the common approach?
Thanks
Luciano
12 Jan
12 Jan
11:33 a.m.
2009/1/12 Luciano Afranllie <listas.luafran(a)gmail.com>om>:
Hi,
I have not experience doing this so I want to ask you what is the best
approach to instruct a media server about what announcement to play to
the user.
Well, this is the Kamailio maillist, not Asterisk maillist :)
For example, if I use asterisk, should I define one
extension per
announcement type? Is this the common approach?
Take a look to RFC 4240, it defines some approachs for what you want.
For example, section 3 " Announcement Service" suggest to use an
INVITE RURI with the following syntax:
sip:annc@ms2.example.net;play=file://fileserver.example.net//geminii/yourHoroscope.wav
This sounds cool, but in Asterisk there is no way to read the RURI
parameters so it's not valid for you.
SEMS media server allows multiple methods to set the announcement:
- As RURI username
- As RURI parameter
- As custom header value
Any of them is valid if it works for you :)
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
11:47 a.m.
Hello,
o Iñaki Baz Castillo [01/12/09 17:33]:
there is also an application that works with the RFC 4240
uri method
from above
http://svn.berlios.de/wsvn/sems/trunk/apps/examples/tutorial/annc_service/a…
http://ftp.iptel.org/pub/sems/doc/current/ModuleDoc_annc_service.html
Regards
Stefan
For example,
if I use asterisk, should I define one extension per
announcement type? Is this the common approach?
Take a look to RFC 4240, it defines some approachs for what you want.
For example, section 3 " Announcement Service" suggest to use an
INVITE RURI with the following syntax:
sip:annc@ms2.example.net;play=file://fileserver.example.net//geminii/yourHoroscope.wav
This sounds cool, but in Asterisk there is no way to read the RURI
parameters so it's not valid for you.
SEMS media server allows multiple methods to set the announcement:
- As RURI username
- As RURI parameter
- As custom header value
Any of them is valid if it works for you :)
--
Stefan Sayer
VoIP Services
stefan.sayer(a)iptego.com
www.iptego.com
IPTEGO GmbH
Am Borsigturm 40
13507 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
13 Jan
13 Jan
7:57 a.m.
On Mon, Jan 12, 2009 at 2:47 PM, Stefan Sayer <stefan.sayer(a)iptego.com> wrote:
Hello,
o Iñaki Baz Castillo [01/12/09 17:33]:
there is also an application that works with the RFC 4240 uri method from
above
http://svn.berlios.de/wsvn/sems/trunk/apps/examples/tutorial/annc_service/a…
http://ftp.iptel.org/pub/sems/doc/current/ModuleDoc_annc_service.html
Regards
Stefan
>
>
> Any of them is valid if it works for you :)
>
Thank you very much guys, that was exactly what I wanted to know.
By the way, for the problem I have right know SEMS announcement
application is perfect. I will rewrite ruri user with the file name of
the announcement I want to play to the user and forward the call to
SEMS.
It is my first experience with SEMS and looks very nice.
Regards
Luciano
For example, if I use asterisk, should I define one extension per
announcement type? Is this the common approach?
Take a look to RFC 4240, it defines some approachs for what you want.
For example, section 3 " Announcement Service" suggest to use an
INVITE RURI with the following syntax:
sip:annc@ms2.example.net;play=file://fileserver.example.net//geminii/yourHoroscope.wav
This sounds cool, but in Asterisk there is no way to read the RURI
parameters so it's not valid for you.
SEMS media server allows multiple methods to set the announcement:
- As RURI username
- As RURI parameter
- As custom header value 
12 Jan
12 Jan
11:36 a.m.
On Monday 12 January 2009, Luciano Afranllie wrote:
I have not experience doing this so I want to ask you
what is the best
approach to instruct a media server about what announcement to play to
the user.
For example, if I use asterisk, should I define one extension per
announcement type? Is this the common approach?
Hi Luciano,
you could use 'rewriteuser()' to set the URI user to a certain type of the
announcement, and then forward it to the respective PBX boxes. This match for
the user, and play in the extension the announcement.
Cheers,
Henning
5615
days inactive
5616
days old
4 comments
4 participants
participants (4)
-
Henning Westerholt -
Iñaki Baz Castillo -
Luciano Afranllie -
Stefan Sayer