The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
kb8uas
New Contributor II

FXS port wont break dialtone

Jump to solution

Has anyone had an issue with 924 where the FXS port wont break dialtone when a user goes off-hook and begins dialing the call?....I see no "bad cabling" reset messages in event history on that port...

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
kb8uas
New Contributor II

Re: FXS port wont break dialtone

Jump to solution

I just did a shut no shut on the FXS port and it came back as a usable port.... nothing in the logs suggested a problem. Ie cable issue etc Sorry so late but I have been busy!

View solution in original post

0 Kudos
2 Replies
Anonymous
Not applicable

Re: FXS port wont break dialtone

Jump to solution

Hello John and thank you for posting to the forum.

Can you verify that the amphenol cable connectors are firmly seated on both the ADTRAN unit and the 66-block?  If the cabling is secure, we will need to look at a debug to determine if the ADTRAN is seeing the phone go offhook on that FXS port.  You can access the ADTRAN by a console connection, SSH, or Telnet - we want to be in the command line.

Once you are in enable mode, run these debugs together:

debug interface fxs

debug voice verbose

Now go offhook on the port you are working on.  We should see messages indicating that the phone/test set is on/off-hook.  Lets verify the ADTRAN is seeing the on/off-hook states and then we can go from there.  Also, feel free to attach your conifg but remove any sensitive information like IP addresses, passwords, etc.

Thanks,

Geoff

kb8uas
New Contributor II

Re: FXS port wont break dialtone

Jump to solution

I just did a shut no shut on the FXS port and it came back as a usable port.... nothing in the logs suggested a problem. Ie cable issue etc Sorry so late but I have been busy!

0 Kudos