hi i link mxone sp7 with a elastix 1

[5755g]

hi i link mxone sp7 with a elastix server tlu76---d115 open vox if call from out incoming caller id working but internal call to mx-one from elastix or elastix to mxone caller id not working plesae help thanks

ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
1 SL60 H'00000300 H'10000000 H'04010020 NO



ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
1 0110000000000010 4 3100000001 0 30 128 03151515 211100000030 111111

<ROEDP:rou=1,tru=all;
ROUTE EQUIPMENT DATA
ROU TRU EQU IP ADDRESS SQU INDDAT CNTRL
1 001-1 001-2-20-01 H'000000000000
1 001-2 001-2-20-02 H'000000000000
1 001-3 001-2-20-03 H'000000000000
1 001-4 001-2-20-04 H'000000000000
1 001-5 001-2-20-05 H'000000000000
1 001-6 001-2-20-06 H'000000000000
1 001-7 001-2-20-07 H'000000000000
1 001-8 001-2-20-08 H'000000000000
1 001-9 001-2-20-09 H'000000000000
1 001-10 001-2-20-10 H'000000000000
1 001-11 001-2-20-11 H'000000000000
1 001-12 001-2-20-12 H'000000000000
1 001-13 001-2-20-13 H'000000000000
1 001-14 001-2-20-14 H'000000000000
1 001-15 001-2-20-15 H'000000000000
1 001-16 001-2-20-17 H'000000000000
1 001-17 001-2-20-18 H'000000000000
1 001-18 001-2-20-19 H'000000000000
1 001-19 001-2-20-20 H'000000000000
1 001-20 001-2-20-21 H'000000000000
1 001-21 001-2-20-22 H'000000000000
1 001-22 001-2-20-23 H'000000000000
1 001-23 001-2-20-24 H'000000000000
1 001-24 001-2-20-25 H'000000000000
1 001-25 001-2-20-26 H'000000000000
1 001-26 001-2-20-27 H'000000000000
1 001-27 001-2-20-28 H'000000000000
1 001-28 001-2-20-29 H'000000000000
1 001-29 001-2-20-30 H'000000000000
1 001-30 001-2-20-31 H'000000000000

END

 

[SBIDIGUDA]

Can you post the following files? Thanks.
/etc/dahdi/system.conf
/etc/asterisk/chan_dahdi.conf
/etc/asterisk/dahdi-channels.conf
/etc/asterisk/extensions.conf

 

[5755g]

hi sure

system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Tue Sep 25 18:42:09 2012
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: D115/D130/0/1 "D115/D130 (E1|T1) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4
span=1,1,0,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
#echocanceller=oslec,1-15,17-31

# Global data

loadzone = us
defaultzone = us


chan_dahdi
[trunkgroups]

[channels]
context=from-pstn
signalling=pri_cpe
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
faxdetect=incoming
;echotraining=800
rxgain=0.0
txgain=0.0
callgroup=1
pickupgroup=1
;quality=yes
;group=0,11
;context=from-pstn
;switchtype=euroisdn
;signalling=pri_cpe
;channel=>1-15,17-31
;group=
;context=default
overlapdial=yes


;Uncomment these lines if you have problems with the disconection of your analog lines
;busydetect=yes
;busycount=3


immediate=no

#include dahdi-channels.conf
#include chan_dahdi_additional.conf
#include dahdi-channels.conf
#include dahdi-channels.conf

dahdi-chanels
; Autogenerated by /usr/sbin/dahdi_genconf on Tue Sep 25 18:42:09 2012
; If you edit this file and execute /usr/sbin/dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: D115/D130/0/1 "D115/D130 (E1|T1) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4
group=0,11
context=from-pstn
switchtype = euroisdn
signalling = pri_net
channel => 1-15,17-31
context = default
group =

extention config

;
; Static and realtime external configuration
; engine configuration
;
; See

https://wiki.asterisk.org/wiki/display/AST/Realtime+Database+Configuration

; for basic table formatting information.
;
[settings]
;
; Static configuration files:
;
; file.conf => driver,database[,table[,priority]]
;
; maps a particular configuration file to the given
; database driver, database and table (or uses the
; name of the file as the table if not specified)
;
;uncomment to load queues.conf via the odbc engine.
;
;queues.conf => odbc,asterisk,ast_config
;extensions.conf => sqlite,asterisk,ast_config
;
; The following files CANNOT be loaded from Realtime storage:
; asterisk.conf
; extconfig.conf (this file)
; logger.conf
;
; Additionally, the following files cannot be loaded from
; Realtime storage unless the storage driver is loaded
; early using 'preload' statements in modules.conf:
; manager.conf
; cdr.conf
; rtp.conf
;
;
; Realtime configuration engine
;
; maps a particular family of realtime
; configuration to a given database driver,
; database and table (or uses the name of
; the family if the table is not specified
;
;example => odbc,asterisk,alttable,1
;example => mysql,asterisk,alttable,2
;example2 => ldap,"dc=oxymium,dc=net",example2
;
; Additionally, priorities are now supported for use as failover methods
; for retrieving realtime data. If one connection fails to retrieve any
; information, the next sequential priority will be tried next. This
; especially works well with ODBC connections, since res_odbc now caches
; when connection failures occur and prevents immediately retrying those
; connections until after a specified timeout. Note: priorities must
; start at 1 and be sequential (i.e. if you have only priorities 1, 2,
; and 4, then 4 will be ignored, because there is no 3).
;
; "odbc" is shown in the examples below, but is not the only valid realtime
; engine. There is:
; odbc ... res_config_odbc
; sqlite ... res_config_sqlite
; pgsql ... res_config_pgsql
; curl ... res_config_curl
; ldap ... res_config_ldap
;
;iaxusers => odbc,asterisk
;iaxpeers => odbc,asterisk
;sipusers => odbc,asterisk
;sippeers => odbc,asterisk
;sipregs => odbc,asterisk
;voicemail => odbc,asterisk
;extensions => odbc,asterisk
;meetme => mysql,general
;queues => odbc,asterisk
;queue_members => odbc,asterisk
;musiconhold => mysql,general
;queue_log => mysql,general
;
;
; While most dynamic realtime engines are automatically used when defined in
; this file, 'extensions', distinctively, is not. To activate dynamic realtime
; extensions, you must turn them on in each respective context within
; extensions.conf with a switch statement. The syntax is:
; switch => Realtime/[[db_context@]tablename]/<opts>
; The only option available currently is the 'p' option, which disallows
; extension pattern queries to the database. If you have no patterns defined
; in a particular context, this will save quite a bit of CPU time. However,
; note that using dynamic realtime extensions is not recommended anymore as a
; best practice; instead, you should consider writing a static dialplan with
; proper data abstraction via a tool like func_odbc.