Dialling out

[cornepiek]

Hi Guys,
I have a little problem every now and then.
I've got local authentication on any fxo call, vhen i dial out, the system keeps telling me my login is incorrect, at the same time, when i get it to accept the login, i just get a long engage tone as if the line is unavailable.
when i reset the system is tells me that the number i dialled is incorrect.

i ran the FXO diagnostics, and every tome it tells me to activate "cutom fxo data" in the "fxocfg.cgi" Page and update the "Fxo Csrs" settings.
the number it gives me to update with keeps changing.

[davrays]

Seems I have a lot of questions on what you have written below

Originally Posted by cornepiek

Hi Guys,
I have a little problem every now and then.
I've got local authentication on any fxo call, vhen i dial out, the system keeps telling me my login is incorrect,

If you dial incorrect extension/password, this is natural. Doyou use "Authentication by login", and are you dialing the same username/password, as configured in local AAA settings?

Originally Posted by cornepiek

at the same time, when i get it to accept the login, i just get a long engage tone as if the line is unavailable.

How do you get it to accept the login? Just dial correct username/password or some another way? How this long engage tone sounds like? If the line if anavailable, you should listen "Please check your PSTN line" message.

Originally Posted by cornepiek

when i reset the system is tells me that the number i dialled is incorrect.

You mean you power-cycle the unit, and it starts to tell that the number is incorrect?
Can you show a snapshot from your routing table?

All this sounds too strange. Can you please enable developer logging, make the experiment, and paste here the "Call Controlling" logs, so we can see what happened there?

Originally Posted by cornepiek

i ran the FXO diagnostics, and every tome it tells me to activate "cutom fxo data" in the "fxocfg.cgi" Page and update the "Fxo Csrs" settings.
the number it gives me to update with keeps changing.

If you have done that once, you don't need to update it again. Most probably your PSTN line is not very stable, and each time the diagnoistics tool gives slightly different results. But it should work with any of those settings.

[cornepiek]

If you dial incorrect extension/password, this is natural. Doyou use "Authentication by login", and are you dialing the same username/password, as configured in local AAA settings?

here i dial the correct username and password, username: 231 Password:1234
the username is the same as my extension number, and the password is, well, duh.
even if i dial very slowly, making sure i don't double punch a number, i still have to try 3, 4 times to get through. all our exts are barred the same way, everyone has the same problem at the same time.


How do you get it to accept the login? Just dial correct username/password or some another way? How this long engage tone sounds like? If the line if anavailable, you should listen "Please check your PSTN line" message.

try retry and try again. it will allow the username and password once in every 5 tries. i get the engage tone on the one ext that is not barred as well. the tone is not normal tone -0.5 sec tone , 0.5 sec pause-
the tone generated is like -1 sec tone, 0.5 sec pause-(usually referred to NU tone)


You mean you power-cycle the unit, and it starts to tell that the number is incorrect?
Can you show a snapshot from your routing table?

All this sounds too strange. Can you please enable developer logging, make the experiment, and paste here the "Call Controlling" logs, so we can see what happened there?

where do i activate "developer logging

[KSComs]

This sure sounds like a DTMF problem .. is there a setting in the handset for Inband / Out of band / RFC / Auto ?

Maybe the answer is the setting for the DTMF in the telephone .. when you uncheck the setting does the DTMF pass alright then or do you have problems in dialling still ?

Regards

Kevin

[cornepiek]

i'm having the login problem mostly on the snom phones.
the "NU" tone i get on the Snom phones and FXS phones

[davrays]

It looks like your Snom phone is using something different than PCMU/PCMA to call, and probably you have "Out of Band DTMF Transport" disabled either on te extensions or on the phone. So your DTMF digits are distrorted, and so not recognized by the Quadro.

You can try enabling the PCMU or PCMA both on the phone and the Quadro, to see if this solves the problem.

Regarding the "NU" tone... - I don't remember such tone in the Quadro.. Most probably this tone is generated by telco.

Developer logs can be enabled from System -> Diagnostics -> Show System Logs -> System Logs Settings page. The Call Controling log can be taken from the page nearby.

[cornepiek]

i had the "Out of Band DTMF Transport" disabled due to the fact that when i tranfer a call from an FXS ext, there is a loud clicking sound when i press the flash button.
i also tried different codecs, the "Out of Band DTMF Transport" setting seemed to have solved this but caused other problems it seemed

[davrays]

Typically "Out of Band DTMF Transport" should not create problems. I don't think that disabliing that you can avoid clicking sound from the flash button on the FXS phone ("flash" is not a DTMF, and though it can be transmitted by the same protocol, Quadro does not support that , and does not transmit "flash"). "Flash" is jsut a short ON/OFF hook switch, and a click can be produced only by the phone hardware (cheap assembly, for example . This click should be very phone-dependant.

If you don't want to enable "Out of Band DTMF Transport", you have to disable all codecs except PCMU/PCMA on the extensions. Only those two lossless codecs can ensure the inband DTMF paases through without distortion.