Hi people,
I have a VoIP link between two branches, which happen to be trading offices. We need a line to be connected at all times, like the lines that bind squak boxes together.
We are using the multicasting solution (hoot-n-holler) with FXS interfaces on each side. At the time of the setup this somehow worked, but for some reason it now works one-way only.
I can speak from one side and be heard on the other side, but not the other way round.
Has anyone done this with two FXSs? I know this works with legacy equipment, as a matter of fact that is what we have running in some other places, but I wonder about the signalling when both interfaces happen to be FXS.
This is the voice port and dialpeer config of one of the routers involved:
!
voice-port 1/0/0
voice-class permanent 1
echo-cancel coverage 32
timeouts wait-release 3
connection trunk 111
music-threshold -30
!
!
dial-peer voice 111 voip
destination-pattern 111
session protocol multicast
session target ipv4:237.111.0.111:22222
dtmf-relay cisco-rtp h245-signal h245-alphanumeric
ip precedence 5
!
Ideas appreciated.
Cheers, Gabriel.
I have a VoIP link between two branches, which happen to be trading offices. We need a line to be connected at all times, like the lines that bind squak boxes together.
We are using the multicasting solution (hoot-n-holler) with FXS interfaces on each side. At the time of the setup this somehow worked, but for some reason it now works one-way only.
I can speak from one side and be heard on the other side, but not the other way round.
Has anyone done this with two FXSs? I know this works with legacy equipment, as a matter of fact that is what we have running in some other places, but I wonder about the signalling when both interfaces happen to be FXS.
This is the voice port and dialpeer config of one of the routers involved:
!
voice-port 1/0/0
voice-class permanent 1
echo-cancel coverage 32
timeouts wait-release 3
connection trunk 111
music-threshold -30
!
!
dial-peer voice 111 voip
destination-pattern 111
session protocol multicast
session target ipv4:237.111.0.111:22222
dtmf-relay cisco-rtp h245-signal h245-alphanumeric
ip precedence 5
!
Ideas appreciated.
Cheers, Gabriel.