NumminorihSF / ami-io

Use node.js or io.js to manage Asterisk through AMI
MIT License
30 stars 16 forks source link

Don't get all data from chanvariable when it contain two params #4

Closed Seafnox closed 8 years ago

Seafnox commented 8 years ago

Result message from ami-io

{
"variables":{},
"event":"Bridge",
"privilege":"call,all",
"timestamp":1469112499000,
"bridgestate":"Unlink",
"bridgetype":"core",
"channel1":"SIP/with-TSE-LIM2-0000a194",
"channel2":"Local/5842@from-queue-0000af99;1",
"uniqueid1":"1469111531.131272",
"uniqueid2":"1469111552.131275",
"callerid1":"4959810606",
"callerid2":"5836",
"chanvariable(sip/with_tse_lim2_0000a194)":"CDR(dst)=5899",
"chanvariable(local/5842@from_queue_0000af99;1)":"CDR(dst)=5842"
}

Incomming event from server

"incomingData":[
"Event: Bridge",
"Privilege: call,all",
"Timestamp: 1469112499.321389",
"Bridgestate: Unlink",
"Bridgetype: core",
"Channel1: SIP/with-TSE-LIM2-0000a194",
"Channel2: Local/5842@from-queue-0000af99;1",
"Uniqueid1: 1469111531.131272",
"Uniqueid2: 1469111552.131275",
"CallerID1: 4959810606",
"CallerID2: 5836",
"ChanVariable(SIP/with-TSE-LIM2-0000a194): CDR(linkedid)=1469111531.131272",
"ChanVariable(SIP/with-TSE-LIM2-0000a194): CDR(dst)=5899",
"ChanVariable(Local/5842@from-queue-0000af99;1): CDR(linkedid)=1469111531.131272",
"ChanVariable(Local/5842@from-queue-0000af99;1): CDR(dst)=5842"]

In this case REAL message from ami-io must have view:

"variables":{},
"event":"Bridge",
"privilege":"call,all",
"timestamp":1469112499000,
"bridgestate":"Unlink",
"bridgetype":"core",
"channel1":"SIP/with-TSE-LIM2-0000a194",
"channel2":"Local/5842@from-queue-0000af99;1",
"uniqueid1":"1469111531.131272",
"uniqueid2":"1469111552.131275",
"callerid1":"4959810606",
"callerid2":"5836",
"chanvariable(sip/with_tse_lim2_0000a194)": [
  "CDR(linkedid)=1469111531.131272",
  "CDR(dst)=5899"
],
"chanvariable(local/5842@from_queue_0000af99;1)": [
  "CDR(linkedid)=1469111531.131272",
  "CDR(dst)=5842"
],

this type of variaables using in different asterisk event and must be parsed everywhere.

NumminorihSF commented 8 years ago

Fixed in 27979b7 Release 1.0.0