LOC/HLOC Routing Question

[picklemogg]

Howdy- Any suggestions/thoughts on this would be greatly appreciated. We are in the process of networking Symposium servers to enable call queing to remote SCCS agents. So my question is basically what is the best way to set up the routing between sites to make this happen. In SCCS you program dialable DN to remote site which equals target sites network CDN which is straight forward. My thought is to route to target sites using LOC codes. So the dialable DN to a target site would be AC+LOC+NetCDN. In cases we will route SCCS calls from site A to site C going through site B. So site B would act like a tandem in this case I guess.
So- A call is routed from site A to B intended to term at B (B LOC dialed from A). Once the call arrives at B, LD 90 sees that the call was dialed with Bs HLOC code, so strip off HLOC digits and term locally. In the event A sends a call to B and ld 90 sees LOC for site C was dialed from A, site B passes call out an RLI to site C. C looks at ld 90 and realizes dialed digits was it's HLOC and strips off HLOC and terminates locally.
That ends question for part 1........

If we end up rotuing calls this way, when calls arrive at a site how do you insert AC to have call look at HLOC/LOC in ld 90. Do you first add AC digits prior to sending the call across the tie or is there a better way?
That ends question for part 2........

Just a general question. If HLOC/LOC codes to not interfere with any other programming in ld 90 (NXX, SPN, etc.) is there a reason to setup AC2 or could we keep using AC1 (9) like we do today? Someone was talking to us about adding AC2 for HLOC/LOC versus using AC1. I can't understand why, but very well could be missing something.
Ends part 3.......

One more general question. CDP versus UDP. We use CDP today so I'm pretty much all over that. I understand what UDP acronym stands for, but what does UDP really mean in terms of programming/routing. Is it the fact you are using LOC codes?
Ends part 4 and post.....

I apologize for the long post. Sorry. Any input would be most welcome. Thanks much.

 

[johnpoole]

couple of things i approach a little diff.. one is by using 5 or more digits is needed all stations have a unique dn.. even if that is not possible i use the remote sites nxx.. no area code... so if the far end is 222 333 1000, i would push all the 333 digits as a dsc, use dgt to del 3 and just send the 1000 to the tie.. if there is a tandem between use, say same set up diff pri.. make it entry 2, because the far end is not the final dest, leave the 333, far end switch sees the 333, if that switch it see 333 as a dsc and puts it on a tie that does hit the target, it strips the 333.. i strip and/or insert digits in the switch the number was dialed... if switch a is east coast, switch b is 213 area code.. in switch a dial 91 213 plus 7.. i would insert the 9 and put it on the tie to switch b.. b treats that the same as it would a single line station.. the 9 sends it to ld 90 and 90 sends it to ld 86, that rld/dgt/frl/route is handled via the far end rules..


you can do the same thing using 9 1 plus 10, strip the 1 npa nxx and just put send the did, if it is passing through that switch, insert the 9 and send it down the pipe.. if that tandem sends it to ld 90 and handles it as if it were dialed local... try to stay away from idc's, there great if needed.. let the originating switch send just the digits the next step needs...

john poole
bellsouth business
columbia,sc

 

[johnpoole]

think of it this way, in any switch dial 1 213 xxx 1234, i strip the 1 and send it to my ld carrier, my ld carrier does not need the one, because i sent it to them they know it's ld.. they look at the 213 only, they put it on a pipe to the downtown LA office but they strip the 213 and just send the xxx 1234, for the same reason.. sending them the call means it's for that area code.. they see the xxx and send it to that local office, stripping the xxx... 4 digits just like my dids.... this was 100 percent true 10 years age, because of number mobility, and offices with more then one area code, it;s a little more complex but one thing holds true... send the fewest numbers you can, but send all the digits that are needed for routing... and my answer is longer then your question

john poole
bellsouth business
columbia,sc

 

[picklemogg]

John- Thanks for the reply. Hey- it only makes sense that a long question deserves a long answer. Definitely makes sense to send fewest amount of digits, but still get the job done.

In your first example with 333 setup as a dsc... I understand your point, but let's say that you couldn't use 333 as a dsc. As in 3s were already being used somewhere else. Short of cleaning up to be able to use 333, what would your approach be? I was actually going to program LOC codes to match target site nxx. So if you programmed 333 as a LOC code, strip 3 dgts, and send remaining 4 dgts across the tie this should do the trick as well?
If I had another PBX with LOC (nxx) 444 and I was trying to send a call to it through PBX 333, I could send 9 (or AC)444XXXX. PBX 333 would see it was a LOC code and strip 444 and send XXXX on its way to the dest site?

Thanks again.
Todd

 

[johnpoole]

sure if you can't free up the distant nxx then use it as a nxx or spn.. a dsc is not reached after ac1 or ac2.. so if i wanted the local to dial 9 444 i would put 444 in as a nxx. if that conflicts with a local nxx then you'll need to find one that is not a conflict or back up to 10 digits which is worse.. any of the ld 87 prompts are not used post ac... 9 takes you to load 90.. a steering code has to be in the vacant dn table... i have see use of ac2 IF you want to burn a two digit number say 81, then make site a 810, plus the dn... not the best choice, buring 100 dn's but it's an option

john poole
bellsouth business
columbia,sc