09-13-2006 09:27 AM - edited 03-15-2019 04:30 AM
I'm at a customers site and I've just added a PVDM2-16 to the existing PVDM2-32. I then changed the pri-groups from an initial 16 channels of E1 to 31.
Now when I dial in from externally, I'm not getting a ringtone just about 10 seconds of buzzing before the call plays fast busy. You can see the call is connected on the gateway but that's about it.
I'm running CCM 4.2(3).
Any ideas? It's a bog standard config that I regularly use.
Cheers - Dave
Solved! Go to Solution.
09-13-2006 12:45 PM
Dave,
You want to run these commands to help diagnose this.
Sh isdn status
Sh isdn service
Sh voice dsp detailed
Make sure that the new DSP is showing up. You should see a total of 3 DSPs now. Verify after the change that all of the channels are in an Idle state (if not check with Telco and verify their change). I'm thinking the channels are in a bottom up selection from Telco, you increased the channels but either those new channels aren't working or the DSP is not working for the new channels and the calls are coming in on 31. Main thing is you want to verify the channels and the DSPs state. If everything looks well in the sh voice dsp detailed then run the DSP test via the hidden command. Here is the link.
http://www.cisco.com/en/US/products/hw/modules/ps2617/products_tech_note09186a008039c316.shtml#s3
Please rate any helpful posts
Thanks
Fred
09-13-2006 09:31 AM
If using MGCP backhaul, then make sure you didn't lose the necessary configuration when you changed your group. Changing the pri-group requires you to shut the voice-port and removes the old pri-group. When re-adding the pri-group, again if MGCP, make sure this is referenced in the configuration. Can you post the config so we can get a better idea of what you are doing?
Please rate any helpful posts
Thanks
Fred
09-13-2006 11:30 AM
Hi Fred,
I'm using H323. Here's most of the config.
clock timezone GMT 0
clock summer-time BST recurring
network-clock-participate wic 0
network-clock-select 1 E1 0/0/0
!
ip cef
!
voice-card 0
no dspfarm
!
!
voice service voip
h323
h245 caps mode restricted
!
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
!
!
voice class h323 1
h225 timeout tcp establish 3
!
!
controller E1 0/0/0
pri-group timeslots 1-16
description ## xxxx ##
!
!
interface Loopback0
ip address 192.168.10.1 255.255.255.255
!
interface FastEthernet0/0
description ## Connection to Core Switch 7/48 ##
ip address 10.x.x.x x.x.x.x
duplex full
speed 100
h323-gateway voip bind srcaddr 10.17.10.1
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
!
!
ip route 0.0.0.0 0.0.0.0 x.x.x.x
!
ip http server
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
control-plane
!
!
voice-port 0/0/0:15
cptone GB
Cheers
Dave
09-13-2006 12:41 PM
Like Fred said, changing the pri-group requires you to shut the voice-port which removes it from the dial-peer. Check to see if your voice-port is associated with your dial peers.
09-13-2006 12:47 PM
David,
Good suggestion but that shouldn't affect him for external inbound calls unless the dial-peers were physically removed as well. Port statements are only used for outbound dial-peer selection. Definitely would cause a problem if outbound calls from the gateway were the issue.
Thanks
Fred
09-13-2006 02:07 PM
David,
Actually I'm wrong, port is a valid option in inbound selection. Don't know what I was thinking when writing that last post. Here is the inbound matching document. Long day I guess.
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml
Thanks
Fred
09-13-2006 02:10 PM
Hahaha, read a little further and we are both right. It can match on Port but isn't required. If it doesn't match on port or any other dial-peer based off dial-peer selection criteria (incoming called-number, etc.) then it matches on the default dial-peer. I thought that Port wasn't required for inbound but I started to second guess myself, again long day.
Thanks
Fred
09-13-2006 12:45 PM
Dave,
You want to run these commands to help diagnose this.
Sh isdn status
Sh isdn service
Sh voice dsp detailed
Make sure that the new DSP is showing up. You should see a total of 3 DSPs now. Verify after the change that all of the channels are in an Idle state (if not check with Telco and verify their change). I'm thinking the channels are in a bottom up selection from Telco, you increased the channels but either those new channels aren't working or the DSP is not working for the new channels and the calls are coming in on 31. Main thing is you want to verify the channels and the DSPs state. If everything looks well in the sh voice dsp detailed then run the DSP test via the hidden command. Here is the link.
http://www.cisco.com/en/US/products/hw/modules/ps2617/products_tech_note09186a008039c316.shtml#s3
Please rate any helpful posts
Thanks
Fred
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