hi guys,
i read just "getting started" from onsip.org i seach for infos about pstn-gw, bit they speak only about cisco-hardware based solution. is the sems deprecated?
bg, grigory fishilevich
Sems is not dead, Stefan Sayer is doing development. Sems has its own mailing lists. http://lists.iptel.org/ The reason the onsip.org Getting Started does not use sems is that it is not considered mature enough for service provider/enterprise deployment. ONsip.org is focused on such deployments. g-)
Grigory Fishilevich wrote:
hi guys,
i read just "getting started" from onsip.org i seach for infos about pstn-gw, bit they speak only about cisco-hardware based solution. is the sems deprecated?
bg, grigory fishilevich
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
thanks for your answer.i have problems with sems+ser configuration. i find no configexample for pstn-gw with ser+sems. the pdf-file from iptel.org provide no current config example. can anybody help me? i need only an example for ser+sems pstn-gw. i have the head version of ser running.
many thanks
Grigory Fishilevich
On 5/12/05, Greger V. Teigre greger@teigre.com wrote:
Sems is not dead, Stefan Sayer is doing development. Sems has its own mailing lists. http://lists.iptel.org/ The reason the onsip.org Getting Started does not use sems is that it is not considered mature enough for service provider/enterprise deployment. ONsip.org is focused on such deployments. g-)
Grigory Fishilevich wrote:
hi guys,
i read just "getting started" from onsip.org i seach for infos about pstn-gw, bit they speak only about cisco-hardware based solution. is the sems deprecated?
bg, grigory fishilevich
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Grigory Fishilevich wrote:
thanks for your answer.i have problems with sems+ser configuration. i find no configexample for pstn-gw with ser+sems. the pdf-file from iptel.org provide no current config example. can anybody help me? i need only an example for ser+sems pstn-gw. i have the head version of ser running.
Grigory:
I no longer use SEMS but this configuration worked for voicemail and announcement services. My implementation used two instances of SER, one for call routing and one for fifo access to SEMS. This is a partial config for the second instance of SER. Hope this helps.
-Steve
----- begin cut -----
xlog("L_INFO", "\n[SER_vm]: URI MATCH. Time: [%Tf] Method: <%rm> R-uri: <%ru> Call-id: < %ci> Contact Header: <%ct> From uri <%fu> To < %tu> IP source address <%is> \n");
# Voicemail specific configuration - begin
# Just absorb ACKs if(method=="ACK") { break; };
if(method=="INVITE" || method=="BYE" || method=="CANCEL" || method=="REFER") { if(t_newtran()) { t_reply("100","Trying -- one moment please !");
xlog("L_INFO", "\n[SER_vm]: NEW TRAN: Time: [%Tf] Method: <%rm> R-uri: <%ru> Call-id: < %ci> Contact Header: <%ct> From uri <%fu> To < %tu> IP source address <%is> \n");
if(method=="INVITE" || method=="REFER") { xlog("L_INFO", "\n[SER_vm]: Begin SEMS INVITE/REFER code at [%Tf] \n"); if( uri =~"conf" ) { if(!t_write_req("/tmp/am_fifo","conference")) { xlog("L_INFO", "\n[SER_vm]: Failed to contact SEMS conference server [%Tf] \n"); t_reply("500","Could not contact conference server"); }; } else if( uri =~"echo" || uri =~"echo+echo" ) { if(!t_write_req("/tmp/am_fifo","echo")) { xlog("L_INFO", "\n[SER_vm]: Failed to contact SEMS echo server [%Tf] \n"); t_reply("500","Could not contact echo"); }; } else if( uri =~"anno" ) { if(!t_write_req("/tmp/am_fifo","announcement")) { xlog("L_INFO", "\n[SER_vm]: Failed to contact SEMS announcement server [%Tf] \n"); t_reply("500","Could not contact echo"); }; } else { if(!t_write_req("/tmp/am_fifo","voicemail")){ xlog("L_INFO", "\n[SER_vm]: Failed to contact SEMS voicemail server [%Tf] \n"); t_reply("500","could not contact voicemail serv"); }; };
xlog("L_INFO", "\n[SER_vm]: End SEMS INVITE/REFER code at [%Tf] \n"); break; };
if(method=="BYE" || method=="CANCEL") { xlog("L_INFO", "\n[SER_vm]: Begin SEMS BYE/CANCEL code at [%Tf] \n");
if(!t_write_req("/tmp/am_fifo","bye")) { xlog("L_INFO", "\n[SER_vm]: Could not bye SEMS media server at [%Tf] \n"); t_reply("500","Could not contact the media server"); }; xlog("L_INFO", "\n[SER_vm]: End SEMS BYE/CANCEL code at [%Tf] \n"); break; }; } else { xlog("L_INFO", "\n[SER_vm]: Could not create new SEMS transaction at [%Tf] \n"); sl_send_reply("500","could not create new transaction"); }; # Voicemail specific configuration - end } else { if (!t_relay()) { sl_reply_error(); }; };
--- end cut ---
many thanks
Grigory Fishilevich
On 5/12/05, Greger V. Teigre greger@teigre.com wrote:
Sems is not dead, Stefan Sayer is doing development. Sems has its own mailing lists. http://lists.iptel.org/ The reason the onsip.org Getting Started does not use sems is that it is not considered mature enough for service provider/enterprise deployment. ONsip.org is focused on such deployments. g-)
Grigory Fishilevich wrote:
hi guys,
i read just "getting started" from onsip.org i seach for infos about pstn-gw, bit they speak only about cisco-hardware based solution. is the sems deprecated?
bg, grigory fishilevich
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