Summary: | ASTERISK-05229: The API Manager continue connection after a "logoff" Action | ||
Reporter: | Fernando Romo (el_pop) | Labels: | |
Date Opened: | 2005-10-03 17:59:06 | Date Closed: | 2005-10-03 18:40:36 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/ManagerInterface |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | After "Action: Logoff" request, the API Manager still open and accept commands. The TCP port don't close properly. ****** ADDITIONAL INFORMATION ****** Using a Telnet with port 5038 to observ and geberate events, when send a "Action: Logoff" the port still open and the telnet session still alive and acepting commands. ------------------------------ Event: Link Privilege: call,all Channel1: SIP/9002-c491 Channel2: Zap/1-1 Uniqueid1: 1128378031.61 Uniqueid2: 1128378031.62 CallerID1: 9002 CallerID2: 50921328 Event: PeerStatus Privilege: system,all Peer: IAX2/kbrown PeerStatus: Registered Action: Logoff Response: Goodbye Message: Thanks for all the fish. Event: Newchannel Privilege: call,all Channel: SIP/9001-3a7d State: Ring CallerID: 9001 CallerIDName: Neocenter Uniqueid: 1128378070.63 Event: Newexten Privilege: call,all Channel: SIP/9001-3a7d Context: default Extension: 9005 Priority: 1 Application: Macro AppData: adminexten|9005 Uniqueid: 1128378070.63 Action: Originate Channel: SIP/9006 Context: default Exten: 7091 Priority: 1 Async: true Response: Success Message: Originate successfully queued ---------------- | ||
Comments: | By: Clod Patry (junky) 2005-10-03 18:39:55 We know about it, see open bugs before reporting the same issue. Thanks. |