Tie Trunk & Brooktrout Caller ID 1

[jrobs]

Hi all,

I've set up a fax server using a Brooktrout TR114+P8V-T1, which accepts a robbed but T1. I created the T1 by building a tie trunk using a TN767 DS1 card in my definity, and made the trunk group like Brooktrout's docs suggested. It works for inbound and outbound, but it's not sending the caller ID based on the user's DID number. Any call made from the fax server sends me the default did of my PRI which routes all outbound calls.
I've added the correct lines in the ISDN Public-unknown numbering for the prefix...but I think the tie trunk is dropping the DID.

Any ideas?

thanks,
josh

 

[1a22ip]

jrobs
I beleve that Tie Lines don't pass any CID data. Outbound from the Faxserver through the PBX onto the PSTN and transporting the PRI CID is correct. I question why this is a problem.

Thanks
Ed

1a2 to ip I seen it all

 

[jrobs]

OK so if doesn't pass data, then how do I get it to stop sending out the CID of the PRI? I'd rather it just sent nothing...

Thanks!
Josh

 

[1a22ip]

jrobs

You might have to talk to the carrier in order to block the PRI CID. But this will stop everyone from seing CID even your users.

Does Brooktrout have any comments on this?

Ed

1a2 to ip I seen it all

 

[pbxman]

I realize it's been a year since the last post, but i'm in the same boat with having default PRI caller ID being sent via the fax server. Is there an update on this? I tried brooktrout's site to no success, and with the new law in place that a business must provide a valid callback number, we're illegal. Calling back the number sent by the PRI gets "we're sorry, the number you have reached..." etc.

Any ideas?
Thanks

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[tc0nn]

Setup a destination for that main number your trunk is using.. !?! Seems too simple?

 

[dufus2506]

I'm not certain, but isn't the law that you have to send the phone number of the originating device, (not the DID of the sender) in fax messages?

It has to come through in that little margin line at the top of a fax, or as part of the cover sheet. It doesn't have to match in the caller ID data that would come through on a common CID box.

If you're broadcasting advertisements, you have to provide a phone number to remove the receiving fax machine from the broadcast list.


Carpe dialem! (Seize the line!)

 

[schned99]

Here is what you do:

1. Pick a number you want the faxes to send out as a return fax number.

2. change system-parameters-features On or about the 8th page you will see CPN/ANI/ICLID Replacement for restricted and unavailable calls. Populate both of these fields with your return fax number.

3. On your ISDN PRI outbound trunk group, on the second page, stroke replace restricted numbers amd replace unavailable numbers to yes.

You should be sending the correct return fax number now.

Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[pbxman]

schned99,

I tried what you posted and it still is sending out the ISDN PRI's default number. Am I missing something else? Currently, we have an order in to change the ISDN's CID to our number - though I'd like to cancel it if the switch can handle this task itself. This is only for local ISDN calls - outbound LD goes over AT&T Tie trunks where AT&T is sending the ID for us instead of the switch.

Thanks

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[BHodgins]

2. change system-parameters-features On or about the 8th page you will see CPN/ANI/ICLID Replacement for restricted and unavailable calls. Populate both of these fields with your return fax number.

On my system, the numbers are what I want them to be, but I noticed that I cannot change them. How did they get there in the first place? (Is a higher-level login needed?)

 

[schned99]

pbxman,

Some LECs over-ride what you send over the trunks and send all outgoing calls with the CPN number associated with the T1 account. There is a service (for a fee, of course) where the LEC will send what you send out via the PBX trunk (in either ISDN-public-unkown table or the CPN replacement field) whatever numbers you program.

BHodgins,

You should be able to make those changes with a "super-user" account. Your "cust" login should have all the permissions required to make this change.

Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[nohuhu]

pbxman,

i see three ways to solve your problem:
first, set up your fax server to provide correct ani. it should be passed out through pri circuit.
second, modify the ani you're receiving in the fax server trunk group, on the first page using fields "calling number - delete/insert/numbering format".
third, if you have cm2.1 and above, you can change ani for tandem calls using "change tandem" command.

 

[pbxman]

dwalin,
"first, set up your fax server to provide correct ani. it should be passed out through pri circuit"

- The fax server itself doesn't have any outbound ani settings. We're using Rightfax v 8.0 enterprise. On the outbound, ISDN Pub/Unk is used. All of our internal devices (including analog fax machines) use this table correctly and send out the correct CID - just not the tie Fax Trunk.

"second, modify the ani you're receiving in the fax server trunk group, on the first page using fields "calling number - delete/insert/numbering format".

- The fax trunk is setup as a tie line, not ISDN. I do not have these settings.

- Also, we dont have cm2.1 at all so the ch tandem isn't an option. :\


Here's the first page of the Fax Trunk setup:

display trunk-group 11 Page 1 of 11
TRUNK GROUP

Group Number: 11 Group Type: tie CDR Reports: y
Group Name: Fax Server COR: 6 TN: 1 TAC: 711
Direction: two-way Outgoing Display? y Trunk Signaling Type:
Dial Access? y Busy Threshold: 99 Night Service:
Queue Length: 0 Incoming Destination:
Comm Type: rbavd Auth Code? n
Trunk Flash? n
BCC: 0
TRUNK PARAMETERS
Trunk Type (in/out): wink/wink Incoming Rotary Timeout(sec): 5
Outgoing Dial Type: tone Incoming Dial Type: tone
Wink Timer(msec): 300 Disconnect Timing(msec): 500
Digit Treatment: Digits:
Sig Bit Inversion: none
Analog Loss Group: 9 Digital Loss Group: 13
Incoming Dial Tone? y
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0 Receive Answer Supervision? y




Here's the first and second page of the ISDN PRI:

display trunk-group 1 Page 1 of 10
TRUNK GROUP

Group Number: 1 Group Type: isdn CDR Reports: y
Group Name: ameritech isdn COR: 6 TN: 1 TAC: 701
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: cbc Auth Code? n TestCall ITC: rest
Usage Alloc? n Far End Test Line No:
TestCall BCC: 0 TestCall Service:
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: descend
Digital Loss Group: 13
Calling Number - Delete: Insert: Numbering Format: pub-unk
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
____________________________________________________________

******************PAGE TWO**********************************

display trunk-group 1 Page 2 of 10
TRUNK FEATURES
ACA Assignment? n Measured: both Wideband Support? n
Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: n Send Calling Number: y
Used for DCS? n
Suppress # Outpulsing? n Numbering Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y

Send UUI IE? y
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

US NI Delayed Calling Name Update? n

SBS? n Network (Japan) Needs Connect Before Disconnect? n


____________________________________________________________


Hopefully, that formatted correctly. So far, i've tried all suggestions for the PBX and this still isn't working. Again, I thought tie lines wont pass outbound CID whatsoever and that the phone company has to send it out. With the PRI sending out the proper ID for all other calls originating in our switch (with the exception of the T1 fax server), i'm wondering if in fact this is the case after all?

Thanks guys. Any more suggestions?

 

[nohuhu]

pbxman,

oops, i'm sorry. missed the part about tie trunk, thought you have isdn to the fax server. so, i think you're able to set up the calling digits in your fax software, right? try to set these digits to "ani_digits*dnis_digits*" and respectfully set the trunk "incoming tone (dtmf) ani" to "ani*dnis*". i think it should work.

 

[pbxman]

Thanks for the quick response, dwalin -

The fax software settings deal with inbound call treatment - nothing for outbound other than stamping a tti line at the top of every fax. Unfortunately, we can't do that due to limitations in our paperless imaging-system setup.
We do receive CID inbound at the fax server - though there's nothing for sending ID out. We have a range of 150 DID numbers that I strip the prefix off of, then pass the last 4 digits and use that at the routing code for our 150 user ID accounts. For example - if you send a fax to 321-555-3550, I pass 3550 to the fax server, and my fax box ID is 3550, so I receive that fax. If your fax machine can handlt the protocol, I will also receive your sending CID. If anybody from our office sends you a fax using Rightfax however, all you get is our ISDN PRI default number.

So really there are two issues/problems - maybe this might help find a different solution? This is what my overall goal is:

1) Each user *should ideally* be able to send you just their originating CID if we wanted to. I dont see why I couldn't pass 321-555-3550 directly from the fax server to your fax mahine?

2) We should *as a company* be able to send out one default number for all faxes originating from that fax server.

That is basically what I'm trying to figure out what I can do. I'd like to be able/know how to accomplish both, but in this situation, the second example is what needs to get accomplished somehow. I know SBC can take care of the CID, but I believe that would affect my ability to accomplish example 1 in the future, as well as negate any custom ISDN-Pub settings I make I believe.

Thanks for all the assistance - I really appreciate it.

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[portcity]

Look at your Fax Server options. Below is a snapshot of an Omtool Fax Server for "Cover Page Variables." I used this fax server several years ago and was able to accomplish success. We had a DID range from 2000 thru 2499. We added an additional DID range of 6000 through 6499 for personal faxes. Within Exchange we imported the 6XXX fax numbers. Each person had their own DID fax number so it was inmportant to send their specific DID fax number.

Exchange polled the fax server and corresponded the fax's to individual mailboxes.

Hope this helps

Omtool - Coverpage Variables

This is a list the cover page variables that you can use to customize your coverpages.

When you type the variable onto the coverpage, place it between two percent signs (%). Make sure that there is not a space between the percent sign and the variable. For example, %RECIP_NAME%. For more information about how to customize your coverpages, refer to the online help in the Fax Sr. Manager.

This file is a


Coverpage Variable Description
%CSI% Calling station ID
%COMMENT#% Comments (where # is a number 1 through 12, for each line of the comment text)
%PAGES% Number of pages in the fax without the coverpage
%CTOTAL% Number of pages in the fax including the coverpage
%RECIP_ADDRESS#% Recipient’s address (where # is a number 1 though 4, for each line of the address)
%RECIP_ASSISTANT% Recipient's assistant
%RECIP_BUSINESS_PHONE% Recipient's business phone number
%RECIP_BUSINESS2_PHONE% Recipient's second business phone number
%RECIP_CITY% Recipient's city
%RECIP_COMP% Recipient's company
%RECIP_COUNTRY% Recipient's country
%RECIP_DEPARTMENT% Recipient's department
%FAX% Recipient's fax number different from below?
%RECIP_FAX_PHONE% Recipient's fax phone number
%RECIP_HOME_PHONE% Recipient's home phone number
%RECIP_HOME2_PHONE% Recipient's second home phone number
%RECIP_INFO% Recipient's information
%RECIP_TITLE% Recipient's job title
%RECIP_MOBIL_PHONE% Recipient's mobile phone number
%RECIP_NAME% Recipient's name
%RECIP_OFFICE% Recipient's office name?
%RECIP_OTHER% Recipient's other information difference from plain info?
%RECIP_PAGER_PHONE% Recipient's pager phone number
%RECIP_STATE% Recipient's state in the US
%RECIP_ZIPCODE% Recipient's zip code
%REFERENCE% Reference field
%ADDRESS#% Sender's address (where # is a number 1 through 4, for each line of the address)
%SENDER% Sender's name
%E-MAIL% Sender's e-mail address
%DMY% Today's date
%DATE% Today's date and time
%TIME% Today's time
%OFFICE_PHONE% Office phone number
%OFFICE_FAX% Office fax phone number

 

[nohuhu]

pbxman,

i'm not yet clear on the first part of the problem, so let's concentrate on the second. and this is a classical case of "ani problems with tandem calls". now, you're saying your faxing software has no settings for outbound faxing. well, i think this means completely dumb software, because any faxing soft i've seen was able at least to set up a prefix for outside dialing. now, at least you can try to send a fax to some manually formatted number, like this "18005551234*18005554321*". i guess even the most dumb software should allow you to define a number to send a fax for? and then, when faxing soft will seize the trunk and dial this digit string out, definity will interpret it as "ani*dnis*" string, route the call according to dnis and use the first part of the string as ani, passing it out through pri. so you will get what you want, and if the faxing soft is not so dumb and can be at least configured to dial some prefix before the number (9 for outside access?), you can include this ani in the prefix and have your share of happiness.
though i think the ideal solution would be to change the faxing trunk to isdn. i'm not sure if this is available with your software.

 

[pbxman]

Thanks portcity - I should have stated that one of the limitations of out paperless system is that we can not send out cover sheets with our production faxes. It's a long-drawn-out process that works very well, but changing our documents is not an option. By the way - we can send out an ID on our faxes if we wanted to (the Rightfax Server is perfectly capable), but the way we need it to operate with out paperless system won't allow any additions to our database-generated & barcoded fax coversheet.

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[pbxman]

Here is a list trace of my TAC's.


Routing Over ISDN Using T1/Faxserver Fax
09:48:43 dial 915552588760
09:48:43 route-pattern 3 preference 1 cid 0x1fd
09:48:43 seize trunk-group 1 member 68 cid 0x1fd
09:48:43 Setup digits 155572588760
09:48:43 Calling Number & Name NO-CPNumber NO-CPName
09:48:43 Proceed trunk-group 1 member 68 cid 0x1fd
09:48:44 Alert trunk-group 1 member 68 cid 0x1fd

Routing Over ISDN using analog Fax
09:50:09 dial 915552588760
09:50:09 route-pattern 3 preference 1 cid 0x215
09:50:09 seize trunk-group 1 member 69 cid 0x215
09:50:09 Setup digits 915552588760
09:50:09 Calling Number & Name 5552584550 NO-CPName
09:50:09 Proceed trunk-group 1 member 69 cid 0x215
09:50:10 Alert trunk-group 1 member 69 cid 0x215


Dwalin - I think i'm starting to understand what you are saying. The fax server (Rightfax) is probably the most powerful out there. I'm sure there are ways to do whatever is necessary, but the way it's setup to dial works like this:

Prefix for all outbound faxes is w9 - meaning the T1 card wits for a wink, then dials 9 to get out. Then from there, it's just straight-passing to the ISDN trunk. So, the user dials 1+area+number, and the fax server passes what you see above. How can I make the switch think it's passing ani as well? I tried entering (in my fax software) 1234*15552588760...which is my internal DID to my phone (to see if 1234 would be passed from the fax server as the caller ID), and here's what I got:


10:35:04 Calling party trunk-group 11 member 19 cid 0x1e1
10:35:04 Calling Number & Name NO-CPNumber NO-CPName
10:35:04 tone-receiver 01B0203 cid 0x1e1
10:35:04 active trunk-group 11 member 19 cid 0x1e1
10:35:07 dial 91234*15
10:35:07 term trunk-group 2 cid 0x1e1
10:35:07 dial 91234*15552
10:35:07 route-pattern 4 preference 1 cid 0x1e1
10:35:07 seize trunk-group 2 member 91 cid 0x1e1
10:35:10 dial 91234*155525
10:35:10 outpulse done 234*155525
10:35:14 idle trunk-group 11 member 19 cid 0x1e1

Then i tried dialing 15552588760*1234 and the default PRI ID was again passed.
I changed all the trunk settings back to default - do I need to go back in and select trunk settings posted in this thread above as schned99 posted before? This is where I become lost.

pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.

 

[nohuhu]

pbxman,

first, don't forget to change the faxing trunk group settings. on the first page, you can set digit treatment for insertion and digits to "9", then you will not have to insert "9" as a prefix for ars access, definity will do it itself. next, on the second page set "incoming tone (dtmf) ani" to whatever format you want. i myself would prefer "*ani*dnis*", it's more readable, though dialing additional digit will consume some time. if you're sending out tons of faxes every day, it can matter. and then you can dial the digits in your format from faxing server. so the digit string will look like "*18005551234*18005554321*", where first number is ani, and second is a phone number of remote recipient. try it.