PDA

View Full Version : Caller ID options on FXS ports



johnq
06-29-09, 11:26 AM
The comments in /etc/pika/pikagp_aoh.cfg mention several protocols for "calleridmode" on the FXO/trunk channels, but only fsk_bellcore on the FXS/Phone channels. The utility pikacf set the mode for both to fsk_bt when the country code was set to GB, but the phone connected to my FXS port only shows the CLI if I manually edit pikagp_aoh.cfg and change the calleridmode to fsk_bellcore. Some clarification would be useful.

I am trying to test FXO CLI detection using a second Pika Warp to generate test calls. i.e. FXS port on Warp 1 connects to FXO port on Warp 2. fsk_bt detection on FXO trunks is probably the one I will need in the UK, but perhaps my test method is unsuitable. Please confirm.

skar
07-20-09, 04:52 PM
This test method will not work. The FXO lines on the WARP do not generate an outgoing FSK signal for Caller ID. The telco is what provides this feature to the far end of the call.

johnq
07-30-09, 05:52 AM
I think you have misunderstood - No attempt is being made to send outgoing FSK signals on the FXO lines. My telco line does not currently send caller ID so I was trying to mimic a telco line that does send it using an FXS port on a second Pika Warp device. However, that part of the question is no longer important.

What is more important now is to establish what are the permitted values for the calleridmode parameter for FXS/Phone channels? If only one value (fsk_bellcore) is permitted, why does the pikacf program write other values into the pikagp_aoh.cfg file?

skar
11-09-09, 10:01 AM
Hi johnq,

We have recently solved several issues with detecting caller ID on UK lines in the latest 2.0.9.2 release of software. Have you tried this software yet to see if it resolves your issues?

Skar (https://twitter.com/skar_pikawarp)

mrecoskie
01-14-10, 10:13 AM
Hi johnq.

Today the Pika driver is only capable of sending 'fsk_bellcore' out of their FXS lines. From my understanding, timings are too tight for other fsk variants to be reliably supported under the current architecture. So as you point out, it is obviously misleading that pikacf sets the fsk caller id to something other than 'fsk_bellcore'.

As for the test scenario you describe of taking fxs lines from one Warp and attaching them to fxo lines of another Warp is perfectly fine. In fact you could even loop fxs to fxo on the same Warp if desired.

damjankresal
01-29-10, 06:33 AM
Hi!

How to change the ID for outgoing calls from analog pika ports (PIKA/FXS/1-9 if present)? Do I have to copy the whole column where channels are 1-9 for each channel separately? I this the solution? How to make it automatically? Configured from FreePBX?

Second question. The problem is with BLF statuses. The status of pika analog FXS are not sent to SIP phones. For other siop phones works normally (The sip invite with status change is sent). I monitored on asterisk console and I see the change that channel status is changed. Why not send to the phone... The phone subscribes to asterisk for the extension....


Best regards!

Damjan

damjankresal
01-29-10, 06:37 AM
Hi!

Another problem which I noticed. When leaving voicemail to the subscriber (extension) on analog pika port (PIKA/FXS/x) the MWI FSK message is not sent to the phone. Is it possible to ****ch the feature on somehow? How to enable FSK MWI for FXS's. MWI message works normally with sip phones and TA's (Grandstream, Audiocodes, etc...) In sip it is a standard message and asterisk hands them well.

Best regards!

Damjan

mrecoskie
02-03-10, 11:08 AM
Hi Damjan,

Yes, I believe the only way to accomodate individual caller id for fxs ports is to separate their configurations. Here are some reference links for that. http://forum.pikatechnologies.com/faq.php?faq=troubleshooting#faq_callerid_fxs or also http://forum.pikatechnologies.com/showthread.php?412 Unfortunately I don't believe this can be done automatically (unless you pre-determine the extension numbers) nor does FreePBX supports this in its GUI.

In regards to the BLF, I assume you have successfully registered 'hints' with asterisk for both the fxs and sip technologies. Could you post some relevant portions of your configuration? What would be most interesting to see would be the hint registeration in your dialplan but also the output of 'sip show subscriptions' as well as 'core show hints' to determine the watchers to your SIP phones.

Finally, I don't think FSK MWI is supported on Warp for fxs phones. It requires ADSI support which is provided by Asterisk but I believe would also require the Pika channel driver to make request to this module to send pre-call messages.

skar
02-04-10, 11:06 AM
The issue with BLF on SIP phones has been resolved for some of our customers by adding the Asterisk func_devstate patch for 1.4. The reason this is needed is described on FreePBX forums here (http://www.freepbx.org/forum/freepbx/users/func-devstate-in-freepbx-2-5-x).

The fix of using func_devstate is detailed here (http://www.freepbx.org/forum/freepbx/users/func-devstate-in-freepbx-2-5-x#comment-12734) as part of that post.

We have integrated this fix in the latest release of FreePBX on PADS that can be retrieved here (http://pikawarp.org/?p=539).

Hope this helps,
Skar (http://twitter.com/skar_pikawarp)