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.

New Member

conversion from vofr to voip issue

I recently had to change the dial peers on my wan links from vofr to voip to make the QOS work for a VOIP phone system.

basic setup is the routers have E&M ports installed and connected properly to the local PBX systems. Calls to and from these locations work. But the dial peers setup so that a remote location could get dial tone from the main and place an outside call off the the main PBX does not work.

dial peer example original vofr

voice-port 2/0

no comfort-noise

operation 4-wire

type 2

signal immediate

!

voice-port 2/1

no comfort-noise

operation 4-wire

type 2

signal immediate

!

!

dial-peer cor custom

!

!

!

dial-peer voice 20 pots

preference 1

destination-pattern 81...

port 2/0

!

dial-peer voice 21 pots

huntstop

preference 2

destination-pattern 81...

port 2/1

!

dial-peer voice 80 vofr

destination-pattern 80...

session target Serial0/0 16

!

dial-peer voice 82 vofr

destination-pattern 82...

session target Serial0/0 17

!

dial-peer voice 83 vofr

destination-pattern 84

session target Serial0/0 18

!

dial-peer voice 8192 pots

preference 1

destination-pattern 8192

port 2/0

forward-digits 2

!

dial-peer voice 81921 pots

huntstop

preference 2

destination-pattern 8192

port 2/1

forward-digits 2

!

dial-peer voice 85 vofr

destination-pattern 85...

session target Serial0/0 19

when I converted these to voip I changed the session target to the appropriate ipv4:x.x.x.x

and added dtmf-relay cisco-rtp

all the dial peers work except the

dial-peer voice 8192 pots

preference 1

destination-pattern 8192

port 2/0

forward-digits 2

!

dial-peer voice 81921 pots

huntstop

preference 2

destination-pattern 8192

port 2/1

forward-digits 2

the calling end of the dial peer pair looks like this

dial-peer voice 8192 voip

destination-pattern 8192

session target ipv4:192.168.2.1

dtmf-relay cisco-rtp

the symptoms are the user placing the call are getting dial tone from the remote location but can not "break dial tone" so it appears that the dtmf digits dialed after the call is connected from location to location are not being passed. dialed digits after the user had dial tone where being passed before the conversion.

It appears that I have missed something in the conversion that is not allowing the dtmf digits to pass after dial tone is pulled from the remote system.

Dos eny one have a sugestion on what to try, or a referance to the appropriate material so I can fix this issue?

Gene

3 REPLIES
Blue

Re: conversion from vofr to voip issue

A router to router H323 call has 4 legs: inbound POTS peer, outbound VOIP peer -------- inbound VOIP peer, outbound POTS peer.

What may be happening is that the inbound VOIP leg is matching the default peer 0, which can not do DTMF relay, rather than the peer you have defined with DTMF relay. To see if this is the problem, place a test call, then show call active voice brief on the router that is receiving the call. You will see an output that will show the PID (peer ID) for both legs. Here is a router inbound call using default VOIP peer 0 and POTS peer 15.

F3D : 770282 -2102137120hs.1 +26 pid:0 Answer active

dur 00:00:36 tx:1830/292800 rx:1825/292000

IP 10.55.10.249:19524 rtt:4ms pl:35495/0ms lost:0/1/0 delay:54/54/65ms cisco

media inactive detected:n media contrl rcvd:n/a timestamp:n/a

F3D : 770283 -2102137118hs.1 +24 pid:15 Originate *6652 active

dur 00:00:36 tx:1825/292000 rx:1825/292000

Tele 0/2/1:23 (770283) [0/2/1.1] tx:36500/36500/0ms cisco noise:-84 acom:64 i/0:-79/-14 dBm

If the VOIP side is 0 you need to force the call to match the correct peer. You can use incoming called-number XXXX under the VOIP peer. An alternative is to set the voice ports to send a calling number that matches the destination pattern of the VOIP peers on the far side. station-id number XXXX If the inbound calling number matches the destination pattern the peer will match.

Here is a good document on peer matching:

http://www.cisco.com/en/US/customer/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#topic4

Please rate helpful posts.

Silver

Re: conversion from vofr to voip issue

I would switch the dtmf-relay from cisco-rtp to h245-alphanumeric. I have had good results from that, and ran across something that made me suspect there could be issues with the cisco stuff, don't remember what exactly.

Mary Beth

Silver

Re: conversion from vofr to voip issue

First check the peer matching, as mentioned above - because no dtmf relay will work if you are matching that 0 peer - change the type if you are still having trouble. If you are matching a different peer inbound, you would want to figure out why, but if you have dtmf relay on that peer, it should work.

194
Views
5
Helpful
3
Replies
CreatePlease login to create content