Call-setup disconnect on FXO lines

Answered Question
Sep 18th, 2008
User Badges:

Having 2 kinds of analog lines from different provider:


1. "WORKING" national/international


--> the following VG config works well, signaling frequency have been measured to set-up accordingly. NO PROBLEM!


voice class custom-cptone EG-Giv

dualtone busy

frequency 1415 1820

cadence 200 300 200 300

dualtone disconnect

frequency 450

cadence 250 250


voice-port 0/1/2

trunk-group AnalogTrunk2-EgyptTelecom-OutInt

supervisory disconnect dualtone mid-call

supervisory answer dualtone

no battery-reversal

cptone EG

connection plar 2761400

impedance complex2

description <REMOVED>

station-id number <REMOVED>

caller-id enable



2. "NOT WORKING" mobile


--> Cannot find a proper configuration, symptom for outgoing AND incoming calls: DIALING STATE --> RINGING STATE --> CONNECT STATE (and call is disconnected)


After line measurements, state voltage are the following:


Call Cycle in DC voltages

On-hook state 48V

Ringing state -38V 38 V in 1st ring, then 0V then 38V starting from the second ring onwards

Answered state -11V

Disconnect state 11V


voice-port 0/2/2

trunk-group AnalogTrunk3-EgyptTelecom-OutMob

battery-reversal

cptone EG

connection plar 2761400

impedance complex2

description <REMOVED>

station-id number <REMOVED>

caller-id enable


--> Tested with & without "battery-reversal", but did not help. According to voltage change, "reverse polarity" as stated by telco provider should be translated to battery-reversal ???

--> Found Cisco doc but did not help: http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00800ae2d1.shtml

Anyone face similar problem ? (IOS version: 124-20.T)

Any idea to get it working ???


PS: the line is known to be working as it was primarily connected to TDM PBX



Correct Answer by jbayuka about 8 years 9 months ago

The cause of the problem is that incoming calls across the FXO was sent to another FXO port instead of being sent to CCM. This causes both ports to get stuck in connect state.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 1 (1 ratings)
Loading.
Correct Answer
jbayuka Wed, 09/24/2008 - 12:15
User Badges:
  • Bronze, 100 points or more

The cause of the problem is that incoming calls across the FXO was sent to another FXO port instead of being sent to CCM. This causes both ports to get stuck in connect state.

DANIEL COHEN-LAROQUE Wed, 09/24/2008 - 22:23
User Badges:

Hi Guys,


I finally solved this issue, by adjusting fxo lines as follow:


voice class dualtone-detect-params 1

freq-max-deviation 25

cadence-variation 4


voice class custom-cptone EG-Giv-Mob

dualtone busy

frequency 425

cadence 200 200

dualtone disconnect

frequency 425

cadence 200 200


voice-port 0/2/1

trunk-group AnalogTrunk3-EgyptTelecom-OutMob

supervisory disconnect dualtone mid-call

supervisory answer dualtone

supervisory custom-cptone EG-Giv-Mob

supervisory dualtone-detect-params 1

no battery-reversal

timeouts call-disconnect 5

timeouts ringing 10

timeouts wait-release 5

connection plar 2761300

description

station-id number

caller-id enable


Hope that can help others ;-)


robertdm1973 Fri, 10/17/2008 - 00:53
User Badges:

Hi DCohen, which debug command(s) do you use to be determine which parameters to adjust?


Thanks.

Actions

This Discussion