June 2018 – Records And Memorys

J2EE is a platform-independent, Java-centric environment from Sun for developing, building and deploying Web-based enterprise applications online. The J2EE platform consists of a set of services, APIs, and protocolsthat provide the functionality for developing multitiered, Web-based applications.

Some of the key features and services of J2EE:

At the client tier, J2EE supports pure HTML, as well as Java applets or applications. It relies on Java Server Pages and servletcode to create HTML or other formatted data for the client.
Enterprise JavaBeans (EJBs) provide another layer where the platform’s logic is stored. An EJB server provides functions such as threading, concurrency, security and memory management. These services are transparent to the author.
Java Database Connectivity (JDBC), which is the Java equivalent to ODBC, is the standard interface for Java databases.
The Java servlet API enhances consistency for developers without requiring a graphical user interface.

In simpler terms, J2EE is essentially a standard middleware architecture, proposed by Sun Microsystems for developing and deploying multitier, distributed, e-enabled, enterprise scale business applications. Applications written for J2EE standards enjoy certain inherent benefits such as portability, security, scalability, load-balancing, and reusability.

2) How to install JBoss in eclipse

~~download from this site : http://jbossas.jboss.org/downloads~~

in eclipse , goto ： help —-> eclipse market , type “jboss” , select “JBoss Tools 4.4.4.final” , and install it

after install , restart eclipse as require .

3) How to build jboss server

June 21, 2018June 21, 2018

what is asterisk max concurrent calls ?

每 X秒送 Y 个电话，每个电话通话 Z 秒
要使 con-current calls 维持在某个数比如300 ，
怎么设置 x,y,z

June 20, 2018July 16, 2018

English sentences

“they want you to be locked in to their
product cycles”

From asterisk pdf

I have confidence that Kim Jong Un will honor the contract we signed &, even more importantly, our handshake. We agreed to the denuclearization of North Korea. China, on the other hand, may be exerting negative pressure on a deal because of our posture on Chinese Trade-Hope Not!

2018-7-9 trump

exert pressure : 施加压力

posture : 态度

18-7-9

Just talked with Pfizer (辉瑞) CEO and @SecAzar on our drug pricing blueprint. Pfizer is rolling back price hikes, so American patients don’t pay more. We applaud Pfizer for this decision and hope other companies do the same. Great news for the American people!

roll back : 回滚

applaud : 欢呼

The European Union makes it impossible for our farmers and workers and companies to do business in Europe (U.S. has a $151 Billion trade deficit), and then they want us to happily defend them through NATO, and nicely pay for it. Just doesn’t work!

deficit : 赤字，逆差

NATO : 北约

A recent Emerson College ePoll said that most Americans, especially Hispanics, feel that they are better off under President Trump than they were under President Obama.

Many countries in NATO, which we are expected to defend, are not only short of their current commitment of 2% (which is low), but are also delinquent for many years in payments that have not been made. Will they reimburse the U.S.?

commitment: 承诺

reimburse : 补偿

I am on Air Force One (空军一号) flying to NATO and hear reports that the FBI lovers, Peter Strzok and Lisa Page are getting cold feet on testifying about the Rigged Witch Hunt headed by 13 Angry Democrats and people that worked for Obama for 8 years. Total disgrace!

get cold feet : 害怕做某事，临阵畏缩

rig: 作弊

head by : 由于

Witch Hunt : 狩猎女巫，引申为以莫须有的罪名进行政治迫害

On behalf of the United States, congratulations to the Thai Navy SEALs and all on the successful rescue of the 12 boys and their coach from the treacherous cave in Thailand. Such a beautiful moment – all freed, great job!

rescue : 救援

Bilateral Breakfast with NATO Secretary General in Brussels, Belgium…

Bilateral : 双边的，双侧的

2018-7-12

Presidents have been trying unsuccessfully for years to get Germany and other rich NATO Nations to pay more toward their protection from Russia. They pay only a fraction of their cost. The U.S. pays tens of Billions of Dollars too much to subsidize Europe, and loses Big on Trade!

subsidy : 补贴津贴。

2018-7-16

President Obama thought that Crooked Hillary was going to win the election, so when he was informed by the FBI about Russian Meddling, he said it couldn’t happen, was no big deal, & did NOTHING about it. When I won it became a big deal and the Rigged Witch Hunt headed by Strzok!

Crooked: 不诚实的

meddle : 干涉，管闲事

no big deal : 没什么了不起

June 14, 2018

asterisk 各种错误情况及处理

June 12, 2018June 13, 2018

How to use wireshark to capture asterisk outgoing call

先看网卡情况

确定了正在使用的网卡是 eth0

先 sudo tshark -i eth0 -w out.pcap ，再用 asterisk AMI 发一个 OriginateCall 的命令，即可截取到 sip 的 wireshark trace

如何在 wireshark 分析 trace 文件？

for more details , refer this article :

BI-7_VoIP_Analysis_Fundamentals

June 12, 2018June 13, 2018

If asterisk have a log of “asterisk -rvvv” ? — configure of logger.conf

; Logging Configuration
;
; In this file, you configure logging to files or to
; the syslog system.
;
; "logger reload" at the CLI will reload configuration
; of the logging system.

[general]
;
; Customize the display of debug message time stamps
; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS)
;
; see strftime(3) Linux manual for format specifiers.  Note that there is also
; a fractional second parameter which may be used in this field.  Use %1q
; for tenths, %2q for hundredths, etc.
;
;dateformat=%F %T       ; ISO 8601 date format
dateformat=%F %T.%3q   ; with milliseconds
;
;
; This makes Asterisk write callids to log messages
; (defaults to yes)
use_callids = yes
;
; This appends the hostname to the name of the log files.
appendhostname = no
;
; This determines whether or not we log queue events to a file
; (defaults to yes).
queue_log = yes
;
; Determines whether the queue_log always goes to a file, even
; when a realtime backend is present (defaults to no).
queue_log_to_file = no
;
; Set the queue_log filename
; (defaults to queue_log)
queue_log_name = queue_log
;
; When using realtime for the queue log, use GMT for the timestamp
; instead of localtime.  The default of this option is 'no'.
queue_log_realtime_use_gmt = no
;
; Log rotation strategy:
; none:  Do not perform any logrotation at all.  You should make
;        very sure to set up some external logrotate mechanism

;        very sure to set up some external logrotate mechanism
;        as the asterisk logs can get very large, very quickly.
; sequential:  Rename archived logs in order, such that the newest
;              has the highest sequence number [default].  When
;              exec_after_rotate is set, ${filename} will specify
;              the new archived logfile.
; rotate:  Rotate all the old files, such that the oldest has the
;          highest sequence number [this is the expected behavior
;          for Unix administrators].  When exec_after_rotate is
;          set, ${filename} will specify the original root filename.
; timestamp:  Rename the logfiles using a timestamp instead of a
;             sequence number when "logger rotate" is executed.
;             When exec_after_rotate is set, ${filename} will
;             specify the new archived logfile.
rotatestrategy = rotate
;
; Run a system command after rotating the files.  This is mainly
; useful for rotatestrategy=rotate. The example allows the last
; two archive files to remain uncompressed, but after that point,
; they are compressed on disk.
;
exec_after_rotate=gzip -9 ${filename}.2
;
;
; For each file, specify what to log.
;
; For console logging, you set options at start of
; Asterisk with -v for verbose and -d for debug
; See 'asterisk -h' for more information.
;
; Directory for log files is configures in asterisk.conf
; option astlogdir
;
; All log messages go to a queue serviced by a single thread
; which does all the IO.  This setting controls how big that
; queue can get (and therefore how much memory is allocated)
; before new messages are discarded.
; The default is 1000
;logger_queue_limit = 250
;
;
[logfiles]
;
; Format is "filename" and then "levels" of debugging to be included:
;    debug
;    notice
;    warning
;    error
;    verbose(<level>)
;    dtmf
;    fax
;    security
;
; Special filename "console" represents the root console
;
; Filenames can either be relative to the standard Asterisk log directory
; (see 'astlogdir' in asterisk.conf), or absolute paths that begin with
; '/'.
;
; Verbose takes an optional argument, in the form of an integer level.
; Verbose messages with higher levels will not be logged to the file.  If
; the verbose level is not specified, it will log verbose messages following
; the current level of the root console.
;
; Special level name "*" means all levels, even dynamic levels registered
; by modules after the logger has been initialized (this means that loading
; and unloading modules that create/remove dynamic logger levels will result
; in these levels being included on filenames that have a level name of "*",
; without any need to perform a 'logger reload' or similar operation).
; Note that there is no value in specifying both "*" and specific level names
; for a filename; the "*" level means all levels.  The only exception is if
; you need to specify a specific verbose level. e.g, "verbose(3),*".
;
; We highly recommend that you DO NOT turn on debug mode if you are simply
; running a production system.  Debug mode turns on a LOT of extra messages,
; most of which you are unlikely to understand without an understanding of
; the underlying code.  Do NOT report debug messages as code issues, unless
; you have a specific issue that you are attempting to debug.  They are
; messages for just that -- debugging -- and do not rise to the level of
; something that merit your attention as an Asterisk administrator.  Debug
; messages are also very verbose and can and do fill up logfiles quickly;
; this is another reason not to have debug mode on a production system unless
; you are in the process of debugging a specific issue.
;
;debug => debug
;security => security
console => notice,warning,error
;console => notice,warning,error,debug
messages => notice,warning,error

<span style="color: #ff0000;">full => notice,warning,error,debug,verbose,dtmf,fax</span>

;syslog keyword : This special keyword logs to syslog facility

;syslog.local0 => notice,warning,error
;

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

; Logging Configuration

;

; In this file, you configure logging to files or to

; the syslog system.

;

; "logger reload" at the CLI will reload configuration

; of the logging system.

[general]

;

; Customize the display of debug message time stamps

; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS)

;

; see strftime(3) Linux manual for format specifiers. Note that there is also

; a fractional second parameter which may be used in this field. Use %1q

; for tenths, %2q for hundredths, etc.

;

;dateformat=%F %T ; ISO 8601 date format

dateformat=%F %T.%3q ; with milliseconds

;

; This makes Asterisk write callids to log messages

; (defaults to yes)

use_callids = yes

;

; This appends the hostname to the name of the log files.

appendhostname = no

;

; This determines whether or not we log queue events to a file

; (defaults to yes).

queue_log = yes

;

; Determines whether the queue_log always goes to a file, even

; when a realtime backend is present (defaults to no).

queue_log_to_file = no

;

; Set the queue_log filename

; (defaults to queue_log)

queue_log_name = queue_log

;

; When using realtime for the queue log, use GMT for the timestamp

; instead of localtime. The default of this option is 'no'.

queue_log_realtime_use_gmt = no

;

; Log rotation strategy:

; none: Do not perform any logrotation at all. You should make

; very sure to set up some external logrotate mechanism

; as the asterisk logs can get very large, very quickly.

; sequential: Rename archived logs in order, such that the newest

; has the highest sequence number [default]. When

; exec_after_rotate is set, ${filename} will specify

; the new archived logfile.

; rotate: Rotate all the old files, such that the oldest has the

; highest sequence number [this is the expected behavior

; for Unix administrators]. When exec_after_rotate is

; set, ${filename} will specify the original root filename.

; timestamp: Rename the logfiles using a timestamp instead of a

; sequence number when "logger rotate" is executed.

; When exec_after_rotate is set, ${filename} will

; specify the new archived logfile.

rotatestrategy = rotate

;

; Run a system command after rotating the files. This is mainly

; useful for rotatestrategy=rotate. The example allows the last

; two archive files to remain uncompressed, but after that point,

; they are compressed on disk.

;

exec_after_rotate=gzip -9 ${filename}.2

;

; For each file, specify what to log.

;

; For console logging, you set options at start of

; Asterisk with -v for verbose and -d for debug

; See 'asterisk -h' for more information.

;

; Directory for log files is configures in asterisk.conf

; option astlogdir

;

; All log messages go to a queue serviced by a single thread

; which does all the IO. This setting controls how big that

; queue can get (and therefore how much memory is allocated)

; before new messages are discarded.

; The default is 1000

;logger_queue_limit = 250

;

[logfiles]

;

; Format is "filename" and then "levels" of debugging to be included:

; debug

; notice

; warning

; error

; verbose(<level>)

; dtmf

; fax

; security

;

; Special filename "console" represents the root console

;

; Filenames can either be relative to the standard Asterisk log directory

; (see 'astlogdir' in asterisk.conf), or absolute paths that begin with

; '/'.

;

; Verbose takes an optional argument, in the form of an integer level.

; Verbose messages with higher levels will not be logged to the file. If

; the verbose level is not specified, it will log verbose messages following

; the current level of the root console.

;

; Special level name "*" means all levels, even dynamic levels registered

; by modules after the logger has been initialized (this means that loading

; and unloading modules that create/remove dynamic logger levels will result

; in these levels being included on filenames that have a level name of "*",

; without any need to perform a 'logger reload' or similar operation).

; Note that there is no value in specifying both "*" and specific level names

; for a filename; the "*" level means all levels. The only exception is if

; you need to specify a specific verbose level. e.g, "verbose(3),*".

;

; We highly recommend that you DO NOT turn on debug mode if you are simply

; running a production system. Debug mode turns on a LOT of extra messages,

; most of which you are unlikely to understand without an understanding of

; the underlying code. Do NOT report debug messages as code issues, unless

; you have a specific issue that you are attempting to debug. They are

; messages for just that -- debugging -- and do not rise to the level of

; something that merit your attention as an Asterisk administrator. Debug

; messages are also very verbose and can and do fill up logfiles quickly;

; this is another reason not to have debug mode on a production system unless

; you are in the process of debugging a specific issue.

;

;debug => debug

;security => security

console => notice,warning,error

;console => notice,warning,error,debug

messages => notice,warning,error

<span style="color: #ff0000;">full => notice,warning,error,debug,verbose,dtmf,fax</span>

;syslog keyword : This special keyword logs to syslog facility

;syslog.local0 => notice,warning,error

;

Above is a /etc/asterisk/logger.conf example ,

Red font part will record every in cli to /var/log/asterisk/full

June 11, 2018June 12, 2018

asterisk cdr and max concurrent call

location is : /var/log/asterisk/cdr-csv/Master.csv

能有多少 concurrent calls :

https://www.voip-info.org/asterisk-dimensioning/

Master.csv 的记录和实际一致吗？

concurrent calls = 280 , 没有丢cdr的情况

怎么从 Master.csv 产生这样的报表：

hour 1400 – generated x calls, with x duration
hour 1500 – Generated X calls with X duration

answer: group excel file by hourly : reference from this article :

https://www.excelcampus.com/charts/group-times-in-excel/

google key word : excel group by time period

cdr 字段 in Master.csv

Fields

accountcode: What account number to use: account, (string, 20 characters)
src: Caller*ID number (string, 80 characters)
dst: Destination extension (string, 80 characters)
dcontext: Destination context (string, 80 characters)
clid: Caller*ID with text (80 characters)
channel: Channel used (80 characters)
dstchannel: Destination channel if appropriate (80 characters)
lastapp: Last application if appropriate (80 characters)
lastdata: Last application data (arguments) (80 characters)
start: Start of call (date/time)
answer: Answer of call (date/time)
end: End of call (date/time)
duration: Total time in system, in seconds (integer)
billsec: Total time call is up, in seconds (integer)
disposition: What happened to the call: ANSWERED, NO ANSWER, BUSY, FAILED
amaflags: What flags to use: see amaflags::DOCUMENTATION, BILL, IGNORE etc, specified on a per channel basis like accountcode.

June 6, 2018

in cctb1 , add pack callflow to existing ree-idd callflow

new add files : DB_Pack.hpp , DB_Pack.cpp ,CVHPack.hpp, CVHPack.cpp

modify files : CSimpleCall.hpp (用本地文件覆盖)

CSimpleCall.cpp (需特别注意在 cctb1 ，

mCommParams.mun16TbxGwPort =12360; 本地是 mCommParams.mun16TbxGwPort = 12358; )

CSimpleCall其他代码用本地覆盖

DB.hpp + DB.cpp 用本地代码覆盖

CVHCallFlow.cpp 的这句注释掉

	//if((nap == "VMS198") || (nap == "VMS199")) 
	//{
	//	ptrLegAttr->GetProfile().SetByProfileName( "profile729" );
	//}

//if((nap == "VMS198") || (nap == "VMS199"))

//{

// ptrLegAttr->GetProfile().SetByProfileName( "profile729" );

//}

outgoing call ‘s codec use g711

保持不变： CVHCCloud.hpp , CVHCCloud.cpp

TBConfig.txt 的修改