readme instructions lead to unexpected result

[nthiad]

When I follow the steps from the readme, the first curl command works ok:

$ curl -d "address=12341234" https://nuntium-stg.instedd.org/tickets.json
{"code":"XXXX","secret_key":"...","status":"pending","data":{"address":"12341234"}}

but the second one returns a response identical to the first:

$ curl 'https://nuntium-stg.instedd.org/tickets/XXXX.json?secret_key=....'
{"code":"XXXX","secret_key":"...","status":"pending","data":{"address":"12341234"}}

[ysbaddaden]

I can only make hypothesis, here, but I suppose the channel didn't get properly setup with the 4 digits pin (not associated, or a network issue, or a plain bug)? @matiasgarciaisaia probably knows much better.

[ysbaddaden]

I doubt it, but maybe one of Nuntium's worker isn't running (workerfast, workerslow or sched or cron maybe), and a request from Nuntium to the QST simulator is pending?

[matiasgarciaisaia]

Where have you created the QST Server channel?