Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Zimlets

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-05-2006, 11:16 PM
Starter Member
 
Posts: 2
Default sms zimlet troubleshooting

Morning.

Hmmm. I would appreciate a little help if someone can point me in the right direction. I followed the general instructions to deploy the sms zimlet as per:
http://wiki.zimbra.com/index.php?title=SMS_Zimlet - as I am clearly missing something.

Steps to deply sms zimlet:

$su - zimbra
$cd zimlets-extras/
$zmzimletctl deploy com_zimbra_sms.zip
$zmzimletctl getConfigTemplate com_zimbra_sms.zip > cfg.tmp
$vi cfg.tmp
Changed the settings to match my ipipi.com account. wq!
$zmzimletctl configure cfg.tmp
$tomcat restart

I should mention that my cfg.tmp looks as follows:

<zimletConfig name="com_zimbra_sms" version="1.0">
<global>
<property name="smsusername">MyUserName</property>
<property name="smspassword">MyPassWord</property>
<property name="smsfrom">SN</property>
</global>
</zimletConfig>

Where MyUserName, MyPassWord and SN are my actual detals as per ipipi.com. I have tested ipipi.com via the web interface and do not have any issues with the service.

Whenever I send a message via the sms zimlet I get: Error could not SMS +6143xxxxxxx - this is after I fudged the sms.jsp to look as follows due to the code inserting a +1 (USA) country code bit. I basically just inserted '6' - for the time being (+61 being the country code for australia) - to test the service:

if (!phone_num.startsWith("+61")) {
if (phone_num.startsWith("6")) {
phone_num = "+" + phone_num;
} else {
phone_num = "+61" + phone_num;
}
}

Even with this alteration I am unable to sms and still get the "Error: Unable to SMS +6143xxxxxxx" error message. I've checked over a few things but don't seem to be able to find a place to where the freaking zimlet is logging its errors. It is not logging to zimbra.log nor anywhere else I could find.

Only thing I have not done as yet is to dump out the ldap schemer, I assume that the sms part within the default schemer was simply overwritten rather then added to everytime I have re-deployed the sms zimlet?

Any help would be much appreciated.

Rgs,

Dan

Release 4.0 on a Fedora Core 5 box.

Last edited by switchnetworks; 09-06-2006 at 12:36 AM..
Reply With Quote
  #2 (permalink)  
Old 09-08-2006, 01:35 PM
Zimbra Employee
 
Posts: 4,792
Default

Try increasing the zimlet version if you changed it. We ignore changes if the version is the same.
__________________
Bugzilla - Wiki - Downloads - Offline Client
Reply With Quote
  #3 (permalink)  
Old 09-10-2006, 09:13 PM
Starter Member
 
Posts: 2
Default

Increased the version. Re-checked settings. Disabled. Undeployed. Redeployed.
Still not getting it to work. Here is a packet dump of the proceedings. All is ok until I get to the RCPT TO: bit and it fails.

0.000000 202.157.179.149 -> 69.28.206.212 TCP 49524 > smtp [FIN, ACK] Seq=0 Ack=0 Win=5840 Len=0
11.074003 202.157.179.149 -> 69.28.206.212 TCP 53245 > smtp [SYN] Seq=0 Len=0 MSS=1460
11.254581 69.28.206.212 -> 202.157.179.149 TCP smtp > 53245 [SYN, ACK] Seq=0 Ack=1 Win=16352 Len=0 MSS=1460
11.254620 202.157.179.149 -> 69.28.206.212 TCP 53245 > smtp [ACK] Seq=1 Ack=1 Win=5840 Len=0
16.138999 69.28.206.212 -> 202.157.179.149 SMTP Response: 220 SMTP service ready
16.139305 202.157.179.149 -> 69.28.206.212 TCP 53245 > smtp [ACK] Seq=1 Ack=25 Win=5840 Len=0
16.141662 202.157.179.149 -> 69.28.206.212 SMTP Command: EHLO web2
16.331633 69.28.206.212 -> 202.157.179.149 SMTP Response: 250-Requested mail action okay, completed
16.332260 202.157.179.149 -> 69.28.206.212 SMTP Command: AUTH LOGIN
16.512656 69.28.206.212 -> 202.157.179.149 SMTP Response: 334 VXNlcm5hbWU6
16.513605 202.157.179.149 -> 69.28.206.212 SMTP Message Body
16.693929 69.28.206.212 -> 202.157.179.149 SMTP Response: 334 UGFzc3dvcmQ6
16.694229 202.157.179.149 -> 69.28.206.212 SMTP Message Body
16.890553 69.28.206.212 -> 202.157.179.149 TCP smtp > 53245 [ACK] Seq=180 Ack=64 Win=16289 Len=0
16.902296 69.28.206.212 -> 202.157.179.149 SMTP Response: 235 Authentication successful
16.939582 202.157.179.149 -> 69.28.206.212 TCP 53245 > smtp [ACK] Seq=64 Ack=211 Win=5840 Len=0
16.959489 202.157.179.149 -> 69.28.206.212 SMTP Command: MAIL FROM:<accounts@domain.com.au>
17.140045 69.28.206.212 -> 202.157.179.149 SMTP Response: 250 Requested mail action okay, completed
17.140352 202.157.179.149 -> 69.28.206.212 TCP 53245 > smtp [ACK] Seq=108 Ack=254 Win=5840 Len=0
17.140568 202.157.179.149 -> 69.28.206.212 SMTP Command: RCPT TO:<+61438XXXXXX@sms.ipipi.com>
17.320933 69.28.206.212 -> 202.157.179.149 SMTP Response: 503 Bad sequence of commands
17.321898 202.157.179.149 -> 69.28.206.212 SMTP Command: RSET
17.502833 69.28.206.212 -> 202.157.179.149 SMTP Response: 250 Requested mail action okay, completed
17.539389 202.157.179.149 -> 69.28.206.212 TCP 53245 > smtp [ACK] Seq=152 Ack=327 Win=5840 Len=0
Reply With Quote
  #4 (permalink)  
Old 09-13-2007, 02:35 AM
Member
 
Posts: 11
Default

Does anyone have this zimlet working yet - I have tried all the permmutations and it still won't do it
Reply With Quote
  #5 (permalink)  
Old 09-13-2007, 04:46 AM
Moderator
 
Posts: 6,237
Default

I had it working fine, but the sms zimlet relies on having an account at sms.ipipi.com-and it seems they've gotten rid of their unlimited free sending; then for a bit they used to have 50/month free...

Now, you only get '3.00 SMS Credits' for free. Then 15c/message - I really think we should explore other options...because by the time you make sure that it doesnt get hit by any spam filters/protocol checks & that the zimlet works properly, you've already used up your 3 tries, and that's certainly not enough to serve an organization.

Yes the idea would be to buy in chunks of '1501' for your entire organization (weird # I know - but apparently you purchase in chunks of it's 50, 100, 400, 1501)
But at 10c that's still $150. Then keeping track of who sent what if you had to tell them to slow down...doesn't seem productive.

Last edited by mmorse; 09-13-2007 at 05:06 AM..
Reply With Quote
  #6 (permalink)  
Old 09-13-2007, 05:27 AM
Member
 
Posts: 11
Default

Hi Mike

I set up the ipipi account yesterday and have changed the params in the files to reflect that with user name and pw etc but it just keeps saying it can't send

R
Reply With Quote
  #7 (permalink)  
Old 03-04-2008, 07:16 AM
Member
 
Posts: 11
Default

Seems that no one knows (or cares?) about this

Does anyone have it working at all please who can help?
Reply With Quote
  #8 (permalink)  
Old 03-04-2008, 10:36 AM
Former Zimbran
 
Posts: 5,606
Default

Can you provide more info? "It doesn't work" isn't helpful.
Reply With Quote
  #9 (permalink)  
Old 03-10-2008, 11:31 PM
Member
 
Posts: 11
Default

Well here's what I did:

1) Signed up for ipipi.com
2) Paid and got credits
3) Tested Ipipi from their own site with a message to my mobile phone (in France)
4) Changed the settings in the zimlet to contain my username and password for ipipi
5) I reloaded everything on our zimbra NE server
6) Right clicked the zimlet and put in my +33 xxxx number and a message
7) Zimlet said "sms sent" with the green message thing etc
8) Message never ever arrives

Is there a log I can look at somewhere maybe that might give a clue?

Thanks
Reply With Quote
  #10 (permalink)  
Old 03-15-2008, 11:58 PM
Intermediate Member
 
Posts: 15
Default changing ipipi.com

can i change and make sms zimlet use someother sms gateway ?
__________________
thanks

Aadil
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.