Hi All,
Just a quickie, I'm having MEGA problems getting SER/SEMS operating as a voicemail server. I'm running SER as a proxy on 5060 and SER/SEMS on 5090.
I can get the calls to divert to SER/SEMS on 5090 if the subscriber is unavailable, but I'm having huge problems getting SER/SEMS running properly. The example conf's in the SER-SEMS howto dont seem to work on my set up, and I keep getting database errors thrown up.
I have mailed the SEMS list, but I wondered if anyone here has a working SER/SEMS Voicemail configuration, would you be kind enough to post your ser.cfg and sems.conf so I can compare to try to see where I'm messing it up?
Many thanks,
Ian
Can you explain what is wrong?
Ian Bonham wrote:
Hi All,
Just a quickie, I'm having MEGA problems getting SER/SEMS operating as a voicemail server. I'm running SER as a proxy on 5060 and SER/SEMS on 5090.
I can get the calls to divert to SER/SEMS on 5090 if the subscriber is unavailable, but I'm having huge problems getting SER/SEMS running properly. The example conf's in the SER-SEMS howto dont seem to work on my set up, and I keep getting database errors thrown up.
I have mailed the SEMS list, but I wondered if anyone here has a working SER/SEMS Voicemail configuration, would you be kind enough to post your ser.cfg and sems.conf so I can compare to try to see where I'm messing it up?
Many thanks,
Ian
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
(Must MUST remember to hit reply-all, and not just reply!)
Hi Steve
Whats happening is the call gets to SER/SEMS and then SEMS seems to fail because it can't communicate with SER properly. I've set up as per the Howto exactly, but if I add the line :
fifo_db_url="mysql://xxx:xxx@localhost/ser"
to ser.cfg in Globals, SER fails to start. This is confusing me as in the Howto's it seems this line is important. If I # out the line, SER starts, but when a call hits SER/SEMS, SEMS in debug mode reports :
(25654) DEBUG: execute (AmServer.cpp:276): everything is OK ! (25654) DEBUG: write_to_fifo (SerClient.cpp:237): write_to_fifo: <:DB:00006436608B8F33 select email_address . subscriber username = "8709304900" .
(25654) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo: completed (25654) DEBUG: parseLine (SerDBQuery.cpp:119): line=<500 command 'DB' not available> (25654) DEBUG: parseLine (SerDBQuery.cpp:119): line=<> (25654) ERROR: startSession (AmSession.cpp:468): 404 voicemail: no email address for user <8709304900> (25654) DEBUG: write_to_fifo (SerClient.cpp:237): write_to_fifo: <:t_reply:0000643625E7F6D6 404 voicemail: no email address for user <8709304900> 43869:628960497 0000643613172552 Contact: sip:8709304900@217.160.187.14:5090
(25654) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo: completed (25654) DEBUG: getReturnCode (AmRequest.cpp:357): response from Ser: 500 command 't_reply' not available (25654) ERROR: reply (AmRequest.cpp:335): AmRequestUAS::reply: 500 command 't_reply' not available
So I'm getting two problems I think. First it can't get the Subscribers email address from the SER database. I can if I run the query from mysql on the command line, but SEMS seems unable to get through to the SER database. Is that because of the error <500 command 'DB' not available> ? Then it cannot find the command 't_reply'.
Any suggestions greatly appriciated,
Ian Bonham
Steve Blair (blairs@isc.upenn.edu) wrote:
Can you explain what is wrong?
Ian Bonham wrote:
Hi All,
Just a quickie, I'm having MEGA problems getting SER/SEMS operating as a voicemail server. I'm running SER as a proxy on 5060 and SER/SEMS on 5090.
I can get the calls to divert to SER/SEMS on 5090 if the subscriber is unavailable, but I'm having huge problems getting SER/SEMS running properly. The example conf's in the SER-SEMS howto dont seem to work on my set up, and I keep getting database errors thrown up.
I have mailed the SEMS list, but I wondered if anyone here has a working SER/SEMS Voicemail configuration, would you be kind enough to post your ser.cfg and sems.conf so I can compare to try to see where I'm messing it up?
Many thanks,
Ian
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
--
ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001fax: 215-898-9348
sip:blairs@upenn.edu
Ian:
What version of SER are you using? I have 0.8.14 stable. In this release the fifo_db_url parameter behaved as you described so I removed it without any adverse affects. Other than loading vm.so and defining the modparam("voicemail", "db_url", "mysql://ser:<rwuser>@localhost/ser") I didn't need to make any specific changes to get SEMS to work.
-Steve
Ian Bonham wrote:
(Must MUST remember to hit reply-all, and not just reply!)
Hi Steve
Whats happening is the call gets to SER/SEMS and then SEMS seems to fail because it can't communicate with SER properly. I've set up as per the Howto exactly, but if I add the line :
fifo_db_url="mysql://xxx:xxx@localhost/ser"
to ser.cfg in Globals, SER fails to start. This is confusing me as in the Howto's it seems this line is important. If I # out the line, SER starts, but when a call hits SER/SEMS, SEMS in debug mode reports :
(25654) DEBUG: execute (AmServer.cpp:276): everything is OK ! (25654) DEBUG: write_to_fifo (SerClient.cpp:237): write_to_fifo: <:DB:00006436608B8F33 select email_address . subscriber username = "8709304900" .
(25654) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo: completed (25654) DEBUG: parseLine (SerDBQuery.cpp:119): line=<500 command 'DB' not available> (25654) DEBUG: parseLine (SerDBQuery.cpp:119): line=<> (25654) ERROR: startSession (AmSession.cpp:468): 404 voicemail: no email address for user <8709304900> (25654) DEBUG: write_to_fifo (SerClient.cpp:237): write_to_fifo: <:t_reply:0000643625E7F6D6 404 voicemail: no email address for user <8709304900> 43869:628960497 0000643613172552 Contact: sip:8709304900@217.160.187.14:5090
(25654) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo: completed (25654) DEBUG: getReturnCode (AmRequest.cpp:357): response from Ser: 500 command 't_reply' not available (25654) ERROR: reply (AmRequest.cpp:335): AmRequestUAS::reply: 500 command 't_reply' not available
So I'm getting two problems I think. First it can't get the Subscribers email address from the SER database. I can if I run the query from mysql on the command line, but SEMS seems unable to get through to the SER database. Is that because of the error <500 command 'DB' not available> ? Then it cannot find the command 't_reply'.
Any suggestions greatly appriciated,
Ian Bonham
Steve Blair (blairs@isc.upenn.edu) wrote:
Can you explain what is wrong?
Ian Bonham wrote:
Hi All,
Just a quickie, I'm having MEGA problems getting SER/SEMS operating as a voicemail server. I'm running SER as a proxy on 5060 and SER/SEMS on 5090.
I can get the calls to divert to SER/SEMS on 5090 if the subscriber is unavailable, but I'm having huge problems getting SER/SEMS running properly. The example conf's in the SER-SEMS howto dont seem to work on my set up, and I keep getting database errors thrown up.
I have mailed the SEMS list, but I wondered if anyone here has a working SER/SEMS Voicemail configuration, would you be kind enough to post your ser.cfg and sems.conf so I can compare to try to see where I'm messing it up?
Many thanks,
Ian
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
--
ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001fax: 215-898-9348
sip:blairs@upenn.edu
Hi Steve,
I'm running version: 0.8.14 (i386/linux). The SEMS is the latest from the CVS.
The vm.so is loaded up with : loadmodule "/lib/ser/modules/vm.so"
I have the modparams : modparam("voicemail", "db_url","mysql://ser:xxx@localhost/ser") modparam("voicemail", "subscriber_table", "subscriber") modparam("voicemail", "email_column", "email_address")
but it won't play ball.
Any ideas? :)
Thanks,
Ian
Steve Blair (blairs@isc.upenn.edu) wrote:
Ian:
What version of SER are you using? I have 0.8.14 stable. In this release the fifo_db_url parameter behaved as you described so I removed it without any adverse affects. Other than loading vm.so and defining the modparam("voicemail", "db_url", "mysql://ser:<rwuser>@localhost/ser") I didn't need to make any specific changes to get SEMS to work.
-Steve
Ian Bonham wrote:
(Must MUST remember to hit reply-all, and not just reply!)
Hi Steve
Whats happening is the call gets to SER/SEMS and then SEMS seems to fail because it can't communicate with SER properly. I've set up as per the Howto exactly, but if I add the line :
fifo_db_url="mysql://xxx:xxx@localhost/ser"
to ser.cfg in Globals, SER fails to start. This is confusing me as in the Howto's it seems this line is important. If I # out the line, SER starts, but when a call hits SER/SEMS, SEMS in debug mode reports :
(25654) DEBUG: execute (AmServer.cpp:276): everything is OK ! (25654) DEBUG: write_to_fifo (SerClient.cpp:237): write_to_fifo: <:DB:00006436608B8F33 select email_address . subscriber username = "8709304900" .
(25654) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo: completed (25654) DEBUG: parseLine (SerDBQuery.cpp:119): line=<500 command 'DB' not available> (25654) DEBUG: parseLine (SerDBQuery.cpp:119): line=<> (25654) ERROR: startSession (AmSession.cpp:468): 404 voicemail: no email address for user <8709304900> (25654) DEBUG: write_to_fifo (SerClient.cpp:237): write_to_fifo: <:t_reply:0000643625E7F6D6 404 voicemail: no email address for user <8709304900> 43869:628960497 0000643613172552 Contact: sip:8709304900@217.160.187.14:5090
(25654) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo: completed (25654) DEBUG: getReturnCode (AmRequest.cpp:357): response from Ser: 500 command 't_reply' not available (25654) ERROR: reply (AmRequest.cpp:335): AmRequestUAS::reply: 500 command 't_reply' not available
So I'm getting two problems I think. First it can't get the Subscribers email address from the SER database. I can if I run the query from mysql on the command line, but SEMS seems unable to get through to the SER database. Is that because of the error <500 command 'DB' not available> ? Then it cannot find the command 't_reply'.
Any suggestions greatly appriciated,
Ian Bonham
Steve Blair (blairs@isc.upenn.edu) wrote:
Can you explain what is wrong?
Ian Bonham wrote:
Hi All,
Just a quickie, I'm having MEGA problems getting SER/SEMS operating as a voicemail server. I'm running SER as a proxy on 5060 and SER/SEMS on 5090.
I can get the calls to divert to SER/SEMS on 5090 if the subscriber is unavailable, but I'm having huge problems getting SER/SEMS running properly. The example conf's in the SER-SEMS howto dont seem to work on my set up, and I keep getting database errors thrown up.
I have mailed the SEMS list, but I wondered if anyone here has a working SER/SEMS Voicemail configuration, would you be kind enough to post your ser.cfg and sems.conf so I can compare to try to see where I'm messing it up?
Many thanks,
Ian
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
--
ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001fax: 215-898-9348
sip:blairs@upenn.edu
--
ISC Network Engineering The University of Pennsylvania 3401 Walnut Street, Suite 221A Philadelphia, PA 19104
voice: 215-573-8396
215-746-8001fax: 215-898-9348
sip:blairs@upenn.edu
-
Ian Bonham -
Steve Blair