Anyone using Asterisk-IM with asterisk 1.6? It all seems good except for the incoming callerid popups. Worked fine in asterisk 1.4. I do know there are some changes in the manager API for 1.6. Anyone have some ideas? Thanks! --Fred
Oh and heres the manager API output for a typical call if someone wants to look at it and see the diferneces to the older API. Some of the obvious changes spotted ar that CallerID: from 1.4 in most cases becomes CallerIDNum: in 1.6 and Event: Link becomes Event: Bridge. Again thanks for any input anyone might have.
Event: NewchannelTimeStamp: 2008-10-15 17:30:58Privilege: call,allChannel: DAHDI/1-1ChannelState: 4ChannelStateDesc: RingCallerIDNum: 0000000000CallerIDName: AccountCode: Uniqueid: 1224113458.571
Event: NewextenTimeStamp: 2008-10-15 17:30:58Privilege: dialplan,allChannel: DAHDI/1-1Context: defaultExtension: 0000000000Priority: 1Application: MacroAppData: didexten,SIP/103,103,20Uniqueid: 1224113458.571
Event: NewextenTimeStamp: 2008-10-15 17:30:58Privilege: dialplan,allChannel: DAHDI/1-1Context: macro-didextenExtension: sPriority: 1Application: WaitAppData: 2Uniqueid: 1224113458.571
Event: NewCalleridTimeStamp: 2008-10-15 17:30:58Privilege: call,allChannel: DAHDI/1-1CallerIDNum: 0000000000CallerIDName: XXXXXXXXXXXXXXXXXUniqueid: 1224113458.571CID-CallingPres: 3 (Presentation Allowed, Network Number)
Event: NewstateTimeStamp: 2008-10-15 17:31:00Privilege: call,allChannel: DAHDI/1-1ChannelState: 6ChannelStateDesc: UpCallerIDNum: 0000000000CallerIDName: XXXXXXXXXXXXXXXXUniqueid: 1224113458.571
Event: NewextenTimeStamp: 2008-10-15 17:31:01Privilege: dialplan,allChannel: DAHDI/1-1Context: macro-didextenExtension: sPriority: 11Application: DialAppData: SIP/103,20,twkUniqueid: 1224113458.571
Event: NewchannelTimeStamp: 2008-10-15 17:31:01Privilege: call,allChannel: SIP/103-08339fd0ChannelState: 0ChannelStateDesc: DownCallerIDNum: CallerIDName: AccountCode: Uniqueid: 1224113461.572
Event: ChannelUpdateTimeStamp: 2008-10-15 17:31:01Privilege: system,allChannel: SIP/103-08339fd0Uniqueid: 1224113461.572Channeltype: SIPSIPcallid: firstname.lastname@example.orgSIPfullcontact: sip:email@example.com:5060
Event: ChannelUpdateTimeStamp: 2008-10-15 17:31:01Privilege: system,allChannel: SIP/103-08339fd0Channeltype: SIPSIPcallid: firstname.lastname@example.orgSIPfullcontact: sip:email@example.com:5060Peername: 103
Event: DialTimeStamp: 2008-10-15 17:31:01Privilege: call,allSubEvent: BeginChannel: DAHDI/1-1Destination: SIP/103-08339fd0CallerIDNum: 0000000000CallerIDName:XXXXXXXXXXXXXXXXUniqueID: 1224113458.571DestUniqueID: 1224113461.572Dialstring: 103
Event: NewCalleridTimeStamp: 2008-10-15 17:31:01Privilege: call,allChannel: SIP/103-08339fd0CallerIDNum: 5059384795CallerIDName: Uniqueid: 1224113461.572CID-CallingPres: 3 (Presentation Allowed, Network Number)
Event: NewstateTimeStamp: 2008-10-15 17:31:01Privilege: call,allChannel: SIP/103-08339fd0ChannelState: 5ChannelStateDesc: RingingCallerIDNum: 0000000000CallerIDName: Uniqueid: 1224113461.572
Event: ChannelUpdateTimeStamp: 2008-10-15 17:31:04Privilege: system,allChannel: SIP/103-08339fd0Channeltype: 1224113461.572Uniqueid: SIPSIPcallid: firstname.lastname@example.orgSIPfullcontact: sip:email@example.com:5060Peername: 103
Event: NewstateTimeStamp: 2008-10-15 17:31:04Privilege: call,allChannel: SIP/103-08339fd0ChannelState: 6ChannelStateDesc: UpCallerIDNum: 0000000000CallerIDName: Uniqueid: 1224113461.572
Event: BridgeTimeStamp: 2008-10-15 17:31:04Privilege: call,allBridgestate: LinkBridgetype: coreChannel1: DAHDI/1-1Channel2: SIP/103-08339fd0Uniqueid1: 1224113458.571Uniqueid2: 1224113461.572CallerID1: 0000000000CallerID2: 0000000000
Event: UnlinkTimeStamp: 2008-10-15 17:31:07Privilege: call,allChannel1: DAHDI/1-1Channel2: SIP/103-08339fd0Uniqueid1: 1224113458.571Uniqueid2: 1224113461.572CallerID1: 0000000000CallerID2: 0000000000
Event: HangupTimeStamp: 2008-10-15 17:31:08Privilege: call,allChannel: SIP/103-08339fd0Uniqueid: 1224113461.572CallerIDNum: 0000000000CallerIDName: <unknown>Cause: 16Cause-txt: Normal Clearing
Event: DialTimeStamp: 2008-10-15 17:31:08Privilege: call,allSubEvent: EndChannel: DAHDI/1-1UniqueID: 1224113458.571DialStatus: ANSWER
Event: HangupTimeStamp: 2008-10-15 17:31:08Privilege: call,allChannel: DAHDI/1-1Uniqueid: 1224113458.571CallerIDNum: 0000000000CallerIDName: XXXXXXXXXXXXXXCause: 16Cause-txt: Normal Clearing
And as well for anyone who might want to look at it. The 1.6 manager API doc for the changes that are in the new API:
- Manager version changed to 1.1
* CHANGED EVENTS AND ACTIONS----------------------------- The Hold/Unhold events - Both are now "Hold" events For hold, there's a "Status: On" header, for unhold, status is off - Modules chan_sip/chan_iax2
- The Ping Action - Now use Response: success - New header "Ping: pong" :-)
- The Events action - Now use Response: Success - The new status is reported as "Events: On" or "Events: Off"
- The JabberSend action - The Response: header is now the first header in the response - now sends "Response: Error" instead of "Failure"
- Newstate and Newchannel events - these have changed headers "State" -> ChannelStateDesc Text based channel state -> ChannelState Numeric channel state - The events does not send "<unknown>" for unknown caller IDs just an empty field
- Newchannel event - Now includes "AccountCode"
- Newstate event - Now has "CalleridNum" for numeric caller id, like Newchannel - The event does not send "<unknown>" for unknown caller IDs just an empty field
- Newexten and VarSet events - Now are part of the new Dialplan privilege class, instead of the Call class
- Dial event - Event Dial has new headers, to comply with other events - Source -> Channel Channel name (caller) - SrcUniqueID -> UniqueID Uniqueid (new) -> Dialstring Dialstring in app data
- Link and Unlink events - The "Link" and "Unlink" bridge events in channel.c are now renamed to "Bridge" - The link state is in the bridgestate: header as "Link" or "Unlink" - For channel.c bridges, "Bridgetype: core" is added. This opens up for bridge events in rtp.c - The RTP channel also reports Bridge: events with bridgetypes - rtp-native RTP native bridge - rtp-direct RTP peer-2-peer bridge (NAT support only) - rtp-remote Remote (re-invite) bridge. (Not reported yet)
- The "Rename" manager event has a renamed header, to use the same terminology for the current channel as other events - Oldname -> Channel
- The "NewCallerID" manager event has a renamed header - CallerID -> CallerIDnum - The event does not send "<unknown>" for unknown caller IDs just an empty field - Reload event - The "Reload" event sent at manager reload now has a new header and is now implemented in more modules than manager to alert a reload. For channels, there's a CHANNELRELOAD event to use. (new) -> Module: manager | CDR | DNSmgr | RTP | ENUM (new) -> Status: enabled | disabled - To support reload events from other modules too - cdr module added
- Status action replies (Event: Status) Header changes - link -> BridgedChannel - Account -> AccountCode - (new) -> BridgedUniqueid
- StatusComplete Event New header - (new) -> Items Number of channels reported
- The ExtensionStatus manager command now has a "StatusDesc" field with text description of the state
- The Registry and Peerstatus events in chan_sip and chan_iax now use "ChannelType" instead of "ChannelDriver"
- The Response to Action: IAXpeers now have a Response: Success header
- The MeetmeJoin now has caller ID name and Caller ID number fields (like MeetMeLeave)
- Action DAHDIShowChannels Header changes - Channel: -> DAHDIChannel For active channels, the Channel: and Uniqueid: headers are added You can now add a "DAHDIChannel: " argument to DAHDIshowchannels actions to only get information about one channel.
- Event DAHDIShowChannelsComplete New header - (new) -> Items: Reports number of channels reported
- Action VoicemailUsersList Added new headers for SayEnvelope, SayCID, AttachMessage, CanReview and CallOperator voicemail configuration settings.
- Action Originate Now requires the new Originate privilege. If you call out to a subshell in Originate with the Application parameter, you now also need the System privilege.
* NEW ACTIONS-------------- Action: ModuleLoad Modules: loader.c Purpose: To be able to unload, reload and unload modules from AMI. Variables: ActionID: <id> Action ID for this transaction. Will be returned. Module: <name> Asterisk module name (including .so extension) or subsystem identifier: cdr, enum, dnsmgr, extconfig, manager, rtp, http LoadType: load | unload | reload The operation to be done on module If no module is specified for a reload loadtype, all modules are reloaded
- Action: ModuleCheck Modules: loader.c Purpose: To check version of a module - if it's loaded Variables: ActionID: <id> Action ID for this transaction. Will be returned. Module: <name> Asterisk module name (not including extension) Returns: If module is loaded, returns version number of the module Note: This will have to change. I don't like sending Response: failure on both command not found (trying this command in earlier versions of Asterisk) and module not found. Also, check if other manager actions behave that way.
- Action: QueueSummary Modules: app_queue Purpose: To request that the manager send a QueueSummary event (see the NEW EVENTS section for more details). Variables: ActionID: <id> Action ID for this transaction. Will be returned. Queue: <name> Queue for which the summary is desired
- Action: QueuePenalty Modules: app_queue Purpose: To change the penalty of a queue member from AMI Variables: Interface: <tech/name> The interface of the member whose penalty you wish to change Penalty: <number> The new penalty for the member. Must be nonnegative. Queue: <name> If specified, only set the penalty for the member for this queue; Otherwise, set the penalty for the member in all queues to which he belongs.
- Action: QueueRule Modules: app_queue Purpose: To list queue rules defined in queuerules.conf Variables: Rule: <name> The name of the rule whose contents you wish to list. If this variable is not present, all rules in queuerules.conf will be listed.
* NEW EVENTS------------
- Event: Transfer Modules: res_features, chan_sip Purpose: Inform about call transfer, linking transferer with transfer target You should be able to trace the call flow with this missing piece of information. If it works out well, the "Transfer" event should be followed by a "Bridge" event The transfermethod: header informs if this is a pbx core transfer or something done on channel driver level. For SIP, check the example: Example: Event: Transfer Privilege: call,all TransferMethod: SIP TransferType: Blind Channel: SIP/device1-01849800 SIP-Callid: firstname.lastname@example.org TargetChannel: SIP/device2-01841200 TransferExten: 100 TransferContext: default
- Event: ChannelUpdate Modules: chan_sip.c, chan_iax2.c Purpose: Updates channel information with ID of PVT in channel driver, to be able to link events on channel driver level. * Integrated in SVN trunk as of May 4th, 2007
Event: ChannelUpdate Privilege: system,all Uniqueid: 1177271625.27 Channel: SIP/olle-01843c00 Channeltype: SIP SIPcallid: NTQzYWFiOWM4NmE0MWRkZjExMzU2YzQ3OWQwNzg3ZmI. SIPfullcontact: sip:email@example.com:49054
- Action: CoreSettings Modules: manager.c Purpose: To report core settings, like AMI and Asterisk version, maxcalls and maxload settings. * Integrated in SVN trunk as of May 4th, 2007 Example: Response: Success ActionID: 1681692777 AMIversion: 1.1 AsteriskVersion: SVN-oej-moremanager-r61756M SystemName: EDVINA-node-a CoreMaxCalls: 120 CoreMaxLoadAvg: 0.000000 CoreRunUser: edvina CoreRunGroup: edvina
- Action: CoreStatus Modules: manager.c Purpose: To report current PBX core status flags, like number of concurrent calls, startup and reload time. * Integrated in SVN trunk as of May 4th, 2007 Example: Response: Success ActionID: 1649760492 CoreStartupTime: 22:35:17 CoreReloadTime: 22:35:17 CoreCurrentCalls: 20
- Event: NewAccountCode Modules: cdr.c Purpose: To report a change in account code for a live channel Example: Event: NewAccountCode Privilege: call,all Channel: SIP/olle-01844600 Uniqueid: 1177530895.2 AccountCode: Stinas account 1234848484 OldAccountCode: OllesAccount 12345
- Event: ModuleLoadReport Modules: loader.c Purpose: To report that module loading is complete. Some aggressive clients connect very quickly to AMI and needs to know when all manager events embedded in modules are loaded Also, if this does not happen, something is seriously wrong. This could happen to chan_sip and other modules using DNS. Example: Event: ModuleLoad ModuleLoadStatus: Done ModuleSelection: All ModuleCount: 24
- Event: QueueSummary Modules: app_queue Purpose: To report a summary of queue information. This event is generated by issuing a QueueSummary AMI action. Example: Event: QueueSummary Queue: Sales LoggedIn: 12 Available: 5 Callers: 10 HoldTime: 47 If an actionID was specified for the QueueSummary action, it will be appended as the last line of the QueueSummary event.
I was able to get it working this morning. Grabbed the 1.0.0 snapshot of the asterisk-java library and then recompiled asterisk-im with that, Caller ID popups now show up with my Asterisk 1.6 system.
Oh and heres the asterisk-im plugin compiled with asterisk-java 1.0.0 snapshot. Be warned though. While it does bring things back to functionality for asterisk 1.6, the plugin config screen on openfire looks to be blank after installing it. The old config is still there for the previous version, just no way to make changes. Maybe someone else will have different results or maybe someone more familar with the plugin source can correct. This was comiled for openfire 3.6.0. --Fred
Retrieving data ...