[cisco-voip] H.323 Gateway PRI selection
Linsemier, Matthew
MLinsemier at apcapital.com
Wed Jun 6 16:15:20 EDT 2007
I forgot to mention CSS but I was thinking along the same lines you
were. The only issue that you may run into if you want to drop PRI's is
calling name. It's really easy to send whatever number you want to
telco and have them send it on (haven't you ever accidently put in the
wrong number mask and your customers think your insurance company is
Bob's Truck Stop), but calling name is a different story. Good luck in
convincing them to add different entries based on the number you send
over one PRI even though I know feasibly it can be done in their
database.
Matt
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Wednesday, June 06, 2007 4:08 PM
To: CarlosOrtiz at bayviewfinancial.com
Cc: cisco-voip-bounces at puck.nether.net; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] H.323 Gateway PRI selection
Then I would follow Gurpinder's idea, but rather then letting the user
select, use calling search spaces so that the appropriate route pattern
was automatically selected.
Then, each route pattern could append a prefix that would match the
appropriate dial-peer.
I would consider removing call screening on the PRIs and leave it up to
the dial-peers to set the callerID. You might be able to drop the number
of PRIs you need.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo."
WJR
----- Original Message -----
From: CarlosOrtiz at bayviewfinancial.com
To: Lelio Fulgenzi <mailto:lelio at uoguelph.ca>
Cc: cisco-voip at puck.nether.net ;
cisco-voip-bounces at puck.nether.net
Sent: Wednesday, June 06, 2007 4:03 PM
Subject: Re: [cisco-voip] H.323 Gateway PRI selection
Basically I need 3 different groups of users always to use their
designated PRI's so that the correct caller ID is presented. Think of
it as 3 companies sharing one gateway, each desginated to a PRI with
that companies name and number on it.
In response to the Gurpinder's post....I do not need them to
select which caller id they want to use. Each of the 3 groups will
always use the same caller ID. I had an idea similar to yours to
prepend digits so that when the call gets to the gateway I know which
PRI it needs to exit from. I just want to make sure I don't miss an
easier method.
Carlos
"Lelio Fulgenzi" <lelio at uoguelph.ca>
Sent by: cisco-voip-bounces at puck.nether.net
06/06/2007 03:50 PM
To
<cisco-voip at puck.nether.net>, <CarlosOrtiz at bayviewfinancial.com>
cc
Subject
Re: [cisco-voip] H.323 Gateway PRI selection
Wouldn't you do this with the dial-peers?
There is a caller ID config statement that you can configure,
then select the appropriate port.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo
buffalo." WJR
----- Original Message -----
From: CarlosOrtiz at bayviewfinancial.com
To: cisco-voip at puck.nether.net
Sent: Wednesday, June 06, 2007 2:24 PM
Subject: [cisco-voip] H.323 Gateway PRI selection
We have a new H.323 Gateway that will have 4 PRI's. 2 PRI's
will be grouped together and present one caller ID. Each of the
remaining 2 PRI's will have their own caller ID (3 total different
Caller ID's). How can you select a specific PRI to be used so that the
correct caller ID is shown depending on which phone dials outboud? I
should be able to prepend a digit on Call Mgr to the 3 different route
patterns (different partitions) and then route the call based on the
leading digit found on the H.323 GW. I know I can do this via MGCP
easily as well. Any other good ideas or thoughts about this via H.323?
Carlos
________________________________
_______________________________________________
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
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20070606/9f071db7/attachment.html
More information about the cisco-voip
mailing list