Recherche dans le site/ Search this Blog:


Blogue OC9 Bienvenue ! - OC9 Blog Welcome !
Problems dialing prefix *67 (anonymous call) on SPA-3102 and Asterisk Imprimer

We allow some peers to place local calls through a PSTN line that is hooked to a SPA-3102. It is impossible to set the callerID on outgoing PSTN calls, in most cases, you are stuck with the callerID assigned to you by your PSTN line provider. In this situation, we want to blank out the callerID by prefixing the number with *67 (anonymous call code) before dialing on the PSTN line.

When prefixing with *67, we had 50% of our calls not completing because of eaten digits.

The following solved the problem, now 100% of our calls prefixed with *67 complete properly.

In the SPA-3102 web interface, admin login, advanced option, in PSTN Line :

PSTN Dialing Delay: 1

PSTN Dial Digit Len: .2/.1


Mis à jour / Last updated ( mardi, 02 octobre 2007 04:21 )
DTMF (dialing digits) and IVR problems in Asterisk with SPA-3102 and PAP-2 devices Imprimer

We had calls going through SPA-3102 and PAP-2 devices where the user couldn't get his dialed digits recognized by both our IVR or other external IVRs. Obviously, this occured both on incoming and outgoing calls. The following changes solved our problems;

Mis à jour / Last updated ( samedi, 15 décembre 2007 20:05 )
Lire la suite /
Caller name lookup script for Asterisk 1.4 and FreePBX 2.3.0 Imprimer

Here is a little script that allows you to look up for the caller name based on the caller phone number. It is pretty basic and works with parsing the HTML returned by 14990/search/ReversePhone?phone=${NUMBER} and falls back on search/?src=&stype=re&pac=${NUMBER:0:3}...

Mis à jour / Last updated ( mardi, 18 décembre 2007 19:42 )
Lire la suite /
Custom Context works fine in FreePBX 2.3.0 Imprimer

I have just tested the Custom Context module on my FreePBX 2.3.0 and Asterisk 1.4 testbed and it works fine.

If you look at the FreePBX site, they say that Custom Contexts are in realty Dial Contexts and that they will be implemented as such in FreePBX 2.3. I even read that Custom Contexts would not work at all in FreePBX 2.3

Well, no traces of Dial Contexts in FreePBX 2.3.0 and Custom Contexts just work fine. Did I miss anything ? if so write to me.

Mis à jour / Last updated ( mardi, 02 octobre 2007 04:23 )
Important thing to look at if you get one way audio problem with Asterisk 1.4.10 and FreePBX 2.3.0 Imprimer

We've had a weird problem where we though that there must be gremlins in the network or providers playing tricks on us. We've tried everything, reviewing our firewall rules, inserting log statements in our firewall rules, running tcpdump, analyzing STUN server traffic, everything !!

Mis à jour / Last updated ( mercredi, 26 mars 2008 23:53 )
Lire la suite /
Bug in FreePBX that prevent PhoneBook to say number Imprimer

There is a funny bug in FreePBX that prevents the PhoneBook application to "say numbers", meaning you can't hear the numbers if there are any in the PhoneBook name of the entry. As an example, for "OC9 Technologies", the PhoneBook application will only say "OC", bypassing the 9. This bug has been there for ever and it is still there in 2.3.0 :

in 2.3.0 in agi-bin/pbdirectory, line 222 :

} else if (('1' <= $string[$i]) && ($string[$i] <= '0')) {

should be replaced with :

} else if (('0' <= $string[$i]) && ($string[$i] <= '9')) {

Mis à jour / Last updated ( mardi, 02 octobre 2007 04:23 )
« Début/StartPréc/Previous111213Suivant/NextFin/End »

Page 13 de 13

Consultez TOUS nos fils d'actualité ici. / View ALL our newsfeed here.