I'm calling the fxs from an E1: in this case I hear nothing.

With internal phones I can hear ring tone correctly.

Tomorrow I'll test the call from other analog phones connected to the FXS module.

Thanks.

On debug isdn q931, you will see if the router is sending alerting; that should make the caller hear ringback. If it does but no ringback, one check with the telco should be done, but in case they can't help, there are workarounds.

Hello,

I've done some tests.

This is an External call that calls the fxo port:

###############################

Mar 29 11:59:43.218: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x4C00

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA18388

Preferred, Channel 8

Calling Party Number i = 0x0183, '335999999'

Plan:ISDN, Type:Unknown

Called Party Number i = 0xA1, '348999999'

Plan:ISDN, Type:National

Sending Complete

Mar 29 11:59:43.222: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x4A calltype 2 CALL_INCOMING

Mar 29 11:59:43.222: ISDN Se0/0/0:15 EVENT: call_incoming: call_id 0x004A, Guid = D0AE0F3C804B

Mar 29 11:59:43.234: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xCC00

Channel ID i = 0xA98388

Exclusive, Channel 8

Mar 29 11:59:43.238: ISDN Se0/0/0:15 Q931: TX -> PROGRESS pd = 8 callref = 0xCC00

Progress Ind i = 0x8188 - In-band info or appropriate now available

Mar 29 11:59:55.138: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x4C00

Cause i = 0x839F - Normal, unspecified

Progress Ind i = 0x8288 - In-band info or appropriate now available

###############################

it seems that the alerting is missing...

I've specified in the E1 (where the external calls arrive) "sending-alert", but nothig changed:

interface Serial0/0/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn overlap-receiving T302 2000

isdn incoming-voice voice

isdn send-alerting

isdn sending-complete

isdn outgoing display-ie

no cdp enable

!

In externals calls to Cisco phones or calls between FXS the ring tone is regularly instead.

Any idea?

Thanks a lot.

Hi Marco,

That is strange, config is correct but alerting is not sent. Which IOS is this? E.g., on an 12.4(4)XJ1 I have alerting correctly sent even if I didn't configure "isdn send-alerting":

Mar 29 12:56:51.439: ISDN Se0/2/0:15 Q931: RX <- SETUP pd = 8 callref = 0x1553

Sending Complete

Bearer Capability i = 0x8090A3

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98382

Exclusive, Channel 2

Progress Ind i = 0x8083 - Origination address is non-ISDN

Calling Party Number i = 0xA1, '06442****'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '64425****'

Plan:ISDN, Type:National

Mar 29 12:56:51.455: ISDN Se0/2/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x9553

Channel ID i = 0xA98382

Exclusive, Channel 2

Mar 29 12:56:51.471: ISDN Se0/2/0:15 Q931: TX -> ALERTING pd = 8 callref = 0x9553

Something you can try, but probably will not help, can you try to add a dollar sign "$" at the end of destination-pattern for the FXS ports ?

Hello,

Version 12.4(11)XJ

(c2800nm-spservicesk9-mz.124-11.XJ.bin)

Adding $ sign doesn't resolve the situation.

Can I ask you if it's normal this output?

voip#sh dspfarm

DSPFARM Configuration Information:

Admin State: DOWN, Oper Status: DOWN - Cause code: ADMIN_STATE_DOWN

Transcoding Sessions: 0(Avail: 0), Conferencing Sessions: 0 (Avail: 0)

Trans sessions for mixed-mode conf: 0 (Avail: 0), RTP Timeout: 600

Connection check interval 600 Codec G729 VAD: ENABLED

The other calls are working regularly...

Thanks.

I would go ahead and upgrade to XJ1 that is available on the ftp.cisco.com when logged with your CCO username and password.

I have the same installation/configuration and alerting is sent correctly for the FXS extensions. Only, I did not define any timer for "isdn overlap-receive".

The dspfarm show down because you haven't configured anything, this is normal.

Hello,

Thanks always for your precious advices.

I don't know how I have found this, but the command:

voice call send-alert

resolved my problem :)

" To enable the terminating gateway to send an alert message instead of a progress message after it receives a call setup message, use the voice call send-alert command in global configuration mode"

Marco.

This is good news Marco.

In fact the "isdn send-alerting" it an older command that may apply to data calls only.

The correct behavior by the router would be to send first call-progress to ack the setup, and then alerting when the destination is actually ringing.

Perhaps some bug in XJ(no 1) or an unseen configuration twist is causing the above to not happen in your installation.

Anyway as anyone that can fix his own problems your post got rated by me for that.