hunt group for right fax on pri

[rejackson]

I can configure the pri but I am stuck on a hunt group.

I cant figure out how to associate the trunk to the hunt group. Do I have to create an ext for each pri channel or is it something in the meesage center and/or lwc reception fields? (mine are none). if I need the extensions how do I assciated them to the trunk? Trunk call handling might work for outbound faxes but what about inbound?

 

[Toni269]

You need a lot of help it sound but here are a few places to start:

Add the port numbers of the DS1 card(s) connected to the trunk into your trunk group form:

change trunk-group X
TRUNK GROUP
Administered Members (min/max): 1/46
GROUP MEMBER ASSIGNMENTS Total Administered Members: 46

Port Code Sfx Name Night Sig Grp
1: 01A1201 TN464 H 1
2: 01A1202 TN464 H 1
3: 01A1203 TN464 H 1
4: 01A1204 TN464 H 1
5: 01A1205 TN464 H 1
6: 01A1206 TN464 H 1
7: 01A1207 TN464 H 1
8: 01A1208 TN464 H 1
9: 01A1209 TN464 H 1
10: 01A1210 TN464 H 1
11: 01A1211 TN464 H 1
12: 01A1212 TN464 H 1
13: 01A1213 TN464 H 1
14: 01A1214 TN464 H 1
15: 01A1215 TN464 H 1

Then ensure that the DID range the Telco gave you is in your dialplan as "ext" with the correct number of digits.

change dialplan analysis Page 1 of 12
DIAL PLAN ANALYSIS TABLE
Percent Full: 2

Dialed Total Call Dialed Total Call Dialed Total Call
String Length Type String Length Type String Length Type
0 1 attd
1 2 fac
14 4 dac
21 4 ext
22 4 ext
25 4 ext
26 4 ext
6 4 ext
67 4 ext
69 4 ext
7 4 ext
8 4 ext
9 1 fac
* 2 fac
# 2 fac


Then you can create extensions and enter them onto your hunt group form. If you want to direct dial a hunt group you use a DID number for the lead then you can use non-DID numbers for all of the hunt group members if you want.

 

[sjforcum]

Is the only thing the PRI is used for is incoming faxing? (Doubtfull).

Normally we assign a DID number as someone's fax. You then setup a virtual extension to route to the fax hunt group as a coverage point.

 

[rejackson]

Thanks for the responses but I figured it out. It doesn't use a trunk or a hunt group. It uses a pri end-point. One end point with a width of 23 channgels and one extension. I pointed a did to that extension and faxes are working both ways now.

 

[rejackson]

Well they are not getting caller id so I have to back off of my thinking that it is working now.

However the two posts that I got seemed to miss the point. This is not an outside PRI, it is a PRI to the brooktrout card. Calls come in the outside PRIs and need to be directed to the PRI for the fax server. Brooktrout/Cantera give lots of documentation on how to configure the PRI including a trunk. But their sample doesn't show any call handling treatment in the trunk. I can't create stations to put in a hunt group because the trunk has the ports assigned and I can't see how to assign a trunk group to a hunt group. To summarize I cannot see how to route calls to the faxserver PRI.

 

[Toni269]

I have the same brooktrout cards for fax and I don't run them through the PBX there is no point in running it through the PBX at my site because the PRI's are dedicated to fax service.

If you're running an internal connection to the brootrout cards then you'll need to create a trunk group and signalling group, connect a DS1 card from the PBX to the Brooktrout server and modify your UDP table. I think your brooktrout software will manage the hunt group as I don't think you need a hunt group or extensions in the PBX for this scenario.

 

[Zen216]

I currently have a pri setup between the pbx and the rightfax server...

this is my trunk group form..

display trunk-group 4 Page 1 of 22
TRUNK GROUP

Group Number: 4 Group Type: tie CDR Reports: y
Group Name: RightFax COR: 5 TN: 1 TAC: 856
Direction: two-way Outgoing Display? n Trunk Signaling Type:
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0 Incoming Destination:
Comm Type: rbavd Auth Code? n
Trunk Flash? n
BCC: 0
Trunk Type (in/out): wink/wink
Group Type: tie Trunk Type: wink/wink

TRUNK PARAMETERS
Incoming Rotary Timeout(sec): 5
Outgoing Dial Type: tone Incoming Dial Type: tone
Wink Timer(msec): 300 Disconnect Timing(msec): 500
Digit Treatment: insertion Digits: 9
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
TRUNK FEATURES
ACA Assignment? n Measured: both
Internal Alert? n Maintenance Tests? y
Data Restriction? n
Glare Handling: none
Used for DCS? n
Suppress # Outpulsing? n
Seize When Maintenance Busy: neither-end




Incoming Tone (DTMF) ANI: no Per Call CPN Blocking Code:
Connected to CO? n Per Call CPN Unblocking Code:

Ds1 Echo Cancellation? n
ADMINISTRABLE TIMERS

Incoming Disconnect(msec): 500 Outgoing Disconnect(msec): 500
Incoming Dial Guard(msec): 70 Outgoing Dial Guard(msec): 1600
Incoming Glare Guard(msec): 1500 Outgoing Glare Guard(msec): 1500



Outgoing Seizure Response(sec): 5
Programmed Dial Pause(msec): 1500 Disconnect Signal Error(sec): 240
Flash Length(msec): 540 Incoming Incomplete Dial Alarm(sec): 255





END TO END SIGNALING
Tone(msec): 350 Pause(msec): 150

OUTPULSING INFORMATION
PPS: 10 Make(msec): 40 Break(msec): 60
ATMS THRESHOLDS
TTL Type: 105-w-rl Far End Test No:
TTL Vendor: TTL Contact:
Trunk Vendor: Trunk Contact:
Trunk Length:
MARGINAL UNACCEPTABLE
Min Max Min Max
1004 Hz Loss: -2 21 -2 21

-Dev +Dev -Dev +Dev
404 Hz Loss: 9 9 9 9
2804 Hz Loss: 9 9 9 9

Maximum C Message Noise: 55 55
Maximum C Notched Noise: 74 74
Minimum SRL-HI: 0 0
Minimum SRL-LO: 0 0
Minimum ERL: 0 0

Allow ATMS Busyout, Error Logging and Alarming? n

now one of the stations...
STATION

Extension: 5324 Lock Messages? n BCC: 0
Type: 2500 Security Code: TN: 1
Port: 01B0301 Coverage Path 1: COR: 5
Name: Fax Server 1 Coverage Path 2: COS: 1
Hunt-to Station: Tests? y

STATION OPTIONS
Loss Group: 1 Message Waiting Indicator: none
Off Premises Station? n



Survivable COR: internal
Survivable Trunk Dest? y
Remote Office Phone? n
STATION
FEATURE OPTIONS
LWC Reception: spe
LWC Activation? y Coverage Msg Retrieval? y
LWC Log External Calls? n Auto Answer: none
CDR Privacy? n Data Restriction? n
Redirect Notification? y Call Waiting Indication: y
Per Button Ring Control? n Att. Call Waiting Indication: y
Bridged Call Alerting? n Distinctive Audible Alert? y
Switchhook Flash? y Adjunct Supervision? y
Ignore Rotary Digits? n
H.320 Conversion? n Per Station CPN - Send Calling Number? y
Service Link Mode: as-needed
Multimedia Mode: basic Audible Message Waiting? n
MWI Served User Type: qsig-mwi

Coverage After Forwarding? s
Multimedia Early Answer? n
Direct IP-IP Audio Connections? y
Emergency Location Ext: 5324 IP Audio Hairpinning? y

We have two main fax lines going to the rightfax server... last 4 digits are 1101 and 1102...
here is a copy of my uniform dial plan

UNIFORM DIAL PLAN TABLE
Percent Full: 0

Matching Insert Node Matching Insert Node
Pattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num
1101 4 0 333 aar n n
1102 4 0 333 aar n n
n n

now my aar analysis
AAR DIGIT ANALYSIS TABLE
Percent Full: 2

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
223 7 7 p16 aar 3 n
224 7 7 p17 aar 4 n
3 7 7 p14 aar n
333 7 7 23 aar n
4 7 7 p14 aar n

and finally route pattern 23
Pattern Number: 23 Pattern Name: RightFax
SCCAN? n Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 4 0 3 n user
2: n user
3: n user
4: n user
5: n user
6: n user

BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 3 4 W Request Dgts Format
Subaddress
1: y y y y y n n rest none
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none


so call comes in,, the udp adds 333 to the 4 digits sent by the telco...
aar strips off the 333 and sends it to route pattern 23, which then hands the call to rightfax... (trunk 4 in my case)
in rightfax, 1101 goes to one box, and 1102 goes to the other,,
hope it helps..

 

[Zen216]

couple of corrections... sorry...
the stations were from an old configuration, and are not used any longer, sorry...

the ports are defined on the trunk group form,, (here is page 6)
TRUNK GROUP
Administered Members (min/max): 1/16
GROUP MEMBER ASSIGNMENTS Total Administered Members: 16

Port Code Sfx Name Night Mode Type Ans Delay
1: 01C1201 TN464 F
2: 01C1202 TN464 F
3: 01C1203 TN464 F
4: 01C1204 TN464 F
5: 01C1205 TN464 F
6: 01C1206 TN464 F
7: 01C1207 TN464 F
8: 01C1208 TN464 F
9: 01C1209 TN464 F
10: 01C1210 TN464 F
11: 01C1211 TN464 F
12: 01C1212 TN464 F
13: 01C1213 TN464 F
14: 01C1214 TN464 F
15: 01C1215 TN464 F

and finally,, there is no hunt group defined for the rightfax server,, just the trunk group...
so all that is defined is the trunk group, uniform dial plan, aar ana, and a route pattern....
hope it helps

 

[cgogan]

I think I have the same configuration that you have and this is what I do to make the calls go to rightfax and pass the digits so that they go to the correct user.

Set the fax number up as a vdn.

In the vector you just need a step that reads

Route to number ???(tac of your trunk group)~p????(number that you want to send to rightfax) with coverage n if unconditionally

This should work if the rightfax is configured correctly and the trunk is up!

 

[rejackson]

Thanks zen216 and cgogan. The udp and aar seem to be what I was missing out on. I had not used it, only ars.

zen216 - Is that trunk really a PRI? I am confused by the type tie and wink/wink.

 

[Zen216]

we just had this installed, (I did not do it, our BP did during the cutover) The way they explained it to me is.. that it was a pri setup as line-side t-1 to the fax server..
so I could be wrong on it being a pri, it would not be the first time that the BP's explanation and reality were completely different,, but we had to get new pri cards for this (TN464's)... hope it helps

 

[rejackson]

Route to number ???(tac of your trunk group)~p????(number that you want to send to rightfax) with coverage n if unconditionally

CGogan - I'm not sure I understand that vector route statement. I had looked into this and couldn't figure out how to route to a trunk. What does the ~p do? I want the called number to go to the rightfax.

 

[rejackson]

zen,

It seems like those patterns, 1101 and 1102 have to be defined somewhere as extensions so the public trunks can direct their call handling to them. Have you any idea how that is done?

 

[cgogan]

The step that I outlined is how to route to a trunk and pass the Rightfax routing code to the server.

This is what the step should look like...

route-to number 123~p9876 with cov n if unconditionally

123 is the trunk access code from page one of your trunk group form (tac), this tells the vector to dial the trunk directly.
~p outpulses the digits after the ~p
9876 is the fax extension/Rightfax routing code.

I do not have anything special set up in my udp and aar tables.

The setup that you have sounds exactly like the setup that I have. If you want to try the vector method I would try the vector as I described above without the udp/aar changes. The vector option enables you to send any phone number in your system to the Rightfax server using the lineside pri trunk that you have connected to your server.

You may also need a change to your trunk group. Make sure that dial access is stroked to y on the first screen. Also, on the group member assignments screen I have the mode set to e&m and the type set to T1-stan.

It looks like Zen216 and I have this set up differently so for Zen216's mothod you would not need the vector and for my method you would not need the udp/aar table entries.

 

[Zen216]

I have searched through my system, and ext 1101 and 1102 are not defined anywhere... (they are setup in rightfax)
the fax #'s are 439-1101 and 439-1102, our carrier just passes 1101 and 1102 to the pbx... then I guess UDP picks it up and the AAR....
here is a trace from my station when I dial 1101...


LIST TRACE

time data

08:58:04 tone-receiver 01AXX03 cid 0x127c
08:58:04 active station 5129 cid 0x127c
08:58:06 dial 1101 route:UDP|AAR
08:58:06 term trunk-group 4 cid 0x127c
08:58:06 dial 1101 route:UDP|AAR
08:58:06 route-pattern 23 preference 1 cid 0x127c
08:58:06 seize trunk-group 4 member 11 cid 0x127c
08:58:08 dial 1101 route:UDP|AAR
08:58:08 outpulse done 1101
08:58:09 active trunk-group 4 member 11 cid 0x127c
08:58:12 idle station 5129 cid 0x127c

here is a trace of the incoming trunk

LIST TRACE

time data

09:01:31 Calling party trunk-group 2 member 1 cid 0x12ba
09:01:31 Calling Number & Name 4138218900 NO-CPName
09:01:31 active trunk-group 2 member 1 cid 0x12ba
09:01:35 dial 1101 route:UDP|AAR
09:01:35 term trunk-group 4 cid 0x12ba
09:01:35 dial 1101 route:UDP|AAR
09:01:35 route-pattern 23 preference 1 cid 0x12ba
09:01:35 seize trunk-group 4 member 12 cid 0x12ba
09:01:38 dial 1101 route:UDP|AAR
09:01:38 outpulse done 1101
09:01:38 active trunk-group 4 member 12 cid 0x12ba
09:01:44 idle trunk-group 2 member 1 cid 0x12ba

 

[rejackson]

Thanks very much Zen216 and CGogan. You both set me straight and opened my eyes up to parts of the system I had not looked into before.

I tried both methods but I used Zen's method because it better accomodated the 20+ inbound fax numbers that can be called at our different offices. They are all being served by the RightFax (or will be).

 

[Zen216]

Glad I could help