07-01-2004 11:21 PM - edited 03-13-2019 05:30 AM
Hello,
I'm trying to get Direct Inward Dialing to work on my Cisco 2650 with a NM-HDV-2E1-60. Outgoing calls work just fine, but incoming calls are not routed.
I read http://www.cisco.com/warp/public/788/AVVID/did-and-callmanager.pdf but it did not work.
Here are my dialer peers so far. The telcoswitch delivers 4769[3-digit-Extension] to the router as called number.
dial-peer voice 1 pots
application mgcpapp
port 1/0:15
!
dial-peer voice 2 pots
application mgcpapp
incoming called-number 4769...
direct-inward-dial
!
dial-peer voice 3 voip
application mgcpapp
destination-pattern 4769...
session target ipv4:[IP-of-CCM]
codec g711alaw
07-02-2004 02:26 AM
Add the port no in dial-peer voice 2 pots
Regds
Prac
07-02-2004 04:06 AM
Unfortunately that did not work. Here is a q931 debug output:
Jul 2 12:04:17.318: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0031
Bearer Capability i = 0x9090A3
Standard = CCITT
Transer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Progress Ind i = 0x8083 - Origination address is non-ISDN
Calling Party Number i = 0x2181, '[calling-number]'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '4769265'
Plan:ISDN, Type:Subscriber(local)
Jul 2 12:04:17.330: ISDN Se1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x
8031
Cause i = 0x8081 - Unallocated/unassigned number
07-02-2004 04:39 AM
Add 'incoming called-number 4769...' to your voip dial-peer instead of pots
07-02-2004 05:23 AM
Dial-peer 2 is missing the Voice Port.
If i were you, i would make it simpler.
Dial-peer voice 1 pots
aplication mgcpapp
incoming-called-number .
port x/x:y
No need for dial-peer voice 2 pots
Then control the digits to be accepted at the gateway level.
07-02-2004 05:38 AM
Forgot to mention that you can include "direct-inward-dialing" statement in dial-peer 1 itself.
Thanks
07-02-2004 06:14 AM
Hello ,
Make sure in the call manager gateway page for inbound calls correct calling search space is choosen.
Thanks,
Radhika
07-02-2004 06:30 AM
OK, I changed some things:
The gateway now receives all digits of the called number, but only reads the last three, the extension. It is in the same CSS as my phones (PhoneCSS), but still no luck!
And why keep I getting this q931 error when I receive calls?
Jul 2 14:27:35.090: ISDN Se1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0045
Bearer Capability i = 0x9090A3
Standard = CCITT
Transer Capability = 3.1kHz Audio
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Progress Ind i = 0x8083 - Origination address is non-ISDN
Calling Party Number i = 0x2181, '7216100265'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '4769265'
Plan:ISDN, Type:Subscriber(local)
Jul 2 14:27:35.098: ISDN Se1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x
8045
Cause i = 0x8081 - Unallocated/unassigned number
My current dial peers:
dial-peer voice 1 pots
application mgcpapp
incoming called-number .
direct-inward-dial
port 1/0:15
!
dial-peer voice 3 voip
application mgcpapp
destination-pattern .
session target ipv4:172.23.64.100
codec g711alaw
07-02-2004 06:39 AM
Hello,
Do you have "isdn overreciving" command on the int serial1/0:15 of the ISdn ?
Take a look at the following link
http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00800b48cb.shtml
Thanks,
Radhika
07-02-2004 06:57 AM
I do not use the "isdn overlap-receiving" command.
Here is the full config:
version 12.3
service config
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname vgw201
!
boot-start-marker
boot-end-marker
!
logging buffered 10000 debugging
enable secret 5 [deleted]
enable password 7 [deleted]
!
username [deleted] password 7 [deleted]
clock timezone CEST 1
clock summer-time CEST recurring last Sun Mar 2:00 last Sun Oct 3:00
no network-clock-participate slot 1
no network-clock-participate wic 0
voice-card 1
!
no aaa new-model
ip subnet-zero
ip cef
!
!
ip domain name [deleted]
ip name-server [deleted]
!
isdn switch-type primary-net5
!
ccm-manager switchback immediate
ccm-manager mgcp
ccm-manager config
!
controller E1 1/0
pri-group timeslots 1-31 service mgcp
!
controller E1 1/1
!
interface FastEthernet0/0
ip address [deleted]
duplex auto
speed auto
no cdp enable
!
interface Serial1/0:15
no ip address
no logging event link-status
isdn switch-type primary-net5
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
ip http server
ip classless
ip route [deleted]
!
!
no cdp run
!
snmp-server [deleted]
snmp-server enable traps tty
!
voice-port 1/0:15
cptone DE
!
mgcp
mgcp call-agent [deleted] service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode cisco
mgcp sdp simple
!
mgcp profile default
!
dial-peer voice 1 pots
application mgcpapp
incoming called-number .
direct-inward-dial
port 1/0:15
!
dial-peer voice 3 voip
application mgcpapp
destination-pattern .
session target ipv4:[deleted]
codec g711alaw
!
!
call-manager-fallback
limit-dn 7910 1
limit-dn 7935 1
limit-dn 7940 1
limit-dn 7960 1
ip source-address [deleted] port 2000
max-ephones 48
max-dn 192
time-format 24
date-format dd-mm-yy
!
!
line con 0
exec-timeout 60 0
password 7 [deleted]
absolute-timeout 60
logging synchronous
login
line aux 0
password 7 [deleted]
login
line vty 0 4
exec-timeout 60 0
password 7 [deleted]
absolute-timeout 60
login
line vty 5 15
exec-timeout 60 0
password 7 [deleted]
absolute-timeout 60
login
!
ntp clock-period 17208421
ntp server [deleted]
What did I do wrong? Outgoing calls work just fine!
07-02-2004 07:28 AM
Please modify your VOIP dialpeer. Destination pattern is not correct. It should be more than a ".".
if your internal numbering sceme is 3xx or 4xx,etc make sure your destination pattern under VOIP dialpeer says 3.. or 4..
Also, your debugs show that the telco is sending you 7 digits, your POTS dialpeer is accepting all digits, make sure that you accept only the last 3 digits at the gateway level or modify the POTS dialpeer.
Also, you might want to consider Radhika's advice regarding ISDN-Overlap.
Here is the Doc.
http://www.cisco.com/warp/public/788/signalling/isdn_overlap_prob.html
after you make the changes, try calling from the router using csim start xxxx command to check if it is a gateway/CCS issue or PSTN signalling issue.
Thanks
Thanks,
07-02-2004 09:50 AM
Hello ,
One more thing.On the callmanager gateway configuration page for inbound calls verify the number of significant digits are correctly set.
Thanks,
Radhika.
07-02-2004 09:57 AM
Hello,
thanks for all the tips. I shall try these on Monday morning, for now I am off into the Weekend.
Have a nice weekend y'all!
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