|
Home > Archive > Voice over IP Cisco > April 2006 > Caller ID
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Ward Knutson 2006-04-24, 7:58 am |
| I recently changed my gateway from a H.323 with 1-T1 PRI to a MGCP with
2-T1 PRI's. The T1's are pooled and I am having trouble passing caller
ID information on outgoing calls. Before I was able to set the Caller
ID DN to 701355XXXX and it worked fine. Since I have two different set
of DID's tied to these T1's I can't use the same settings. I tried 10
X's and also tried to leave the Caller ID DN blank but then I get the
number that is associated to the T1 from the service provider. This it
how I have it set now.
Calling Line ID Presentation Allowed
Calling Party Selection Originator
Called party IE number type unknown cisco CallManager
Calling party IE number type unknown cisco CallManager
Called Numbering Plan Cisco
CallManager
Calling Numbering Plan Cisco
CallManager
Number if digits to strip 1
Caller ID DN
7013553000
SMDI Base Port 0
If you have any ideas they would be greatly appreciated.
Ward Knutson
Network Coordinator
Bismarck Public Schools
Bismarck, North Dakota
ward_knutson@educ8.org
701-355-3037 Office
701-527-4034 Cell
| |
| Justin Steinberg 2006-04-24, 7:58 am |
| What is your ISDN switch type?
On 4/21/06, Ward Knutson <ward_knutson@educ8.org> wrote:
>
> I recently changed my gateway from a H.323 with 1-T1 PRI to a MGCP with
> 2-T1 PRI's. The T1's are pooled and I am having trouble passing caller ID
> information on outgoing calls. Before I was able to set the Caller ID DNto
> 701355XXXX and it worked fine. Since I have two different set of DID's tied
> to these T1's I can't use the same settings. I tried 10 X's and also tried
> to leave the Caller ID DN blank but then I get the number that is associated
> to the T1 from the service provider. This it how I have it set now.
>
>
>
> Calling Line ID Presentation Allowed
>
> Calling Party Selection Originator
>
> Called party IE number type unknown cisco CallManager
>
> Calling party IE number type unknown cisco CallManager
>
> Called Numbering Plan Cisco
> CallManager
>
> Calling Numbering Plan Cisco
> CallManager
>
> Number if digits to strip 1
>
> Caller ID DN
> 7013553000
>
> SMDI Base Port 0
>
>
>
> If you have any ideas they would be greatly appreciated.
>
>
>
>
>
> Ward Knutson
>
> Network Coordinator
>
> Bismarck Public Schools
>
> Bismarck, North Dakota
>
> ward_knutson@educ8.org
>
> 701-355-3037 Office
>
> 701-527-4034 Cell
>
>
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
| |
| pnowicki@neo.rr.com 2006-04-24, 7:58 am |
| With this type of setup where you have 2 different ranges of DID (ex.
701355XXXX and 701250XXXX) like you said, you can not set the calling
number transformation to a pattern such as these. This is why the
external phone number mask on the DN pages of the phones are handy. You
can set those to what ever you would like (usually restricted to phone
numbers assigned to your PRI group by the carrier)..
Set these to 701355XXXX or what ever you like.. Then on your route
pattern, check the box for "use external phone number mask" in the
calling party transformation area. You do not need to set anything more
in the calling number modification fields...
If the carrier still sends out the billing number of the PRI's, instead
of the callerid that you specified, then I would suggest checking out
your numbering plan and Calling Party number type settings on the PRI
itself.. The "CallManager" setting basically says that you are using
the "9.@" route pattern with route filters and for the callmanager to
apply the number type/plan as recognizes number formats. If it does not
recognize it, or if you are not using the "9.@" route pattern, then, it
will send out an "unknown" setting to the carrier for these fields.
This is usually ok for most purposes, but I find that carriers are more
and more requiring the numbering type to be set appropriately. I would
suggest to set the "Calling party IE number type" to ISDN and
the "Calling Numbering Plan" to National if you are sending out a ten
digit phone number as the caller id...
Hope this helps...
-Patrick
----- Original Message -----
From: Ward Knutson <ward_knutson@educ8.org>
Date: Friday, April 21, 2006 10:41 am
Subject: [cisco-voip] Caller ID
To: cisco-voip@puck.nether.net
> I recently changed my gateway from a H.323 with 1-T1 PRI to a MGCP
> with2-T1 PRI's. The T1's are pooled and I am having trouble
> passing caller
> ID information on outgoing calls. Before I was able to set the Caller
> ID DN to 701355XXXX and it worked fine. Since I have two
> different set
> of DID's tied to these T1's I can't use the same settings. I
> tried 10
> X's and also tried to leave the Caller ID DN blank but then I get the
> number that is associated to the T1 from the service provider.
> This it
> how I have it set now.
>
>
>
> Calling Line ID Presentation Allowed
>
> Calling Party Selection
> Originator
> Called party IE number type unknown cisco CallManager
>
> Calling party IE number type unknown cisco CallManager
>
> Called Numbering Plan Cisco
> CallManager
>
> Calling Numbering Plan Cisco
> CallManager
>
> Number if digits to strip 1
>
> Caller ID DN
> 7013553000
>
> SMDI Base Port 0
>
>
>
> If you have any ideas they would be greatly appreciated.
>
>
>
>
>
> Ward Knutson
>
> Network Coordinator
>
> Bismarck Public Schools
>
> Bismarck, North Dakota
>
> ward_knutson@educ8.org
>
> 701-355-3037 Office
>
> 701-527-4034 Cell
>
>
>
>
>
>
|
|
|
|
|