[RISOLTO] Caller ID Ingresso

anonymous

Well-Known Member
Registrato
14 Gennaio 2008
Messaggi
19.170
Buongiorno a tutti,
posseggo un patton 4114 su 4 linee analogiche (normali) e un centrlino 3cx.
Tutto è ok ma avrei la necessità di vedere il numero del chiamante. Questo il mio operatore (fastweb) mi conferma che avviene, ma come faccio a inoltrare il numero chiamante patton-->3cx e quindi agli apparecchi telefonici?

questa è configrazione del mio patton ma non capisco dove sia la falla... avete suggeriementi o consigli?

#

#
# #
# SN4114/JO/EUI #
# R4.2 2007-12-03 H323 SIP FXS FXO #
# 1970-01-03T07:49:19 #
# SN/00A0BA029A38 #
# Generated configuration file #
# #
#

#

cli version 3.20
webserver port 80 language en
system hostname 192.168.169.253

system

ic voice 0
low-bitrate-codec g729

profile ppp default

profile call-progress-tone IT_Dialtone
play 1 200 425 -12
pause 2 200
play 3 600 425 -12
pause 4 1000

profile call-progress-tone IT_Alertingtone
play 1 1000 425 -12
pause 2 4000

profile call-progress-tone IT_Busytone
play 1 500 425 -12
pause 2 500

profile tone-set default

profile tone-set IT
map call-progress-tone dial-tone IT_Dialtone
map call-progress-tone ringback-tone IT_Alertingtone
map call-progress-tone busy-tone IT_Busytone
map call-progress-tone release-tone IT_Busytone
map call-progress-tone congestion-tone IT_Busytone

profile voip default
codec 1 g711alaw64k rx-length 20 tx-length 20
codec 2 g711ulaw64k rx-length 20 tx-length 20

profile pstn default

profile sip default

profile aaa default
method 1 local
method 2 none

context ip router

interface eth0
ipaddress 192.168.169.253 255.255.255.0

context ip router
route 0.0.0.0 0.0.0.0 192.168.169.254 0

context cs switch
no digit-collection timeout

routing-table called-e164 OUT
route default dest-interface sipif0 CALLED

routing-table called-e164 OUT1
route default dest-interface sipif1 CALLED1

mapping-table called-e164 to called-e164 CALLED
map default to MIONUMEROTELEFONO

mapping-table called-e164 to called-e164 CALLED1
map default to MIONUMEROTELEFONO

interface sip sipif0
bind gateway sipgw0
service default
route call dest-service fxohuntgroup
early-disconnect
remote-party-id called-party
address-translation outgoing-call from-header user-part fix 10000 host-part local-ip
address-translation incoming-call called-e164 to-header

interface sip sipif1
bind gateway sipgw1
service default
route call dest-service fxohuntgroup
early-disconnect
address-translation outgoing-call from-header user-part fix 10001 host-part local-ip

interface sip sipif2
bind gateway sipgw2
service default
route call dest-service fxohuntgroup
early-disconnect
address-translation outgoing-call from-header user-part fix 10002 host-part local-ip

interface sip sipif3
bind gateway sipgw3
service default
route call dest-service fxohuntgroup
early-disconnect
address-translation outgoing-call from-header user-part fix 10003 host-part local-ip

interface fxo fxoif0
route call dest-table OUT
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
use profile tone-set IT

interface fxo fxoif1
route call dest-table OUT1
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
use profile tone-set IT

interface fxo fxoif2
route call dest-interface sipif2
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
use profile tone-set IT

interface fxo fxoif3
route call dest-interface sipif3
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
use profile tone-set IT

service hunt-group fxohuntgroup
drop-cause normal-unspecified
drop-cause no-circuit-channel-available
drop-cause network-out-of-order
drop-cause temporary-failure
drop-cause switching-equipment-congestion
drop-cause access-info-discarded
drop-cause circuit-channel-not-available
drop-cause resources-unavailable
drop-cause user-busy
route call 1 dest-interface fxoif0
route call 2 dest-interface fxoif1
route call 3 dest-interface fxoif2
route call 4 dest-interface fxoif3

context cs switch
no shutdown

gateway sip sipgw0
bind interface eth0 router

service default
domain 192.168.169.22
defaultserver manual 192.168.169.22 loose-router
registration manual 192.168.169.22
user 10000 authenticate password LbFCDNv4/Fk= encrypted default register

gateway sip sipgw0
no shutdown

gateway sip sipgw1
call-signaling-port 5062
bind interface eth0 router

service default
domain 192.168.169.22
defaultserver manual 192.168.169.22 loose-router
registration manual 192.168.169.22
user 10001 authenticate password dZ8edXkjFnM= encrypted default register

gateway sip sipgw1
no shutdown

gateway sip sipgw2
call-signaling-port 5064
bind interface eth0 router

service default
domain 192.168.169.22
defaultserver manual 192.168.169.22 loose-router
registration manual 192.168.169.22
user 10002 authenticate password iAaKwKfxX4Q= encrypted default register

gateway sip sipgw2
no shutdown

gateway sip sipgw3
call-signaling-port 5066
bind interface eth0 router

service default
domain 192.168.169.22
defaultserver manual 192.168.169.22 loose-router
registration manual 192.168.169.22
user 10003 authenticate password ySyWxUvSc/c= encrypted default register

gateway sip sipgw3
no shutdown

port ethernet 0 0
medium auto
encapsulation ip
bind interface eth0 router
no shutdown

port fxo 0 0
use profile fxo us
encapsulation cc-fxo
bind interface fxoif0 switch
no shutdown

port fxo 0 1
use profile fxo us
encapsulation cc-fxo
bind interface fxoif1 switch
no shutdown

port fxo 0 2
use profile fxo us
encapsulation cc-fxo
bind interface fxoif2 switch
no shutdown

port fxo 0 3
use profile fxo us
encapsulation cc-fxo
bind interface fxoif3 switch
no shutdown
 
Se ritieni che la configurazione sia corretta (e credo lo sia visto che ricevi le telefonata), ti rispondo per la medesima situazione in ambiente Telecom: su 3 impianti diversi con il Patton 4114, appena attaccavo le uscite, improvvisamente il caller ID mi diventava anonimo. Ho attaccato quindi alla borchia un normale telefono, composto il codice per l'attivazione del servizio "chi è" e tutto si è risolto.

Potrebbe essere uno spunto di risoluzione anche del tuo problema?? Ovviamente accertati tramite il tuo operatore di telefonia su qual è il codice per lo sblocco
 
Problema risolto sul patton, non rigirava correttamente il caller ID, è bastato rigenerare la configurazione dal server 3cx e tutto si è risolto.
 
puoi mettere un bel [RISOLTO] sul titolo del primo post? aiuta!! :mrgreen:
 

Inizia con 3CX – Admin

Forum statistics

Discussioni
44.658
Messaggi
233.414
Membri
78.444
Ultimo Iscritto
PCCAdmin