11-18-2008 04:53 PM - last edited on 03-25-2019 09:28 PM by ciscomoderator
I have an MGCP gateway. One of the FXO card has an intercom that has only the ability to generate tone plugged into it. On the gateway a dial-peer with this config is in there: See attachment please.
When you press the intercom the device calls a number but shows up as unknown. How can I make this device show a caller id instaed of unknow. PS. I tried the clid command and caller-id enable command under the dial-peer and voiceport already and this didn't work.
The gateway is controlled by Cisco call manager.
Any help appreciated.
!
voice-port 0/0/0
connection plar 9497247540
caller-id enable
!
voice-port 0/0/1
!
voice-port 0/0/2
timing hookflash-out 500
description Paging System
!
voice-port 0/0/3
timing hookflash-out 500
connection plar 9497247444
description Front Door Intercom
caller-id enable
!
voice-port 0/1/0
!
voice-port 0/1/1
!
voice-port 0/1/2
!
voice-port 0/1/3
connection plar 9497246155
!
ccm-manager fallback-mgcp
ccm-manager redundant-host COI-MCS7835-1
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.20.251.10
ccm-manager config
!
mgcp
mgcp call-agent COI-MCS7835-2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface GigabitEthernet0/0
mgcp bind media source-interface GigabitEthernet0/0
!
mgcp profile default
!
!
!
dial-peer voice 7744 voip
description Front Door Intercom
destination-pattern 9497247444
voice-class codec 323
session target ipv4:10.20.250.10
!
dial-peer voice 6123 voip
destination-pattern 9497246155
voice-class codec 323
session target ipv4:10.20.250.10
!
dial-peer voice 5001 pots
description Front Door Intercom
service mgcpapp
destination-pattern 5001
port 0/0/3
!
dial-peer voice 999002 pots
service mgcpapp
destination-pattern ##59
port 0/0/2
!
dial-peer voice 999010 pots
service mgcpapp
port 0/1/0
!
dial-peer voice 999011 pots
service mgcpapp
port 0/1/1
!
dial-peer voice 2 pots
description Outbound calls
destination-pattern 91..........
incoming called-number .T
port 0/0/1
forward-digits 11
!
dial-peer voice 6000 pots
translation-profile outgoing maintainFourDigits
destination-pattern 6...
port 0/0/1
!
dial-peer voice 7000 pots
translation-profile outgoing maintainFourDigits
destination-pattern 7...
port 0/0/1
!
dial-peer voice 3 pots
description Outbound calls
destination-pattern 9[2-9]......
incoming called-number .T
port 0/0/1
forward-digits 7
!
dial-peer voice 5059 voip
incoming called-number ##59
!
dial-peer voice 999003 pots
service mgcpapp
port 0/0/3
!
!
call-manager-fallback
secondary-dialtone 9
max-conferences 8 gain -6
transfer-system full-consult
timeouts interdigit 5
timeouts ringing 30
ip source-address 10.1.1.249 port 2000
max-ephones 52
max-dn 192
system message primary Please call HelpDesk 9-7246147
transfer-pattern 949724....
!
Solved! Go to Solution.
11-18-2008 05:45 PM
The 17xx, 26xx and 36xx gateways do not forward caller ID from a FXO port to the CallManager in MGCP mode
http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K20807102
Caller ID cannot be passed from a Foreign Exchange Office (FXO) port on any of the 17xx, 26xx and 36xx gateways that run in Media Gateway Control Protocol (MGCP) mode. However, the caller ID can be passed from a PRI or a Foreign Exchange Station (FXS).
Alternatively, if caller ID support is essential on the FXO port, configure the gateway to run in H323 mode.
HTH
java
if this helps, please rate
11-18-2008 05:45 PM
The 17xx, 26xx and 36xx gateways do not forward caller ID from a FXO port to the CallManager in MGCP mode
http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K20807102
Caller ID cannot be passed from a Foreign Exchange Office (FXO) port on any of the 17xx, 26xx and 36xx gateways that run in Media Gateway Control Protocol (MGCP) mode. However, the caller ID can be passed from a PRI or a Foreign Exchange Station (FXS).
Alternatively, if caller ID support is essential on the FXO port, configure the gateway to run in H323 mode.
HTH
java
if this helps, please rate
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide