[cisco-voip] Partition Question

[Haas, Neal]

I ended up doing the additional partitions, everything works! Now I just need to test some……

Thanks

Neal Haas

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Friday, January 06, 2012 10:24 AM
To: Haas, Neal
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Partition Question

Then your choice is to duplicate your dial plan, i.e. all route patterns pointing to different gateways, contained in a different partition which your FAX lines have access to.

Or, as Matthew pointed out, you can use local route groups. It just means doubling up on your device pools.

Simplicity goes with additional route patterns and partitions, that stuff is pretty easy to sort out, but probably more time consuming. Local route groups is likely something new which will take a bit more work.

I guess it's six of one, half a dozen of the other.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)


________________________________
From: "Neal Haas" <nhaas at co.fresno.ca.us<mailto:nhaas at co.fresno.ca.us>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Friday, January 6, 2012 1:09:51 PM
Subject: RE: [cisco-voip] Partition Question


I forgot 1 thing, I want to keep the dialing the same 9.XXXXXXX. So they will dial the same on the phone or Fax. This would be for SIP and PRI calling, The end user cannot know that there is a difference.

Neal Haas
County of Fresno
Please report Troubles to the Help Desk. 559-600-5900
559-600-5890

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]<mailto:[mailto:lelio at uoguelph.ca]>
Sent: Friday, January 06, 2012 10:02 AM
To: Haas, Neal
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Partition Question

If you're trying to allow a particular set of phones access to SIP trunks, it's the CSS of that phone you have to change. That way, it has access to a set of route patterns that accesses those particular trunks.

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
                              - LFJ (with apologies to Mr. Popeil)
________________________________
From: "Neal Haas" <nhaas at co.fresno.ca.us<mailto:nhaas at co.fresno.ca.us>>
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Friday, January 6, 2012 12:53:15 PM
Subject: [cisco-voip] Partition Question

What is the best way to send calls out a particular set of trunks?

I have setup all of our VOIP phones on a Partition of “Internal” We want to route this out the SIP trunks, but I don’t want to route our faxes out the SIP trunk.

So I had in my mind to create a Partition of “FAX-ONLY” and I create new CSS so that the calls go out the PRI’s, it works, also calling to and from the internal and FAX-ONLY it works, but when I try to call the number it does not work. Busy signal, So I do some digging the PRI’s are on a CSS that was not included in FAX-ONLY so I add the CSS of 1020 trunk. Still does not work.

My coworker says that I did it wrong I only needed to change the device pool, to get the desired effect, I don’t think so.

What is the best way to make a fax use a particular PRI for calling out? I want to make it easy for the techs to work with.

Thanks

Neal Haas


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120106/9b660014/attachment.html>