Datatex Dynamics

by **stephen** » Mon Apr 02, 2012 9:54 am

Hi

We're in the process of replacing our old Asterisk 1.4 server to new hardware on Asterisk 1.8.

When I look in asterisk I can see TNG connects fine on the manager interface, but when I make calls, its not logging any calls. I managed to find a log in TNG that gives me this message:

Code: Select all: 2012-04-01 12:30:35:027 [1.0.7.0] - AMI Exception:Event: Dial[10]Privilege: call,all[10]SubEvent: End[10]Channel: SIP/153-00000000[10]UniqueID: 1333276396.0[10]DialStatus: ANSWER[10] 2012-04-01 12:30:35:026 [1.0.7.0] - AMI Exception:ProcessAMIEvent: Access violation at address 0813F4D5, accessing address 000000A9 2012-04-01 12:30:00:884 [1.0.7.0] - AMI connected to port 5038 on 10.0.8.201 2012-04-01 12:30:00:759 [1.0.7.0] - AMI Exception:ConnectToAsterisk: Socket Error # 111[13][10]Connection refused. 2012-04-01 12:30:00:634 [1.0.7.0] - AMI Exception:Connection Closed Gracefully. 2012-04-01 12:30:00:634 [1.0.7.0] - AMI Disconnected:0 - 2012-04-01 12:27:04:551 [1.0.7.0] - AMI Exception:Event: Dial[10]Privilege: call,all[10]SubEvent: End[10]Channel: SIP/153-00000000[10]UniqueID: 1333276186.0[10]DialStatus: ANSWER[10] 2012-04-01 12:27:04:551 [1.0.7.0] - AMI Exception:ProcessAMIEvent: Access violation at address 0813F4D5, accessing address 000000A9 2012-04-01 12:23:44:337 [1.0.7.0] - AMI connected to port 5038 on 10.0.8.201 2012-04-01 12:23:44:212 [1.0.7.0] - AMI Exception:ConnectToAsterisk: Socket Error # 111[13][10]Connection refused. 2012-04-01 12:23:44:087 [1.0.7.0] - AMI Exception:Connection Closed Gracefully.

So it looks like TNG is in fact picking up the calls being made, but I'm not sure why its not logging it. Perhaps because of access violation part?

by **Belinda Frick** » Mon Apr 02, 2012 2:08 pm

Please see forum post

AMI Exception:ProcessAMIEvent: Access violation Asterisk 1.8

by **stephen** » Fri Apr 06, 2012 11:16 am

Hi. I'm still getting these messages:

Code: Select all: [10]DialStatus: ANSWER[10] 2012-04-06 11:06:18:547 [1.0.7.7] - AMI Exception:ProcessAMIEvent: ProcessDial 3: Access violation at address 08142D16, accessing address 000000A9 2012-04-06 11:06:18:547 [1.0.7.7] - AMI Exception:Event: Dial[10]Privilege: call,all[10]SubEvent: End[10]Channel: SIP/5747-00000004[10]UniqueID: 1333703343.4[10]DialStatus: ANSWER[10] 2012-04-06 11:08:23:759 [1.0.7.7] - AMI Exception:ProcessAMIEvent: ProcessDial 3: Access violation at address 08142D16, accessing address 000000A9 2012-04-06 11:08:23:759 [1.0.7.7] - AMI Exception:Event: Dial[10]Privilege: call,all[10]SubEvent: End[10]Channel: SIP/192.169.5.5-0000000a[10]UniqueID: 1333703456.10[10]DialStatus: ANSWER[10] 2012-04-06 11:09:07:739 [1.0.7.7] - AMI Exception:ProcessAMIEvent: ProcessDial 3: Access violation at address 08142D16, accessing address 000000A9 2012-04-06 11:09:07:739 [1.0.7.7] - AMI Exception:Event: Dial[10]Privilege: call,all[10]SubEvent: End[10]Channel: SIP/5747-00000008[10]UniqueID: 1333703396.8[10]DialStatus: ANSWER[10] 2012-04-06 11:09:16:325 [1.0.7.7] - AMI Exception:ProcessAMIEvent: ProcessDial 3: Access violation at address 08142D16, accessing address 000000A9 2012-04-06 11:09:16:325 [1.0.7.7] - AMI Exception:Event: Dial[10]Privilege: call,all[10]SubEvent: End[10]Channel: SIP/192.169.5.5-00000006[10]UniqueID: 1333703382.6[10]DialStatus: ANSWER[10]

I have followed each thread from AMI Exception:ProcessAMIEvent: Access violation Asterisk 1.8
and also made sure I have my configration set as described in: viewtopic.php?f=24&t=2637#p2659

The ami.txt log does not show any errors when I make calls (at least, I don't see any), only the tng log. I would really like to get this sorted.

by **stephen** » Tue Apr 10, 2012 9:22 am

This is what I see when I don't have TNG running as a daemon and making a call:

Code: Select all: TimeStamp: 09:21:59.912 Event: Newchannel Privilege: call,all Channel: SIP/5776-00000006 ChannelState: 0 ChannelStateDesc: Down CallerIDNum: 5776 CallerIDName: 5776 AccountCode: Exten: 0792393159 Context: default Uniqueid: 1334042526.6 TimeStamp: 09:21:59.917 Event: Newstate Privilege: call,all Channel: SIP/5776-00000006 ChannelState: 4 ChannelStateDesc: Ring CallerIDNum: 5776 CallerIDName: 5776 ConnectedLineNum: ConnectedLineName: Uniqueid: 1334042526.6 TimeStamp: 09:21:59.921 Event: Newchannel Privilege: call,all Channel: SIP/trunk_mweb-00000007 ChannelState: 0 ChannelStateDesc: Down CallerIDNum: CallerIDName: AccountCode: Exten: Context: default Uniqueid: 1334042526.7 TimeStamp: 09:21:59.924 Event: NewCallerid Privilege: call,all Channel: SIP/trunk_mweb-00000007 CallerIDNum: 0792393159 CallerIDName: Uniqueid: 1334042526.7 CID-CallingPres: 0 (Presentation Allowed, Not Screened) TimeStamp: 09:21:59.926 Event: Dial Privilege: call,all SubEvent: Begin Channel: SIP/5776-00000006 Destination: SIP/trunk_mweb-00000007 CallerIDNum: 5776 CallerIDName: 5776 ConnectedLineNum: <unknown> ConnectedLineName: <unknown> UniqueID: 1334042526.6 DestUniqueID: 1334042526.7 Dialstring: trunk_mweb/0792393159 TimeStamp: 09:22:04.914 Event: Newstate Privilege: call,all Channel: SIP/trunk_mweb-00000007 ChannelState: 5 ChannelStateDesc: Ringing CallerIDNum: 0792393159 CallerIDName: ConnectedLineNum: 5776 ConnectedLineName: 5776 Uniqueid: 1334042526.7 TimeStamp: 09:22:08.072 Event: Registry Privilege: system,all ChannelType: SIP Domain: sip.mweb.net Status: Registered TimeStamp: 09:22:08.396 Event: Newstate Privilege: call,all Channel: SIP/trunk_mweb-00000007 ChannelState: 6 ChannelStateDesc: Up CallerIDNum: 0792393159 CallerIDName: ConnectedLineNum: 5776 ConnectedLineName: 5776 Uniqueid: 1334042526.7 TimeStamp: 09:22:08.403 Event: Newstate Privilege: call,all Channel: SIP/5776-00000006 ChannelState: 6 ChannelStateDesc: Up CallerIDNum: 5776 CallerIDName: 5776 ConnectedLineNum: ConnectedLineName: Uniqueid: 1334042526.6 TimeStamp: 09:22:08.407 Event: NewAccountCode Privilege: call,all Channel: SIP/trunk_mweb-00000007 Uniqueid: 1334042526.7 AccountCode: OldAccountCode: TimeStamp: 09:22:08.409 Event: Bridge Privilege: call,all Bridgestate: Link Bridgetype: core Channel1: SIP/5776-00000006 Channel2: SIP/trunk_mweb-00000007 Uniqueid1: 1334042526.6 Uniqueid2: 1334042526.7 CallerID1: 5776 CallerID2: 0792393159 TimeStamp: 09:22:11.249 Event: Unlink Privilege: call,all Channel1: SIP/5776-00000006 Channel2: SIP/trunk_mweb-00000007 Uniqueid1: 1334042526.6 Uniqueid2: 1334042526.7 CallerID1: 5776 CallerID2: 0792393159 TimeStamp: 09:22:11.254 Event: Hangup Privilege: call,all Channel: SIP/trunk_mweb-00000007 Uniqueid: 1334042526.7 CallerIDNum: 0792393159 CallerIDName: <unknown> ConnectedLineNum: 5776 ConnectedLineName: 5776 Cause: 16 Cause-txt: Normal Clearing TimeStamp: 09:22:11.259 Event: Dial Privilege: call,all SubEvent: End Channel: SIP/5776-00000006 UniqueID: 1334042526.6 DialStatus: ANSWER TimeStamp: 09:22:11.263 Event: Hangup Privilege: call,all Channel: SIP/5776-00000006 Uniqueid: 1334042526.6 CallerIDNum: 5776 CallerIDName: 5776 ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Cause: 16 Cause-txt: Normal Clearing TimeStamp: 09:22:23.638 Event: PeerStatus Privilege: system,all ChannelType: SIP Peer: SIP/5776 PeerStatus: Registered Address: 10.0.8.21:5060 TimeStamp: 09:22:24.249 Event: Registry Privilege: system,all ChannelType: SIP Domain: sip.mweb.net Status: Registered

It does not look like errors or permission problems.

by **stephen** » Tue Apr 10, 2012 2:29 pm

My Asterisk 1.8 and TNG are on seperate servers.
I have upgraded to 1.0.7.7.
I have followed everything explained in Asterisk output configuration required

My Asterisk configs as follow:
manager.conf

Code: Select all: [loftsasterisk] secret=xxxxxx deny=0.0.0.0/0.0.0.0 permit=127.0.0.1/255.255.255.255 permit=10.0.8.203/255.255.255.255 permit=10.0.15.249/255.255.255.255 permit=10.0.8.210/255.255.255.255 read=system,call,log,verbose,command,agent,user write=system,call,log,verbose,command,agent,user writetimeout=10000

cdr_custom.conf

Code: Select all: [mappings] Master.csv => "${CDR(clid)}","${CDR(src)}","${CDR(dst)}","${CDR(dcontext)}","${CDR(channel)}","${CDR(dstchannel)}","${CDR(lastapp)}","${CDR(lastdata)}","${CDR(start)}","${CDR(answer)}","${CDR(end)}","${CDR(duration)}","${CDR(billsec)}","${CDR(disposition)}","${CDR(amaflags)}","${CDR(accountcode)}","${CDR(uniqueid)}","${CDR(userfield)}"

Asterisk log:

Code: Select all: tail /var/log/asterisk/cdr-custom/Master.csv -n1 ""5776" <5776>","5776","0792393159","default","SIP/5776-00000006","SIP/trunk_mweb-00000007","Dial","SIP/trunk_mweb/0792393159","2012-04-10 14:01:10","2012-04-10 14:01:17","2012-04-10 14:01:20","10","3","ANSWERED","DOCUMENTATION","","1334059270.6",""

What other info can I supply to get some real help ?

by **stephen** » Thu Apr 12, 2012 7:41 am

Hi

I installed TNG on the Asterisk server as Odette suggested, as per our conversation the other day and it seems to log now. We are fine with running TNG on the same server and happy that its working.

Only thing wrong now, when I sent the registration file, I got a response back saying that the company email already exists. I'm sure that is an automated response. Should I sent the registration file again? If yes, to which address?

by **Odette Danster** » Thu Apr 12, 2012 9:10 am

Dear Stephen

Please log into TNG, under General Settings - Company Details, change the current company e-mail address to another valid e-mail account and save the settings.

Once company e-mail address has been changed, please navigate to the License page and re-create the registration file and send the new registration file to register@datatex.co.za

Yours Sincerely
Odette

Datatex Dynamics

TNG not logging calls

TNG not logging calls

Re: TNG not logging calls

Re: TNG not logging calls

Re: TNG not logging calls

Re: TNG not logging calls

Re: TNG not logging calls

Re: TNG not logging calls

Who is online