Patton Caller ID Showing anonymous on incoming calls

[Blueskyremote]

I have a Patton 4112 gateway connected to 3cx over a vpn, incoming calls only show up as anonymous and outbound call show up as a number for a different gateway on the pbx. How can I fix this?

SN4112/JO/EUI #
# R6.9 2017-03-13 H323 SIP FXS FXO #
# 2022-07-12T19:46:07 #
# SN/00A0BA10A5E5 #
# Generated configuration file #
# #
#----------------------------------------------------------------#

cli version 3.20
clock local default-offset +00:00
webserver port 80 language en

system

ic voice 0
low-bitrate-codec g729

profile ppp default

profile call-progress-tone defaultDialtone
play 1 1000 350 -13 440 -13

profile call-progress-tone defaultAlertingtone
play 1 1000 440 -19 480 -19
pause 2 3000

profile call-progress-tone defaultBusytone
play 1 500 480 -24 620 -24
pause 2 500

profile call-progress-tone defaultReleasetone
play 1 250 480 -24 620 -24
pause 2 250

profile call-progress-tone defaultCongestiontone
play 1 250 480 -24 620 -24
pause 2 250

profile tone-set default

profile voip default
codec 1 g711ulaw64k rx-length 20 tx-length 20 silence-suppression
codec 2 g711alaw64k rx-length 20 tx-length 20 silence-suppression
codec 3 g729 rx-length 20 tx-length 20 silence-suppression
fax transmission 1 relay t38-udp

profile pstn default
echo-canceler-hybrid-loss 0
echo-canceler-nlp silence

profile sip default
no autonomous-transitioning

profile aaa default
method 1 local
method 2 none

context ip router

interface IF_IP_WAN
ipaddress dhcp
tcp adjust-mss rx mtu
tcp adjust-mss tx mtu

interface IF_IP_LAN
ipaddress 192.168.12.153 255.255.255.0
tcp adjust-mss rx mtu
tcp adjust-mss tx mtu

context ip router
route 0.0.0.0 0.0.0.0 192.168.12.254 0

context cs switch

routing-table called-e164 RT_SIP_TO_FXO
route .% dest-service HG_TO_FXO

routing-table called-e164 RT_FXO_00_TO_SIP
route default dest-interface IF_SIP MT_CALL_ID_00

routing-table called-e164 RT_FXO_01_TO_SIP
route default dest-interface IF_SIP MT_CALL_ID_01

routing-table called-e164 RT_FXO_02_TO_SIP
route default dest-interface IF_SIP MT_CALL_ID_02

routing-table called-e164 RT_FXO_03_TO_SIP
route default dest-interface IF_SIP MT_CALL_ID_03

mapping-table called-e164 to called-e164 MT_CALL_ID_00
map .% to 000000

mapping-table called-e164 to called-e164 MT_CALL_ID_01
map .% to 000001

mapping-table called-e164 to called-e164 MT_CALL_ID_02
map .% to 000002

mapping-table called-e164 to called-e164 MT_CALL_ID_03
map .% to 000003

interface sip IF_SIP
bind context sip-gateway GW_SIP
route call dest-table RT_SIP_TO_FXO
remote 10.0.1.41 5060
early-disconnect
address-translation outgoing-call request-uri user-part fix 10001 host-part to-header target-param none
trust remote

interface fxo IF_FXO_0
route call dest-table RT_FXO_00_TO_SIP
loop-break-duration min 300 max 1200
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
mute-dialing
caller-id format bell

interface fxo IF_FXO_1
route call dest-table RT_FXO_01_TO_SIP
loop-break-duration min 300 max 1200
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
mute-dialing
caller-id format bell

interface fxo IF_FXO_2
route call dest-table RT_FXO_02_TO_SIP
loop-break-duration min 300 max 1200
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
mute-dialing
caller-id format bell

interface fxo IF_FXO_3
route call dest-table RT_FXO_03_TO_SIP
loop-break-duration min 300 max 1200
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
mute-dialing
caller-id format bell

service hunt-group HG_TO_FXO
drop-cause destination-out-of-order
drop-cause user-busy
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
route call 1 dest-interface IF_FXO_0
route call 2 dest-interface IF_FXO_1

context cs switch
no shutdown

authentication-service AS_ALL_LINES
realm 1 3CXPhoneSystem
username 10001 password OZHKEfwXwbp6f+WLMGQywA== encrypted

location-service LS_10001
domain 1 10.0.1.41

identity-group default

authentication outbound
authenticate 1 authentication-service AS_ALL_LINES username 10001

identity 10001

authentication outbound
authenticate 1 authentication-service AS_ALL_LINES

registration outbound
registrar 10.0.1.41 5060
lifetime 300
register auto

context sip-gateway GW_SIP

interface LAN
bind interface IF_IP_LAN context router port 5060

context sip-gateway GW_SIP
bind location-service LS_10001
no shutdown

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

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

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

 

[leejor]

The inbound issue may be because caller Id is not being sent by the provider (use a caller ID box, on one of the lines), or, because the gateway is not waiting long enough to collect he caller ID information before sending the call to 3CX. This will depend on the caller ID type being used, primarily in the case of Bellcore type CID.

Outbound caller ID, on a PSTN gateway, will be the number assigned to the line being used, by your provider. You cannot manipulate caller ID on a PSTN line. If the number being sent, is from another gateway, then I'd assume the call is using that gateway, or the same outbound caller ID number has been assigned, by your provider, to the lines on this gateway (or you've got your lines crossed somewhere).

Maybe worth checking the firmware version...

https://www.3cx.com/community/threads/caller-id-number-not-shown.2642/

 

[Blueskyremote]

The inbound issue may be because caller Id is not being sent by the provider (use a caller ID box, on one of the lines), or, because the gateway is not waiting long enough to collect he caller ID information before sending the call to 3CX. This will depend on the caller ID type being used, primarily in the case of Bellcore type CID.

Outbound caller ID, on a PSTN gateway, will be the number assigned to the line being used, by your provider. You cannot manipulate caller ID on a PSTN line. If the number being sent, is from another gateway, then I'd assume the call is using that gateway, or the same outbound caller ID number has been assigned, by your provider, to the lines on this gateway (or you've got your lines crossed somewhere).

Maybe worth checking the firmware version...

https://www.3cx.com/community/threads/caller-id-number-not-shown.2642/

When I hook a butt set up and call my cell phone it shows the correct number

 

[leejor]

When I hook a butt set up and call my cell phone it shows the correct number

...from the line you are calling out on, which means, 3CX is not using that particular line. As I said, you cannot change the outgoing caller ID on a PSTN line. that is fixed by your provider and will never change. If the outgoing caller ID is different, then the call is using a line with that caller ID assigned.

 

[Blueskyremote]

...from the line you are calling out on, which means, 3CX is not using that particular line. As I said, you cannot change the outgoing caller ID on a PSTN line. that is fixed by your provider and will never change. If the outgoing caller ID is different, then the call is using a line with that caller ID assigned.

I have 2 pattons at 2 different locations connected by a VPN one is using number A and one is using number B. Patton with number A is on the same LAN as the 3cx server. Patton with number B is on the other end of the VPN. How do I make the phone at Patton B location use Patton B instead of Patton A?

 

[leejor]

You would do that in the outbound rules. Each route would have been given a unique trunk name in 3CX when you created them. The 3CX Activity Log (Verbose), will show a call matching a rule and using a particular gateway. Perhaps your rules are not in the correct order, or have not been set to force specific extensions, to use one gateway.

 

[Blueskyremote]

I fixed the outbound rules and when my cell the correct ID shows up. When I call the extension from my cell it shows up as anonymous. How would I fix this?

 

[leejor]

Confirm that the provider is sending caller ID to the gateway. Connect a CID device on each phone line if necessary. Once that is confirmed, make sure that the caller ID type, in the gateway, is set correctly, and if required (such as in the case of Bellcore type CID), that the gateway is waiting long enough to capture the information, before passing the call on to 3CX.