Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected Properties In Events #8

Closed
louishawkins opened this issue Jan 25, 2017 · 1 comment
Closed

Unexpected Properties In Events #8

louishawkins opened this issue Jan 25, 2017 · 1 comment

Comments

@louishawkins
Copy link

I've noticed in the case of a "Bridge" event that amigo will produce extra properties AccountCode, Channel, Uniqueid.

When connecting to the same box using Nami (the NodeJS client) these properties are not on the event object.

Why would the same AMI produce different data?

According to the documentation we should only have the following for a bridge event:

Event: Bridge
Bridgestate: <value>
Bridgetype: <value>
Channel1: <value>
Channel2: <value>
Uniqueid1: <value>
Uniqueid2: <value>
CallerID1: <value>
CallerID2: <value>

NAMI Event:

{ Event: 'Bridge',
  Privilege: 'call,all',
  Bridgestate: 'Link',
  Bridgetype: 'core',
  Channel1: 'SIP/1180-000005fd',
  Channel2: 'SIP/Flowroute-000005fe',
  Uniqueid1: '1485316340.3781',
  Uniqueid2: '1485316340.3782',
  CallerID1: '15555551170',
  CallerID2: '15555551170' }

AMIGO Event:

map[Channel2:SIP/Flowroute-000005fe CallerID2:15555551170 AccountCode: Uniqueid2:1485316340.3782 CallerID1:15555551170 Channel:SIP/Flowroute-000005fe Bridgestate:Link Bridgetype:core Uniqueid1:1485316340.3781 Event:Bridge Privilege:call,all Uniqueid:1485316340.3782 OldAccountCode: Channel1:SIP/1180-000005fd]
@louishawkins
Copy link
Author

Upgrading to the latest version seemed to fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant