Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Tags: andyfenggq/ari

Tags

v5.0.0-pre3

Toggle v5.0.0-pre3's commit message
update mock for bridge API change

v5.0.0-pre2

Toggle v5.0.0-pre2's commit message
Allow subscription to all events (CyCoreSystems#102)

Allows the websocket to be created with the subscribeAll flag set, to read events outside the scope of the specified ARI application.

v5.0.0-pre1

Toggle v5.0.0-pre1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Add AddChannelWithOptions (CyCoreSystems#101)

Adds support for additional options to be passed when adding a channel
to a bridge.

Fixes CyCoreSystems#100

v4.8.4

Toggle v4.8.4's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Originate: change key to referenceKey (CyCoreSystems#99)

Having the "key" field to Originate and StageOriginate is confusing.  It
is easy to think that you should pass in the key for the channel you
wish to create, rather than it being a completely optional "originator"
key.  Therefore, this patch changes the name of the variable to
`referenceKey` so as to disambiquate the two, as well as offering an
explanation in the comments.

v4.8.3

Toggle v4.8.3's commit message
[style] Do not mix implicit and explicit returns

Addresses CyCoreSystems#93 readability

v4.8.2

Toggle v4.8.2's commit message
update mocks

v4.8.1

Toggle v4.8.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request CyCoreSystems#91 from CyCoreSystems/issue-90

add MOH and StopMOH to bridge

v4.8.0

Toggle v4.8.0's commit message
do not lint before dep

v4.7.2

Toggle v4.7.2's commit message
Ignored error in StageOriginate? (CyCoreSystems#89)

* Ignored error in StageOriginate?

If I read it correctly, we're currently returning nil here regardless of whether there is an error when doing originate or not. Shall we instead return the same value that we get from c.client.post(...)?

I tested by originating to unreachable destinations and the original version did not return an error, while the proposed one did. Please let me know if any more details could be helpful. Thanks!

v4.7.1

Toggle v4.7.1's commit message
do not treat empty timestamps as catastrophic