It is in fact required for some implementations of callerid name. It
comes on a facility message that arrives after the call is setup. It
also can come in a display IE in the call setup. It really depends on
which way they are sending it.
Matthew Fredrickson
On Apr 11, 2006, at 12:49 PM, C
On Mon, 2006-04-10 at 22:42 -0400, Andres wrote:
> Steven wrote:
> You heard wrong. We have multiple PRIs from XO and they DO NOT send
> caller name. We have discussed the issue with them on several
> ocassions. The sales people will say whatever they want, but the tech
> people who actually
No, I'm taking receiving CallerID name and *not* sending. and no on a
PRI wait should not be required for callerID to come in.
On 4/11/06, Jerry Jones <[EMAIL PROTECTED]> wrote:
> I CAN VERIFY via aa dozen PRI from XO that yes indeed provide
> incoming callerID on PRI. It arrives shortly after the
I CAN VERIFY via aa dozen PRI from XO that yes indeed provide
incoming callerID on PRI. It arrives shortly after the setup message.
Hence the wait(1) required to display it.
Now if you are referring to sending caller name across PSTN - that
does NOT work since the terminating switch will do a
On 4/10/06, Andres <[EMAIL PROTECTED]> wrote:
> Steven wrote:
>
> >I switched PRI vendors recently, and one of my questions was "do you provide
> >caller ID name in addition to number?"
> >AT&T Local did not, But XO communications said they did.
> >
> >
> You heard wrong. We have multiple PRIs fr
Steven wrote:
I switched PRI vendors recently, and one of my questions was "do you provide caller
ID name in addition to number?"
AT&T Local did not, But XO communications said they did.
You heard wrong. We have multiple PRIs from XO and they DO NOT send
caller name. We have discussed the
There is nothing you really need 'to do' if your PRI is working already,
If you are able to receive and make calls your D-Channel is functioning
properly. In the case of CallerID, some telcos provide this extra
function via the FACILITY messages instead of the SETUP messages, If
that is the case,
