[cisco-voip] off-net and on-net classification of route patterns and gateways

[Lelio Fulgenzi]

Thanks Peter. That one slipped my mind as well. I guess, for all intents and purposes, on-net is really when it's an enterprise system, regardless of how it gets from side to side. 

Would have to consider all of this when marking them on-net vs off-net. 

One thing I do recall, when connecting our PBX, is because we didn't have CDRs enabled on our PBX, is that we had to plug in the extension of the PBX phone into the equivalent external calling mask field, because this was what being marked in the CallManager CDRs. 

I suspect the on-net vs off-net affects how CDRs are cut as well and what number is shown to the called party. 

I'm going to test extension to extension dialing tomorrow to see how that plays through. 

I'm thinking more and more that everything should be marked as on-net, and then the off-campus calls are marked off-net when they finally get off. 



Lelio 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 

519‐824‐4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

----- Original Message -----

From: "Peter Slow" <peter.slow at gmail.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "Cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net> 
Sent: Tuesday, January 27, 2015 4:37:24 PM 
Subject: Re: [cisco-voip] off-net and on-net classification of route patterns and gateways 

I think it will also affect termination/Continuance of CUCM controlled 
conference calls. Users participating in a conference call over a 
trunk marked on-net will be able to keep a conference call alive with 
the service parameter set accordingly. (There's a confcall knob to 
modify when a call shoudl terminate, when the controller leaves or 
whathaveyou.) 

-Pete 

On Tue, Jan 27, 2015 at 4:03 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 
> This was my understanding as well. This is a strange one for me. 
> 
> I don't understand why this is happening. Especially the "To Private" part. 
> 
> I might try switching everything to on-net and see if that helps. 
> 
> --- 
> Lelio Fulgenzi, B.A. 
> Senior Analyst, Network Infrastructure 
> Computing and Communications Services (CCS) 
> University of Guelph 
> 
> 519‐824‐4120 Ext 56354 
> lelio at uoguelph.ca 
> www.uoguelph.ca/ccs 
> Room 037, Animal Science and Nutrition Building 
> Guelph, Ontario, N1G 2W1 
> 
> ________________________________ 
> From: "Brian Meade" <bmeade90 at vt.edu> 
> To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
> Cc: "Cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net> 
> Sent: Tuesday, January 27, 2015 3:20:05 PM 
> Subject: Re: [cisco-voip] off-net and on-net classification of route 
> patterns and gateways 
> 
> 
> Only things I know of it's used for is the different on-net/off-net ringing 
> behavior as well as being able to use the service parater od blocking 
> offnet-to-offnet transfers. 
> 
> On Tue, Jan 27, 2015 at 3:03 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote: 
>> 
>> 
>> Just wondering what exactly the call classification of off-net and on-net 
>> for route patterns and gateways does? I always thought it had more to do 
>> with ring type, i.e. single ring vs double ring. 
>> 
>> I'm trying out a scenario where I have a test gateway connected to a 
>> production gateway using a T1 crossover cable. It's not working out to well. 
>> I'm working with the TAC to figure out where things are going wrong, and I'm 
>> hoping it's not a bug since I had this working without issue in v7. We've 
>> since moved to v9. 
>> 
>> I had the two connected gateway ports configured as on-net and the route 
>> pattern which sent the calls across as off-net, and things would not work. 
>> We modified both gateway ports to off-net and things are working, but now 
>> the calls show "To Private". 
>> 
>> Very weird. 
>> 
>> In my scenario, I want to be able to send calls to extensions, not only 
>> PSTN numbers, so I'm thinking I should be marking all route patterns and the 
>> gateways as on-net. Then, the calls is marked as off-net when it leaves the 
>> phone system and hits the PSTN. I'm still hoping I can mark route patterns 
>> as "secondary dialtone" even if marked as on-net. 
>> 
>> So: 
>> 
>> phone -> route pattern -> test gateway o/b port -> T1 Xover <- production 
>> gateway A i/b port -> production gateway B o/b port -> PSTN 
>> 
>> Any thoughts? 
>> 
>> Note: The reason for this set up is so that I can test ACLs on the test 
>> gateway first, before applying to the production gateways. 
>> 
>> --- 
>> Lelio Fulgenzi, B.A. 
>> Senior Analyst, Network Infrastructure 
>> Computing and Communications Services (CCS) 
>> University of Guelph 
>> 
>> 519‐824‐4120 Ext 56354 
>> lelio at uoguelph.ca 
>> www.uoguelph.ca/ccs 
>> Room 037, Animal Science and Nutrition Building 
>> Guelph, Ontario, N1G 2W1 
>> 
>> 
>> _______________________________________________ 
>> 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 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150127/2902641b/attachment.html>