Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

FXO port, hears 5 rings before the call is connected

Dear all,

When an incoming call rings on a Cisco 2921 FXO port, the caller hears 5 rings before the call is connected.  Does anyone know of a way to shorten or eliminate  this delay?

Please find attached the configuration and sceanario as following:

Cisco 2921 04 FXO with H323 configuration and 4 FXS with MGCP configuration.

Cisco Call Manager 8.6

Thanks you for your help.

1 ACCEPTED SOLUTION

Accepted Solutions
Green

FXO port, hears 5 rings before the call is connected

Hi,

Your router is failing with a cause code 18 on dial peer 1

!

dial-peer voice 1 voip

preference 1

destination-pattern [1-7]...

session target ipv4:172.16.69.10

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 2 voip

preference 2

destination-pattern [1-7]...

session target ipv4:172.16.69.14

dtmf-relay h245-alphanumeric

codec g711ulaw

This is your preference 1 --- 1st choice

It then timesout and reties on dial peer 2 --  this is succesful.

Look for connectivity issues between the router IP address 172.16.69.18 and the call processor CCM on 172.16.69.10

May be the call manager service is not running or there is no pings etc.

HTH

Alex

Please rate useful posts

Regards, Alex. Please rate useful posts.
22 REPLIES
Green

FXO port, hears 5 rings before the call is connected

Hi,

You can try changing your PLAR to immediate

!

voice-port 0/0/0

cptone GB

connection plar opx immediate 6002

impedance 600c

station-id name PSTN

station-id number 35123497

Please be aware that this may stop the inbound CLI being presented if you need it.

Try and test

HTH

Alex

Please rate useful posts

Regards, Alex. Please rate useful posts.
Community Member

FXO port, hears 5 rings before the call is connected

Dear Alex,

I try your comment, but it still have no luck. Any help ?

Regards,

Thanh

Hall of Fame Super Silver

Re: FXO port, hears 5 rings before the call is connected

Does it ring 5 times after hitting the GW? Or before even hitting it?

Sent from Cisco Technical Support iPhone App

Community Member

FXO port, hears 5 rings before the call is connected

Dear Chris,

Maybe it ring 5 times after hitting the GW because on the first ring gateway FXO Port light up.

Regards,

Thành

Hall of Fame Super Silver

Re: FXO port, hears 5 rings before the call is connected

can you post your full GW config?

Any chance there is an overlapping pattern/DN on CUCM causing interdigit timeout?

Sent from Cisco Technical Support iPhone App

Community Member

FXO port, hears 5 rings before the call is connected

Dear Chris,

You can find the attached file configuration in the first post above. Anyway i repost:

I had two Call Manager.

Extension range: 1xxx - 3xxx

Auto-Attendant & CTI port: 6xxx

icense udi pid CISCO2911/K9 sn FGL1601126G

hw-module pvdm 0/0

!

!

!

!

redundancy

!

!

!

!

!

!

interface Embedded-Service-Engine0/0

no ip address

shutdown

!

interface GigabitEthernet0/0

description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$

ip address 172.16.69.18 255.255.255.0

duplex auto

speed auto

h323-gateway voip interface

h323-gateway voip bind srcaddr 172.16.69.18

!

interface GigabitEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

interface GigabitEthernet0/2

no ip address

shutdown

duplex auto

speed auto

!

ip forward-protocol nd

!

ip http server

ip http access-class 23

ip http authentication local

ip http secure-server

ip http timeout-policy idle 60 life 86400 requests 10000

!

ip route 0.0.0.0 0.0.0.0 172.16.69.1

!

!

!

!

control-plane

!

!

voice-port 0/0/0

cptone GB

connection plar opx 6002

impedance 600c

station-id name PSTN

station-id number 35123497

!

voice-port 0/0/1

timing hookflash-out 50

!

voice-port 0/0/2

timing hookflash-out 50

!

voice-port 0/0/3

timing hookflash-out 50

!

voice-port 0/1/0

!

voice-port 0/1/1

!

voice-port 0/1/2

!

voice-port 0/1/3

!

ccm-manager redundant-host 172.16.69.14

ccm-manager mgcp

no ccm-manager fax protocol cisco

ccm-manager music-on-hold

ccm-manager config server 172.16.69.10

ccm-manager config

!

mgcp

mgcp call-agent 172.16.69.10 2427 service-type mgcp version 0.1

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

mgcp package-capability sst-package

mgcp package-capability pre-package

no mgcp package-capability res-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

!

mgcp profile default

!

!

dial-peer voice 999010 pots

service mgcpapp

port 0/1/0

!

dial-peer voice 1 voip

preference 1

destination-pattern [1-7]...

session target ipv4:172.16.69.10

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 21 pots

destination-pattern .T

direct-inward-dial

port 0/0/0

forward-digits all

!

dial-peer voice 2 voip

preference 2

destination-pattern [1-7]...

session target ipv4:172.16.69.14

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 999011 pots

service mgcpapp

port 0/1/1

!

dial-peer voice 999012 pots

service mgcpapp

port 0/1/2

!

dial-peer voice 999013 pots

service mgcpapp

port 0/1/3

!

Hall of Fame Super Silver

FXO port, hears 5 rings before the call is connected

Your dial-peer 21 is creating an overlap thus causing the inter-digit timeout.  You need to make it something other than .T, something more explicit that does not overlap with [1-7]...  If you are using Off-Net access code on CUCM, you need not to strip it on CUCM and change this dial-peer to 9.T for example.

HTH,

Chris

Community Member

FXO port, hears 5 rings before the call is connected

Dear Chris,

Thanks for your support. I try to remove all dial-peer except dial-per voice 1 voip

dial-peer voice 1 voip

preference 1

destination-pattern 6002

session target ipv4:172.16.69.10

dtmf-relay h245-alphanumeric

codec g711ulaw

With only this one, the call ring forever and cant connect to.

Regards,

Hall of Fame Super Silver

Re: FXO port, hears 5 rings before the call is connected

how about if you add back dial peer 2? Perhaps that CUCM is not responding or not in the cm group.

Sent from Cisco Technical Support iPhone App

Community Member

FXO port, hears 5 rings before the call is connected

When i add back dial peer 2, the call can be connected but still after 5 ring times.

I added two call manager in one group already.

Hall of Fame Super Gold

FXO port, hears 5 rings before the call is connected

Please take "debug vpm signal" and "debug ccapi inout" with "term mon".

Do not take other debugs. Do not use attachments.

Just poste in the relevant information preferably in a fixed font.

Green

FXO port, hears 5 rings before the call is connected

Thanh

Can you clarify if the 5 rings is on calls to or from the PSTN.

I also notice that the CUCM IP addresses and the router IP address are on the same subnet.

They are probably in the same building.

If this is the case you should remove the PLAR OPX to make it just PLAR

!

voice-port 0/0/0

no connection plar opx 6002

connection plar 6002

!

Try & test

Regards

Alex

Regards, Alex. Please rate useful posts.
Community Member

Re: FXO port, hears 5 rings before the call is connected

Dear all,

Please find debug of voicegateway as following:

HO-VG-02#

Feb 20 08:52:47.511: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fx                                                                                        ols_onhook_ringing

Feb 20 08:52:47.511: htsp_timer - 125 msec

Feb 20 08:52:47.639: htsp_process_event: [0/0/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVE                                                                                        NT_TIMER]fxols_wait_ring_min_timer

Feb 20 08:52:47.639: htsp_timer - 10000 msec

Feb 20 08:52:48.603: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100]

Feb 20 08:52:48.603: fxols_ringing_not

Feb 20 08:52:48.603: htsp_timer_stop

Feb 20 08:52:48.603: htsp_timer_stop3 htsp_setup_ind

Feb 20 08:52:48.603: [0/0/0] get_local_station_id calling num=35123497 calling n                                                                                        ame=PSTN calling time=02/20 08:52  orig called=

Feb 20 08:52:48.603: htsp_process_event: [0/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SE                                                                                        TUP_ACK]

Feb 20 08:52:48.603: fxols_wait_setup_ack:

Feb 20 08:52:48.603: htsp_timer - 6000 msec

Feb 20 08:52:48.607: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEE                                                                                        DING]fxols_offhook_proc

Feb 20 08:52:52.571: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

Feb 20 08:52:52.571: htsp_timer_stop

Feb 20 08:52:52.571: htsp_timer_stop2

Feb 20 08:52:53.679: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0100]fxols_proceed_clear

Feb 20 08:52:53.679: htsp_timer_stop2

Feb 20 08:52:53.679: htsp_timer - 6000 msec

Feb 20 08:52:57.647: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

Feb 20 08:52:57.647: htsp_timer_stop

Feb 20 08:52:57.647: htsp_timer_stop2

Feb 20 08:52:58.759: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0100]fxols_proceed_clear

Feb 20 08:52:58.759: htsp_timer_stop2

Feb 20 08:52:58.759: htsp_timer - 6000 msec

Feb 20 08:53:02.703: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

Feb 20 08:53:02.703: htsp_timer_stop

Feb 20 08:53:02.703: htsp_timer_stop2 htsp_alert_notify

Feb 20 08:53:03.647: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)

Feb 20 08:53:03.679: htsp_call_bridged invokedhtsp_call_service_msghtsp_call_service_msg not EFXS (2)

Feb 20 08:53:03.679: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect

Feb 20 08:53:03.679: [0/0/0] set signal state = 0xC timestamp = 0

Feb 20 08:53:03.679: htsp_timer_stop

Feb 20 08:53:03.679: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice

Feb 20 08:53:03.883: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_DSP_SIG_0100]fxols_normal_battery

Feb 20 08:53:03.883: htsp_timer_stop2

Feb 20 08:53:03.955: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_DSP_SIG_0110]fxols_rvs_battery

Feb 20 08:53:03.955: htsp_timer_stop2

Feb 20 08:53:03.959: htsp_timer_stop2

Feb 20 08:53:20.551: htsp_timer_stop3

Feb 20 08:53:20.567: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_RELEASE_REQ]fxols_offhook_release

Feb 20 08:53:20.567: htsp_timer_stop

Feb 20 08:53:20.567: htsp_timer_stop2

Feb 20 08:53:20.567: htsp_timer_stop3

Feb 20 08:53:20.567: [0/0/0] set signal state = 0x4 timestamp = 0

Feb 20 08:53:20.567: htsp_timer - 2000 msec

Feb 20 08:53:20.839: htsp_process_event: [0/0/0, FXOLS_GUARD_OUT, E_DSP_SIG_0110]

Feb 20 08:53:22.567: htsp_process_event: [0/0/0, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout

Feb 20 08:53:22.567: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

Hall of Fame Super Gold

FXO port, hears 5 rings before the call is connected

Can you please the trace exactly as indicated above ?

1045
Views
0
Helpful
22
Replies
CreatePlease to create content