voip and tandem connection

Unanswered Question
May 3rd, 2007

Here is the scenario;

1000-fxs-RA--IP--RB--IP--RC-fxs-3000. I

RA:

Dial peer 100 voip

destination-pattern 3000

sess target ipv4:RB

Rb:

Dial peer 100 voip

destination-pattern 3000

sess target ipv4:RB

Will 1000 able to call 3000 via this tandem connection? I have to do this for a very special reason. Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (3 ratings)
Loading.
Paolo Bevilacqua Fri, 05/04/2007 - 00:40

Hi,

this "tandem" is called IP-to-IP Gateway, or BSC - Border Session Controller, in Cisco parlance.

Yes it's supported, however Rb will need to run and IP-to-IP image, which image name ends with _isv, at that point it will be able to connect VoIP even when different signaling protocols are used, and do (some limited) transcoding, plus other things

Be courteous, in exchange of received answers, rate useful posts!

ciscoforum Fri, 05/04/2007 - 09:19

Thanks. Do you know what's the commmand? or which link has the detailed information?

Paolo Bevilacqua Fri, 05/04/2007 - 10:25

These are the commands

voice service voip

allow-connections h323 to h323 (or any combination you are using)

dial-peer voice XX voip

codec transparent

that's it.

As a courtesy to those providing answers, please rate all posts using the scrollbox below!

Paolo Bevilacqua Tue, 05/08/2007 - 12:02

Or configure a voice-class that lists the codecs you want allow the endpoints to negotiate.

Remember to rate useful posts as an appreciation for those providing answers!

kelvin.blair Tue, 05/08/2007 - 13:54

You can either use the voice class or transparent. The transparent will use what ever the other ends offers. The voice class will allow you to set a restriction on what codecs to use and it is up to both parties to decide on which to use. One problem with this is that if both parties disagree on codec, then you will get a codec mismatch and the call will be busy out.

ciscoforum Sun, 05/13/2007 - 18:59

So then I don't think we need _ivs image since the following commands is supported in voiceip image too, right?

voice service voip

allow-connections h323 to h323

Actions

This Discussion