Re: [PATCH] start-at-boot / userguide
Am 03.10.2012 22:36, schrieb Juan Nin: Was this ever commited? Hi Juan, nop, this never made it's way to the SVN trunk. I'm winding this up right now. All I'd like to change is the name of the config directive, and use 'dead-start = no' (as default). The term boot is something strange to me here, even while I know what Alejandro means of course. Stipe On Thu, Sep 1, 2011 at 4:34 AM, Juan Nin jua...@gmail.com mailto:jua...@gmail.com wrote: See attached patch for adding the start-at-boot directive (smsc group) to the Kannel User's Guide. This was the only missing part so as to get Alejandro Guerrieri's start-at-boot patch into the main tree. Regards, Juan On 5/15/11 6:53 AM, Hillel wrote: Hi Alejandro, Have you been able to commit your start-at-boot patch? thanks From: Alejandro Guerrieriaguerrieri@kannel.__org mailto:aguerri...@kannel.org To: Alexander Malyshamal...@kannel.org mailto:amal...@kannel.org Cc: Kannel Develde...@vm1.kannel.org mailto:de...@vm1.kannel.org Subject: Re: useful patches for everyone Message-ID:0357DE26-1F81-__4C34-96E7-078482437284@kannel.__org mailto:0357de26-1f81-4c34-96e7-078482437...@kannel.org Content-Type: text/plain; charset=us-ascii Thanks Alex, I'll write the userguide part and commit. Regards, Alex -- Alejandro Guerrieri aguerri...@kannel.org mailto:aguerri...@kannel.org On 19/04/2011, at 11:52, Alexander Malysh wrote: Hi Alex, IMHO this option is not really needed and is only workaround about a fact that bearerbox is unable to reload configuration without restart. But reload is much bigger implementation as this simple hack. If this hack will help much people to do cleaner configuration now then I'm not voting against this feature. Alex, please update userguide and commit this patch if nobody has any objections. I'm +0 Thanks, Alexander Malysh Am 19.04.2011 um 10:49 schrieb Alejandro Guerrieri: For KISS's sake, this doesn't clutter configuration nor breaks backwards compatibility. It doesn't hurt performance either. If you don't want to use it just ignore it completely, the default behavior if the directive is missing is to start the smsc at boot as usual, so no harm's done. Where do we trace the absolutely necessary line is of course fuzzy, but from what I read seems like other users would find it useful as well. Regards, -- Alejandro Guerrieri aguerri...@kannel.org mailto:aguerri...@kannel.org On 19/04/2011, at 05:19, Nikos Balkanas wrote: Hi, wapbox must be kept around because of backwards compatibility, that is a must for all open source software. Users are still using it. Finally I would like to add my support for keeping configuration explosion in check. Otherwise, what a few people might gain in convenience, a lot of people might have to pay for it in terms of kannel support due to more difficult configuration. Some golden rules in configuration are: 1) KISS 2) Don't expand it, unless it is absolutely necessary. Stopping service to modify configuration is a no-no. Commenting a configuration file off-line is convenience. My 2 cents, Nikos - Original Message - From: Juan Nin To: Kannel Devel Sent: Tuesday, April 19, 2011 4:41 AM Subject: Re: useful patches for everyone That's what we do today, but the idea is not to have to do any extra work, neither having to comment/uncomment things out, nor have to add/remove config files. Having the start-at-boot directive allows you to just keep the configuration defined, but the smsc does not start. So anytime you need it, you just use the start-smsc and then the stop-smsc. This is much cleaner IMHO than having to do all the extra manual work, no matter how easy that manual work it may be. A similar discussion was held some months ago, can't remember
Re: [PATCH] start-at-boot / userguide
Am 08.10.2012 18:40, schrieb Stipe Tolj:
Am 03.10.2012 22:36, schrieb Juan Nin:
Was this ever commited?
Hi Juan,
nop, this never made it's way to the SVN trunk. I'm winding this up
right now.
All I'd like to change is the name of the config directive, and use
'dead-start = no' (as default). The term boot is something strange to
me here, even while I know what Alejandro means of course.
and committed to the SVN trunk:
2012-10-08 Stipe Tolj stolj at kannel.org
* doc/userguide.xml: adding documentation part for new config directive
'dead-start' being a global config directive for the 'group = smsc'
scope.
* gw/bb_smscconn.c: use the dead_start flag in the connection struct to
determine if we're connecting a SMSC or leave it in 'dead' mode.
* gw/bearerbox.[ch]: changed prototype for smsc2_resume() to indicate a
flag if it was/should be inited.
* gw/smscconn_p.h: add dead_start flag to smscconn.
* gw/smscconn.c: read the SMSC type generic 'dead-start' boolean config
directive to determine if we are starting this SMSC connection
type in
a disconnected mode (dead).
This patchset was originally provided by Alejandro Guerrieri.
[Msg-Id: db023a11-9563-4f0b-a4cb-39a8e86de...@kannel.org]
Thanks to Alejandro for the patchset, and Juan Nin for raising the
topic.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: [PATCH] start-at-boot / userguide
Sounds good! Thanks! On Mon, Oct 8, 2012 at 2:40 PM, Stipe Tolj st...@kannel.org wrote: Am 03.10.2012 22:36, schrieb Juan Nin: Was this ever commited? Hi Juan, nop, this never made it's way to the SVN trunk. I'm winding this up right now. All I'd like to change is the name of the config directive, and use 'dead-start = no' (as default). The term boot is something strange to me here, even while I know what Alejandro means of course. Stipe On Thu, Sep 1, 2011 at 4:34 AM, Juan Nin jua...@gmail.com mailto:jua...@gmail.com wrote: See attached patch for adding the start-at-boot directive (smsc group) to the Kannel User's Guide. This was the only missing part so as to get Alejandro Guerrieri's start-at-boot patch into the main tree. Regards, Juan On 5/15/11 6:53 AM, Hillel wrote: Hi Alejandro, Have you been able to commit your start-at-boot patch? thanks From: Alejandro Guerrieriaguerrieri@kannel.__**org mailto:aguerri...@kannel.org** To: Alexander Malyshamal...@kannel.org mailto: amal...@kannel.org Cc: Kannel Develde...@vm1.kannel.org mailto: de...@vm1.kannel.org Subject: Re: useful patches for everyone Message-ID:0357DE26-1F81-__**4C34-96E7-078482437284@kannel.** __org mailto:0357DE26-1F81-4C34-**96e7-078482437...@kannel.org0357de26-1f81-4c34-96e7-078482437...@kannel.org Content-Type: text/plain; charset=us-ascii Thanks Alex, I'll write the userguide part and commit. Regards, Alex -- Alejandro Guerrieri aguerri...@kannel.org mailto:aguerri...@kannel.org On 19/04/2011, at 11:52, Alexander Malysh wrote: Hi Alex, IMHO this option is not really needed and is only workaround about a fact that bearerbox is unable to reload configuration without restart. But reload is much bigger implementation as this simple hack. If this hack will help much people to do cleaner configuration now then I'm not voting against this feature. Alex, please update userguide and commit this patch if nobody has any objections. I'm +0 Thanks, Alexander Malysh Am 19.04.2011 um 10:49 schrieb Alejandro Guerrieri: For KISS's sake, this doesn't clutter configuration nor breaks backwards compatibility. It doesn't hurt performance either. If you don't want to use it just ignore it completely, the default behavior if the directive is missing is to start the smsc at boot as usual, so no harm's done. Where do we trace the absolutely necessary line is of course fuzzy, but from what I read seems like other users would find it useful as well. Regards, -- Alejandro Guerrieri aguerri...@kannel.org mailto:aguerri...@kannel.org On 19/04/2011, at 05:19, Nikos Balkanas wrote: Hi, wapbox must be kept around because of backwards compatibility, that is a must for all open source software. Users are still using it. Finally I would like to add my support for keeping configuration explosion in check. Otherwise, what a few people might gain in convenience, a lot of people might have to pay for it in terms of kannel support due to more difficult configuration. Some golden rules in configuration are: 1) KISS 2) Don't expand it, unless it is absolutely necessary. Stopping service to modify configuration is a no-no. Commenting a configuration file off-line is convenience. My 2 cents, Nikos - Original Message - From: Juan Nin To: Kannel Devel Sent: Tuesday, April 19, 2011 4:41 AM Subject: Re: useful patches for everyone That's what we do today, but the idea is not to have to do any extra work, neither having to comment/uncomment things out, nor have to add/remove config files. Having the start-at-boot directive allows you to just keep the configuration defined, but the smsc does not start. So anytime you need it, you just use the start-smsc and then the stop-smsc.
GSM Modem is not sending SMS or even not putting into queue
Hi Team, I have installed Kannel and working perfectly with *Ubuntu 12.04.1 LTS*. But I am not able to installed *BluOcean™ USB GSM / GPRS Modem*. Could you please help me so that I will configure and used my GSM modem for sending SMS from Kannel. -- Thanks and regards Virendra Bhati +91-9718500594 Asterisk Developer E-mail-: virbh...@gmail.com Skype id:- virbhati2 New Delhi(India) [image: View my profile on LinkedIn]http://in.linkedin.com/pub/virendra-bhati/6/a30/755
Re: GSM Modem is not sending SMS or even not putting into queue
On 08.10.2012, at 19:39, virendra bhati virbh...@gmail.com wrote: Hi Team, I have installed Kannel and working perfectly with Ubuntu 12.04.1 LTS. But I am not able to installed BluOcean™ USB GSM / GPRS Modem. Could you please help me so that I will configure and used my GSM modem for sending SMS from Kannel. do you have a manual for it? what kind of GSM modem options have you configured? what does the bearerbox.log say if you enable log-level = 0 ? Usually its only a question of finding the right init strings...(which can be tricky at times...) -- Thanks and regards Virendra Bhati +91-9718500594 Asterisk Developer E-mail-: virbh...@gmail.com Skype id:- virbhati2 New Delhi(India)
[PATCH] Kannel SMPP v5.0 support
Hi list,
please find attached a patchset that adds all the relevant new PDUs and
optional TLVs as defined in SMPP v5.0. The diff is against current SVN
trunk.
Some facts about the patch:
- We add the missing PDUs as defined in SMPP v5.0, even while we're
currently not handling them. (This is more or less the same case already
for the submit_multi PDU that is supported in SMPP v3.4)
- We add the missing optional TLVs that are now added to various known
PDUs. From those we currently use only 'billing_idenfitication' in the
submit_sm and data_sm PDU. The field carries according to the SMPP v5.0
spec an arbitrary billing information, so we're mapping this into/from
our msg-sms.binfo field.
- The patch is not intrusive, meaning it doesn't change any current
behavior.
- To allow a v5.0 connection to a SMSC, the 'interface-version = 50' can
be configured in the 'group = smsc' scope.
Please review, any comments are welcome.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Index: gw/smsc/smpp_pdu.def
===
--- gw/smsc/smpp_pdu.def(revision 4992)
+++ gw/smsc/smpp_pdu.def(working copy)
@@ -62,6 +62,8 @@
* Initial optional parameters implementation.
* Alexander Malysh a.mal...@centrium.de:
* Extended optional parameters implementation.
+ * Stipe Tolj stolj at kannel.org:
+ * Adding SMPP v5.0 PDUs
*/
@@ -118,6 +120,9 @@
INTEGER(command_status, 4) \
INTEGER(sequence_number, 4)
+/*
+ * PDUs defined in SMPP v3.4
+ */
PDU(bind_transmitter,
0x0002,
HEADER
@@ -225,10 +230,11 @@
INTEGER(sm_length, 1)
OCTETS(short_message, sm_length)
OPTIONAL_BEGIN
+/* defined in SMPP v3.4 */
TLV_INTEGER(user_message_reference, 2)
TLV_INTEGER(source_port, 2)
TLV_INTEGER(source_addr_subunit, 1)
-TLV_INTEGER(destination_port, 2)
+TLV_INTEGER(destination_port, 2) /* renamed to 'dest_port' in SMPP v5.0
?? */
TLV_INTEGER(dest_addr_subunit, 1)
TLV_INTEGER(sar_msg_ref_num, 2)
TLV_INTEGER(sar_total_segments, 1)
@@ -253,6 +259,23 @@
TLV_INTEGER(its_reply_type, 1)
TLV_OCTETS(its_session_info, 2, 2)
TLV_OCTETS(ussd_service_op, 1, 1)
+/* added in SMPP v5.0 */
+TLV_OCTETS(billing_identification, 1, 1024)
+TLV_INTEGER(dest_addr_np_country, 5)
+TLV_OCTETS(dest_addr_np_information, 10, 10)
+TLV_INTEGER(dest_addr_np_resolution, 1)
+TLV_INTEGER(dest_bearer_type, 1)
+TLV_NULTERMINATED(dest_network_id, 65)
+TLV_INTEGER(dest_network_type, 1)
+TLV_OCTETS(dest_node_id, 6, 6)
+TLV_INTEGER(dest_telematics_id, 2)
+TLV_INTEGER(qos_time_to_live, 4)
+TLV_INTEGER(set_dpf, 1)
+TLV_INTEGER(source_bearer_type, 1)
+TLV_NULTERMINATED(source_network_id, 65)
+TLV_INTEGER(source_network_type, 1)
+TLV_OCTETS(source_node_id, 6, 6)
+TLV_INTEGER(source_telematics_id, 1)
OPTIONAL_END
)
@@ -260,6 +283,13 @@
0x8004,
HEADER
NULTERMINATED(message_id, 65)
+ OPTIONAL_BEGIN
+ /* added in SMPP v5.0 */
+TLV_NULTERMINATED(additional_status_info_text, 256)
+TLV_INTEGER(delivery_failure_reason, 1)
+TLV_INTEGER(dpf_result, 1)
+TLV_OCTETS(network_error_code, 3, 3)
+OPTIONAL_END
)
PDU(submit_multi,
@@ -283,6 +313,7 @@
INTEGER(sm_length, 1)
OCTETS(short_message, sm_length)
OPTIONAL_BEGIN
+/* defined in SMPP v3.4 */
TLV_INTEGER(user_message_reference, 2)
TLV_INTEGER(source_port, 2)
TLV_INTEGER(source_addr_subunit, 1)
@@ -305,6 +336,28 @@
TLV_INTEGER(ms_msg_wait_facilities, 1)
TLV_INTEGER(alert_on_message_delivery, 0)
TLV_INTEGER(language_indicator, 1)
+/* added in SMPP v5.0 */
+TLV_OCTETS(billing_identification, 1, 1024)
+TLV_INTEGER(dest_addr_np_country, 5)
+TLV_OCTETS(dest_addr_np_information, 10, 10)
+TLV_INTEGER(dest_addr_np_resolution, 1)
+TLV_INTEGER(dest_bearer_type, 1)
+TLV_NULTERMINATED(dest_network_id, 65)
+TLV_INTEGER(dest_network_type, 1)
+TLV_OCTETS(dest_node_id, 6, 6)
+TLV_INTEGER(dest_telematics_id, 2)
+TLV_INTEGER(its_reply_type, 1)
+TLV_OCTETS(its_session_info, 2, 2)
+TLV_INTEGER(more_messages_to_send, 1)
+TLV_INTEGER(number_of_messages, 1)
+TLV_INTEGER(qos_time_to_live, 4)
+TLV_INTEGER(set_dpf, 1)
+TLV_INTEGER(source_bearer_type, 1)
+TLV_NULTERMINATED(source_network_id, 65)
+TLV_INTEGER(source_network_type, 1)
+TLV_OCTETS(source_node_id, 6, 6)
+TLV_INTEGER(source_telematics_id, 1)
+TLV_INTEGER(user_response_code, 1)
OPTIONAL_END
)
@@ -313,6 +366,15 @@
[PATCH] Parlay/X and GSMA OneAPI support
Hi list,
after further revision of the gSOAP support patch that enables Kannel to
used Ericsson's Parlay/X and GSMA's OneAPI SOAP interfaces for SMS
sending and receiving, here is the latest patchset, which is drastically
reduced.
We're expecting the system to host the gsoap import/ and plugin/
directories in the /usr/share/gsoap place, as most common distro do.
Please find the latest (version 6) patchset for this at URL:
http://www.kannel.org/~tolj/patchsets/gSOAP/gateway-gsoap.v6.diff
Comments are always welcome. If no further objections are posted, I'll
be committing the changes to the SVN trunk within the next days.
Stipe
--
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: devel Digest, Vol 74, Issue 7
*1) do you have a manual for it?* http://www.bluocean.biz/gsm_modem.html#usb_gprs model 2 is the GSM modem.. *2) what kind of GSM modem options have you configured?* group = core admin-port = 13000 smsbox-port = 13001 admin-password = hariom status-password = foo admin-deny-ip = admin-allow-ip = log-level = 0 log-file = /var/log/kannel/kannel.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 access-log = /var/log/kannel/access.log store-location= /var/log/kannel/a-z.log smsbox-max-pending = 10 unified-prefix = 91,0091,+91,091 group = smsc smsc = at smsc-id = Bluocean modemtype = Bluocean device = /dev/ttyUSB0 my-number = +6583640330 speed = 115200 log-level = 0 log-file = /var/log/kannel/smsc.log group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log log-level = 0 # MODEM DEFINITIONS group = modems id = wavecom name = wavecom detect-string = wavecom init-string = ATZ reset-string = ATZ group = smsbox bearerbox-host = localhost sendsms-port = 13003 global-sender = 9718500594 #sendsms-url = http://localhost:13003/cgi-bin/sendsms; access-log = /var/log/kannel/smsaccess.log log-file = /var/log/kannel/smsbox.log log-level = 0 # SEND-SMS USERS group = sendsms-user username = virendra password = bhati #- # SERVICES group = sms-service keyword = default text = This facility is down for maintenance. accept-x-kannel-headers = true max-messages = 1 concatenation = true get-url = http://localhost/playsms/plugin/gateway/kannel/geturl.php?t=%tq=%qa=%a; group = mysql-connection id = mydlr host = localhost username = root password = database = playsms max-connections = 1 group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc3)what does the bearerbox.log say if you enable log-level = 0 ? *what does the bearerbox.log say if you enable log-level = 0 ?* Right now dedicated server center is down when come up then I will provide that details as well. On Tue, Oct 9, 2012 at 12:09 AM, devel-requ...@kannel.org wrote: Send devel mailing list submissions to devel@kannel.org To subscribe or unsubscribe via the World Wide Web, visit http://www.kannel.org/mailman/listinfo/devel or, via email, send a message with subject or body 'help' to devel-requ...@kannel.org You can reach the person managing the list at devel-ow...@kannel.org When replying, please edit your Subject line so it is more specific than Re: Contents of devel digest... Today's Topics: 1. GSM Modem is not sending SMS or even not putting into queue (virendra bhati) 2. Re: GSM Modem is not sending SMS or even not putting into queue (Andreas Fink) 3. [PATCH] Kannel SMPP v5.0 support (Stipe Tolj) -- Forwarded message -- From: virendra bhati virbh...@gmail.com To: devel@kannel.org, devel-requ...@kannel.org Cc: Date: Mon, 8 Oct 2012 23:09:13 +0530 Subject: GSM Modem is not sending SMS or even not putting into queue Hi Team, I have installed Kannel and working perfectly with *Ubuntu 12.04.1 LTS*. But I am not able to installed *BluOcean™ USB GSM / GPRS Modem*. Could you please help me so that I will configure and used my GSM modem for sending SMS from Kannel. -- Thanks and regards Virendra Bhati +91-9718500594 Asterisk Developer E-mail-: virbh...@gmail.com Skype id:- virbhati2 New Delhi(India) [image: View my profile on LinkedIn]http://in.linkedin.com/pub/virendra-bhati/6/a30/755 -- Forwarded message -- From: Andreas Fink af...@list.fink.org To: virendra bhati virbh...@gmail.com Cc: devel Devel devel@kannel.org Date: Mon, 8 Oct 2012 19:42:15 +0200 Subject: Re: GSM Modem is not sending SMS or even not putting into queue On 08.10.2012, at 19:39, virendra bhati virbh...@gmail.com wrote: Hi Team, I have installed Kannel and working perfectly with *Ubuntu 12.04.1 LTS*. But I am not able to installed *BluOcean™ USB GSM / GPRS Modem*. Could you please help me so that I will configure and used my GSM modem for sending SMS from Kannel. do you have a manual for it? what kind of GSM modem options have you configured? what does the bearerbox.log say if you enable log-level = 0 ? Usually its only a question of finding the right init strings...(which can be tricky at times...) -- Thanks and regards Virendra Bhati +91-9718500594 Asterisk Developer E-mail-: virbh...@gmail.com Skype id:- virbhati2 New Delhi(India) [image: View my profile on LinkedIn]http://in.linkedin.com/pub/virendra-bhati/6/a30/755 -- Forwarded message -- From: Stipe Tolj st...@kannel.org To: devel@kannel.org Cc: Date: Mon, 08 Oct 2012 20:39:20 +0200 Subject: [PATCH] Kannel SMPP v5.0 support Hi list, please find attached a patchset that adds all the
Re: GSM Modem is not sending SMS or even not putting into queue
you have modemtype = Bluocean but no modem definition with that name in the config file. Try adding this: group = modems id = Bluocean name = Bluocean speed = 115200 detect-string = Bluocean detect-string2 = init-string = AT+CNMI=2,2,2,1,0 enable-hwhs = need-sleep = true no-pin = true no-smsc = false sendline-sleep = 100 keepalive-cmd = AT broken = false message-storage = SM hardware-flow-control = false reset-string = AT+CFUN=1 You might have to play with the init string, hardware handshake, speed etc. Above settings is what I use with my wavecom modems which are pretty much following the GSM standards. Trial and error helps there. Just set it up and watch the bearerbox logfile to see what kannel does do when talking to the modem and how the modem reacts. Especially in cases where you have lots of incoming SMS or delivery reports. On 09.10.2012, at 06:04, virendra bhati virbh...@gmail.com wrote: 1) do you have a manual for it? http://www.bluocean.biz/gsm_modem.html#usb_gprs model 2 is the GSM modem.. 2) what kind of GSM modem options have you configured? group = core admin-port = 13000 smsbox-port = 13001 admin-password = hariom status-password = foo admin-deny-ip = admin-allow-ip = log-level = 0 log-file = /var/log/kannel/kannel.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 access-log = /var/log/kannel/access.log store-location= /var/log/kannel/a-z.log smsbox-max-pending = 10 unified-prefix = 91,0091,+91,091 group = smsc smsc = at smsc-id = Bluocean modemtype = Bluocean device = /dev/ttyUSB0 my-number = +6583640330 speed = 115200 log-level = 0 log-file = /var/log/kannel/smsc.log group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log log-level = 0 # MODEM DEFINITIONS group = modems id = wavecom name = wavecom detect-string = wavecom init-string = ATZ reset-string = ATZ group = smsbox bearerbox-host = localhost sendsms-port = 13003 global-sender = 9718500594 #sendsms-url = http://localhost:13003/cgi-bin/sendsms; access-log = /var/log/kannel/smsaccess.log log-file = /var/log/kannel/smsbox.log log-level = 0 # SEND-SMS USERS group = sendsms-user username = virendra password = bhati #- # SERVICES group = sms-service keyword = default text = This facility is down for maintenance. accept-x-kannel-headers = true max-messages = 1 concatenation = true get-url = http://localhost/playsms/plugin/gateway/kannel/geturl.php?t=%tq=%qa=%a; group = mysql-connection id = mydlr host = localhost username = root password = database = playsms max-connections = 1 group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc3)what does the bearerbox.log say if you enable log-level = 0 ? what does the bearerbox.log say if you enable log-level = 0 ? Right now dedicated server center is down when come up then I will provide that details as well. On Mon, Oct 8, 2012 at 11:12 PM, Andreas Fink af...@list.fink.org wrote: On 08.10.2012, at 19:39, virendra bhati virbh...@gmail.com wrote: Hi Team, I have installed Kannel and working perfectly with Ubuntu 12.04.1 LTS. But I am not able to installed BluOcean™ USB GSM / GPRS Modem. Could you please help me so that I will configure and used my GSM modem for sending SMS from Kannel. do you have a manual for it? what kind of GSM modem options have you configured? what does the bearerbox.log say if you enable log-level = 0 ? Usually its only a question of finding the right init strings...(which can be tricky at times...) -- Thanks and regards Virendra Bhati +91-9718500594 Asterisk Developer E-mail-: virbh...@gmail.com Skype id:- virbhati2 New Delhi(India) -- Thanks and regards Virendra Bhati +91-9718500594 Asterisk Developer E-mail-: virbh...@gmail.com Skype id:- virbhati2 New Delhi(India)
