Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Bronze

FXS/DID number of digits outpulsed different than what is recieved

I have analog DID's from the Telco configured for wink-start.  A switch tech has confirmed they are outpulsing 4 digits.  However, "debug vpm all" shows only 3 digits recieved and when configured for 3 works fine.  Could there be a potential timing issue where the router is not ready to recieve the leading digit? If so what are some suggested timing commands?

Testing late last night and had to plug them back into production dialogic board so I don't have a working "debug vpm all" output right now.

3845

12.4.24(T4)

vic3-4fxs/did

!
voice-port 0/3/0
signal did wink-start
!
dial-peer voice 500 voip
description "To Call Manager"
destination-pattern [0-9]...
voice-class codec 1
voice-class h323 1
session target ipv4:x.x.x.x
incoming called-number .
dtmf-relay h245-alphanumeric
!

Thanks in advance.

3 REPLIES
Cisco Employee

Re: FXS/DID number of digits outpulsed different than what is re

I am assuming its the leading digit (first digit) that is missing ?

Most likely due to the cause you have identified aleady. Router

port not ready before the digit comes in...so yes, a timing issue.

GW should be ready soon after it sends wink to rec. the digits

and doubt we can change any port timing on IOS side for it to

rec. digits faster.

Switch side needs to introduce a little delay (few hundred millisec)

after rec. the wink before outpusling the digits for it to work properly.

Or is it that they are outpulsing without waiting for a wink ? In which

case, you shd be configured for immediate-start - have u tried that

just for testing sake?

Can u share ur config along with vpm signal digits ?

Bronze

Re: FXS/DID number of digits outpulsed different than what is re

Applicable configuration below.  The analog DID's can only be tested after hours so I will have to try the signal immediate again later on.  Unfortunately I did not save any of the debug vpm outputs so I will have to get that later. Voice Port 0/3/0 - 3 are my ports in question.

voice call carrier capacity active
!
voice service voip
fax protocol cisco
!
!
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
codec preference 3 g729br8
!
!
!
!
voice class h323 1
  h225 timeout tcp establish 30
!
controller T1 0/0/0
shutdown
!
controller T1 0/0/1
shutdown
!
controller T1 0/1/0
pri-group timeslots 1-24 service mgcp
!
controller T1 0/1/1
pri-group timeslots 1-24 service mgcp
!
!
interface GigabitEthernet0/0
ip address x.x.x.x 255.255.255.0
ip flow ingress
duplex auto
speed auto
media-type rj45
h323-gateway voip interface
h323-gateway voip bind srcaddr x.x.x.x
!
interface GigabitEthernet0/1
no ip address
shutdown
duplex auto
speed auto
media-type rj45
!
interface Serial0/1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
interface Serial0/1/1:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
!
voice-port 0/1/0:23
echo-cancel coverage 64
!
voice-port 0/1/1:23
echo-cancel coverage 64
!
voice-port 0/2/0
echo-cancel coverage 24
timing hookflash-out 50
!
voice-port 0/2/1
!
voice-port 0/3/0
signal did wink-start
!
voice-port 0/3/1
signal did wink-start
!
voice-port 0/3/2
signal did wink-start
!
voice-port 0/3/3
signal did wink-start
!
ccm-manager fallback-mgcp
ccm-manager redundant-host x.x.x.x
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server x.x.x.x
ccm-manager config
!
mgcp
mgcp call-agent x.x.x.x 2427 service-type mgcp version 0.1
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
mgcp default-package fxr-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax rate 9600
mgcp fax t38 ls_redundancy 2
mgcp fax t38 hs_redundancy 2
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 999020 pots
service mgcpapp
port 0/2/0
!
dial-peer voice 500 voip
description "To Call Manager"
preference 1
destination-pattern [0-9]..
voice-class codec 1
voice-class h323 1
session target ipv4:x.x.x.x
incoming called-number .
dtmf-relay h245-alphanumeric
!
dial-peer voice 501 voip
description "To call Manager"
destination-pattern [0-9]..
voice-class codec 1
voice-class h323 1
session target ipv4:x.x.x.x
dtmf-relay h245-alphanumeric
!
dial-peer voice 100 pots
incoming called-number .
direct-inward-dial
port 0/3/0
!
dial-peer voice 101 pots
direct-inward-dial
port 0/3/1
!
dial-peer voice 102 pots
direct-inward-dial
port 0/3/2
!
dial-peer voice 103 pots
direct-inward-dial
port 0/3/3
!
!

New Member

FXS/DID number of digits outpulsed different than what is reciev

We just experienced this exact issue. Using a buttset we could monitor the DTMF tones. The digits were being sentfrom the CO switch before the cisco gateway wink was complete. We also would miss the first inbound digit. We solved this by changing the wink duration to be shorter. This is in the Timing config.

1039
Views
0
Helpful
3
Replies