Closed cbetta closed 8 years ago
@sammachin do you have any samples of what valid sip/tel/vmxl updates look like for https://docs.nexmo.com/tools/developer-api/number-update ?
So the types and example values are as follows:
app, [uuid] eg 67676c91-1d73-4fc7-a1d7-b9d6f1a580b6
tel, [e.164 number] eg +447970513607
sip, [sip uri] eg sip:100@sip.sammachin.com
vxml, [url] eg https://example.com/app.vxml
Also the SMS callback URL could be set but that uses the moHttpUrl param, so if the type = sms then set the value to moHttpUrl
Cool. Sounds like we can do this all under the link/unlink command then
Notes from me and Sam:
nexmo link:app <number> <app_id>
nexmo link:sms <number> <callback_url>
nexmo link:tel <number> <other_number>
nexmo link:sip <number> <sip_uri>
nexmo link:vxml <number> <callback_url>
nexmo number:update <country> <msisdn> --moHttpUrl <moHttpUrl> —moSmppSysType <moSmppSysType>
and
nexmo link <number> <destination> —type <type>
nexmo link:app <number> <app_id>
nexmo link:sms <number> <callback_url>
nexmo link:tel <number> <other_number> —statuscallback <url>
nexmo link:sip <number> <sip_uri> —statuscallback <url>
nexmo link:vxml <number> <callback_url> —statuscallback <url>
I think we also decided to drop the plan 'link' command.
Yeah agreed. Just quickly dumped our notes :)
just tested and you can have a status callback url set when a number is forwarded to tel (I assume same goes for SIP)
Cool so works everywhere?
No Only on voicexml, tel or sip Not on app or sms
Thanks for clarifying. Will make implementing it easier.
A simple version of this has currently been implemented for the
app
type but there are other types.