DID to paging trunk

[pginhb]

I have a customer who is in the process of getting rid of the option 61 they have in the next year and they want to access the paging from another site via a DID. So far I have tried, acdn-ncfw to paging access code. Incoming digit conversion of DID to paging access code. Incoming digit conversion of DID to an in house extension then acdn of the in house extension ncfw to the paging trunk. Phantom tn dcfw to paging trunk, (works if dcfw is to my cell) Regular analog phone hard cfw to the paging access coed. DID sent to VM then built menu and sent #1 to call the paging access code. Every single thing just bounces the call to the operator. Some of the settings, net data has TRNX and EXTT set to yes, DID route has TARG 1, Page route has TARG 8 and 9 and is built as PAG, page trunk tn is built as PAG, LD 86 has TGAR set to no, page trunk has supervision, page route has PGNU in RDB, anybody see anything I'm missing? sounds like it could be some sort of trunk to trunk transfer problem. They used to have a tie line between them and that is how they used to page but it is gone and this is how they want to do it. Thanks

 

[GHTROUT]

I suggest changing the PAG route type to WAT or COT - or at least create a test route to try.

~~
Gene at GHTROUT.com

 

[KCFLHRC]

Get one of these

http://www.valcom.com/pdf/v-9940.pdf

and make your page access an analog DN with an associated DID.