December 16, 2010

Making Calls With Twilio Sand Box

I have been playing with Twilio in the past weeks. It is pretty good and I have been able to send SMS from day one.
All good so far.
But I have failed miserably at placing calls.
Nothing showed in Twilio's debugger and it seemed as if nothing was even be triggered in Twilio at all.


Of course, I debugged my app (more details on that later) by pointing it to a mock Twilio service and it seemed to be doing everything it should. I have been pulling my hair over this issue for quite a while.
Sending SMS from my sandbox number, say +14156669999 to my cell, say +15127778888 works like a charm.... so why would placing a call from the same sandbox number to the same cell woud fail ? No idea. But that's just the way it is.


What you have to do is register one of your own numbers and initiate the call from the validated phone number to the cell number. The numbers I am talking about show in the Twilio account, on the "Phone Numbers" tab, in the section titled "My outgoing callerid numbers".
Unlike for SMS, you MUST use one of these numbers or Twilio just won't budge. Not even acknowledge that this is not what it expects....


be warned!

December 15, 2010

Easily Persist Java To Any Directory Server

Rationale
Simply providing a trivial example to get you started.


The Meat
To make it really trivial, I will use a very simple object that already exists in the default schema, the person object class. This class only requires the person to have a first and last name, respectively stored in the cn (or commonName) and sn (or surname) attributes. To spice it up a bit and make it remotely useful, let's say we also expect a person to have a password so we can authenticate them later. The default schema allows us to do so in the userPassword attribute.


The whole idea of persistence is that you don't have to worry at all about the LDAP. All you need to do is 



>generate-source-from-schema -h localhost -p 389 -D "cn=directory manager" -w password --outputDirectory src/com/example --structuralClass person --rdnAttribute cn --defaultParentDN dc=example,dc=com --packageName com.example --className Person --terse


When you have done this, you have a Person.java in src/com/example created for you.
We'll go ahead and create a groovy script file in src/com/example to add a new guy in our directory server:

package com.example
import com.unboundid.ldap.sdk.LDAPConnection;
import com.unboundid.ldap.sdk.persist.LDAPPersister;
def cx = new LDAPConnection("localhost",389,"cn=directory manager","password")
def persister = LDAPPersister.getInstance(Person.class)
def newGuy = new Person()
newGuy.setCn('new')
newGuy.setSn('guy')
newGuy.setUserPassword('changeme')
persister.add(newGuy, cx, null)



That's it!
Yes, that really is it. Unbelievable? Try for yourself.