Call from FSX port on MC3810 to fxs port on a VG200
pullin-gs
Member Posts: 38 ■■□□□□□□□□
....wont work.
It works fine from MC3810 to another MC3810.
It also works when I originate call from VG200 directed to MC810.
But whenever I originate the call from the MC3810 directed to the VG200 I get no ring or anything. The RX is just white-noise.
I upgraded IOS from 12.2 to a 12.3(35).
No work. The only difference now is that I get a "beeb-beeb-beeb-beeb" (not a fast busy, but high-pitch tone beeps).
Ideas?
VG200 code:
!
dial-peer voice 10002 pots
destination-pattern 10002
port 1/0/0
!
dial-peer voice 20001 voip
destination-pattern 20001
session target ipv4:10.1.1.4
codec g711alaw
ip qos dscp af31 media
!
voice-port 1/0/0
codec g711alaw
!
!
***************************************
MC3810 code:
!
!
voice-port 1/1
description POTS phone
codec g711alaw
!
dial-peer voice 20001 pots
destination-pattern 20001
port 1/1
!
dial-peer voice 10002 voip
destination-pattern 10002
session target ipv4:10.1.1.9
codec g711alaw
ip qos dscp af31 media
!
It works fine from MC3810 to another MC3810.
It also works when I originate call from VG200 directed to MC810.
But whenever I originate the call from the MC3810 directed to the VG200 I get no ring or anything. The RX is just white-noise.
I upgraded IOS from 12.2 to a 12.3(35).
No work. The only difference now is that I get a "beeb-beeb-beeb-beeb" (not a fast busy, but high-pitch tone beeps).
Ideas?
VG200 code:
!
dial-peer voice 10002 pots
destination-pattern 10002
port 1/0/0
!
dial-peer voice 20001 voip
destination-pattern 20001
session target ipv4:10.1.1.4
codec g711alaw
ip qos dscp af31 media
!
voice-port 1/0/0
codec g711alaw
!
!
***************************************
MC3810 code:
!
!
voice-port 1/1
description POTS phone
codec g711alaw
!
dial-peer voice 20001 pots
destination-pattern 20001
port 1/1
!
dial-peer voice 10002 voip
destination-pattern 10002
session target ipv4:10.1.1.9
codec g711alaw
ip qos dscp af31 media
!
Comments
-
dtlokee Member Posts: 2,378 ■■■■□□□□□□I'm assuming it's connected FXS to FXO?The only easy day was yesterday!
-
pullin-gs Member Posts: 38 ■■□□□□□□□□No, It's VOIP peering (see code).
One POTS phone in an FSX port on the MC3810
Another POTS phone in an FSX port on the VG200
IP-WAN (lab...pings fine) connecting the two together.
I peer off the loopbacks -
dtlokee Member Posts: 2,378 ■■■■□□□□□□Sorry I saw the title of the thread and thought you had them connected FXS to FXS and didn't try to debug the code
SOunds like a failure to negotiate some attribute of the call, try debug h245 events and debug 225 events and see what it give youThe only easy day was yesterday! -
pullin-gs Member Posts: 38 ■■□□□□□□□□Thanks for the fast reply. I'll try that.
...this has got a buggy feel to it.
Cheers! -
pullin-gs Member Posts: 38 ■■□□□□□□□□Doh!
It's fixed.
I had the pots dial-peers setup in my config pointing to the wrong ports.
I made the mistake of assuming cisco numbered their port# on these things from left to right.
Nope.....it is right to left....the ports I referenced were FXO ports with nothing plugged up.
Now why on earth it was working for outbound calls?
I guess my pots voice peers are only applicable for incoming calls, thus the reason my outgoing calls did not reference them?
Three hours wasted away! -
dtlokee Member Posts: 2,378 ■■■■□□□□□□Yeah the dial peers are only needed for the called number, even if that number is on the same voice router or a different one. I guess similar to an IP route, we don't care about where it came from only here it's going.The only easy day was yesterday!