[cisco-voip] Caller ID with Verizon
IT
it at cimgroup.com
Tue Mar 14 14:08:33 EST 2006
Justin!
You are exactly right!
Verizon just told me exactly the same thing as what you said (2 minutes
earlier), and it totally fixed the problem.
Thank you,
Avidan
-----Original Message-----
From: Justin Steinberg [mailto:jsteinberg at gmail.com]
Sent: Tuesday, March 14, 2006 11:00 AM
To: IT
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Caller ID with Verizon
Avidan,
I think your problem is that you're sending a '1' in front of the
called party number while your settings say 'National' and that isn't
making NI2 happy.
Changing to the settings below might fix your problem.
Called party IE number type unknown* set to National
Calling party IE number type unknown* set to National
Called Numbering Plan* set to Unknown
Calling Numbering Plan* set to ISDN
Justin
On 3/14/06, IT <it at cimgroup.com> wrote:
>
>
>
> Carlos,
>
> Thanks for the reply, I thought that as well, but I confirmed that
they have
> all the correct phone numbers in their "screening table". Does anyone
have a
> gateway with Verizon in the DC area who can verify my PRI
configuration?
>
> Thanks,
>
> Avidan
>
>
>
>
> ________________________________
>
>
> From: Ortiz, Carlos [mailto:CORTIZ at broward.org]
> Sent: Tuesday, March 14, 2006 5:49 AM
> To: Voll, Scott; IT; cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Caller ID with Verizon
>
>
>
>
> Down here in Florida this happens when Bellsouth only has the main
line in
> their "screening table". In other words, If they don't recognize the
called
> from number in their screening table they output the main line or
billing
> number. Could this be your issue?
>
>
>
> Carlos
>
>
> ________________________________
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
> Voll, Scott
> Sent: Tuesday, March 14, 2006 12:41 AM
> To: IT; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Caller ID with Verizon
>
>
>
>
> I don't know about Verizon in MD but in OR you have to pay a $200 to
setup
> the service and $75 a month to keep it.
>
>
>
>
>
> Scott
>
>
>
> ________________________________
>
>
> From: cisco-voip-bounces at puck.nether.net on behalf of IT
> Sent: Mon 3/13/2006 8:17 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Caller ID with Verizon
>
>
> I am dealing with issues on my PRI in Bethesda, MD with Verizon. I
have
> used the exact same configuration as with my gateways in California
> (with SBC/att), but I have the following problem. When I make any
calls
> through the gateway, I pass the caller-id information, but the called
> party gets the generic "main line" number for the office as the
calling
> party.
> For example, I have attached the output below of me calling my
cellphone
> through this PRI from extension 3581.
> Notice that the calling party is 3014693581, but I call my cellphone
and
> it appears as 3014693580.
> For reference, here is a link to a screen shot of my PRI config from
> CallManager.
> http://www.avidanross.com/pri_config.pdf
>
> Thanks,
> Avidan
>
> DEBUG ISDN Q931 OUTPUT
> -----------------------
> *Mar 13 21:57:20: Modify Nominator =
> *Mar 13 21:57:20: DTMF_TONE_DET
> *Mar 13 21:57:20: Modify Nominator =
> *Mar 13 21:57:20: FAX
> *Mar 13 21:57:20: CODEC_BYTES
> *Mar 13 21:57:20: NTE_PAYLOAD
> *Mar 13 21:57:20: DTMF_RELAY
> *Mar 13 21:57:20: NSE_PAYLOAD
> *Mar 13 21:57:20: SIGNAL_TYPE
> *Mar 13 21:57:20: FAX_BYTES
> *Mar 13 21:57:20: NTE_TX_PAYLOAD
> *Mar 13 21:57:20: SEQ_NUM_START
> *Mar 13 21:57:20: MP_CAP_MODEM_PROTO
> *Mar 13 21:57:20: MP_CAP_MODEM_CODEC
> *Mar 13 21:57:20: MP_CAP_VOICE_RTP_NSE_PAYLOAD
> *Mar 13 21:57:20: MR_INFO
> *Mar 13 21:57:20: IP_TONE_HANDLER
> *Mar 13 21:57:20: Modify Nominator =
> *Mar 13 21:57:20: FAX_TONE_DET
> *Mar 13 21:57:20: MODEM_TONE_DET
> *Mar 13 21:57:20: CM_TONE_DET
> *Mar 13 21:57:20: PER_CALL_DEBUG
> *Mar 13 21:57:20: ISDN Se0/2/0:23 Q931: TX -> SETUP pd = 8 callref =
> 0x0006
> Bearer Capability i = 0x8090A2
> Standard = CCITT
> Transfer Capability = Speech
> Transfer Mode = Circuit
> Transfer Rate = 64 kbit/s
> Channel ID i = 0xA98397
> Exclusive, Channel 23
> Calling Party Number i = 0x2881, '3014693581'
> Plan:National, Type:National
> Called Party Number i = 0xA1, '13239439922'
> Plan:ISDN, Type:National
> *Mar 13 21:57:20: ISDN Se0/2/0:23 Q931: RX <- CALL_PROC pd = 8
callref
> = 0x8006
>
> Channel ID i = 0xA98397
> Exclusive, Channel 23
> *Mar 13 21:57:20: Modify Nominator =
> *Mar 13 21:57:20: DTMF_TONE_DET
> *Mar 13 21:57:20: FAX_TONE_DET
> *Mar 13 21:57:20: Modify Nominator =
> *Mar 13 21:57:20: DTMF_TONE_DET
> *Mar 13 21:57:20: FAX_TONE_DET
> *Mar 13 21:57:25: ISDN Se0/2/0:23 Q931: RX <- PROGRESS pd = 8 callref
=
> 0x8006
> Progress Ind i = 0x8488 - In-band info or appropriate now
> available
> *Mar 13 21:57:26: ISDN Se0/2/0:23 Q931: RX <- ALERTING pd = 8 callref
=
> 0x8006
> *Mar 13 21:57:27: Modify Nominator =
> *Mar 13 21:57:27: DTMF_TONE_DET
> *Mar 13 21:57:27: Modify Nominator =
> *Mar 13 21:57:27: DTMF_TONE_DET
> *Mar 13 21:57:27: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8
callref
> = 0x000
> 6
> Cause i = 0x8090 - Normal call clearing
> *Mar 13 21:57:27: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8 callref
=
> 0x8006
> *Mar 13 21:57:27: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8
> callref = 0x0
> 006
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
More information about the cisco-voip
mailing list