04-25-2008 01:21 PM - edited 03-15-2019 10:18 AM
I am trying to get my fax solution to work outbound. Long Story short my fax server cannot route via calling number, they can only route based on called number. So I have devised a workaround to send all calls to a dedicated router that will route based on calling number and then route to the appropriate Gateway. It Routes properly because I can use a cisco phone and complete a call but faxing attempts attempts to sync up using T.38 but I am receiving a sip message - 488 Not Acceptable Media.
I have tried both H323 and SIP as well as playing with the Fax Rate, sip udp, etcâ¦. but still having an issue.
For Testing Purposes I have the following setup.
FaxServer ->Gateway1->Gateway2->PSTN
Gateway1 ver12.4(17a)
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 ls-redundancy 2 hs-redundancy 2 fallback cisco
h323
sip
bind control source-interface FastEthernet0/1
bind media source-interface FastEthernet0/1
!
voice class h323 1
h225 timeout tcp establish 3
!
voice translation-rule 1
rule 1 /\(.*\)/ /701\1/
!
voice translation-profile XXXXXXXXXX-In
translate called 1
dial-peer voice 1341 voip
description ***Outbound Fax Dial based on ANI 1341 Prepend 701 send to Dial
translation-profile incoming XXXXXXXXXX -In
answer-address XXXXXXXXXX
voice-class h323 1
session protocol sipv2
incoming called-number XXXXXXXXXX
dtmf-relay h245-alphanumeric
codec g711ulaw
fax-relay ecm disable
fax rate 14400
fax protocol t38 ls-redundancy 2 hs-redundancy 2 fallback cisco
no vad
!
dial-peer voice 7011341 voip
description ***Outbound Fax Dial Hairping
destination-pattern 701T
voice-class h323 1
session protocol sipv2
session target ipv4:<Gateway2IpAddress>
dtmf-relay h245-alphanumeric
codec g711ulaw
fax-relay ecm disable
fax rate 14400
fax protocol t38 ls-redundancy 2 hs-redundancy 2 fallback cisco
no vad
!
Gateway2 12.4(15)T3
12.4(15)T3
voice service voip
address-hiding
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 ls-redundancy 2 hs-redundancy 2 fallback cisco
h323
sip
bind control source-interface GigabitEthernet0/0
bind media source-interface GigabitEthernet0/0
options-ping 90
voice class h323 1
h225 timeout tcp establish 3
dial-peer voice 999998 pots
destination-pattern 7010T
port 0/1/0:23
dial-peer voice 2 voip
description ***default inbound voip dial peer ****
voice-class h323 1
session protocol sipv2
incoming called-number .
dtmf-relay h245-alphanumeric
codec g711ulaw
fax-relay ecm disable
fax rate 14400
fax protocol t38 ls-redundancy 2 hs-redundancy 2 fallback cisco
Anyone have any ideas?
04-25-2008 02:10 PM
Nevermind I figured it out, we upgraded the one router to 12.4(15)T3 IPVoice
I think it has some additional commands like the default "fax-relay sg3-to-g3"
Then it started working...after that we wanted calls to go through call manager and in order to get T.38 going there we had to change the sip security profile to UDP on outgoing Transport Type.
09-11-2008 02:05 PM
Which did you find easier Sip or H323, what fax server are you using? could you please let me see your current config.
Thank you
Stuart
09-11-2008 06:00 PM
I have done several installations in the past couple of months. Each instance has been slightly different and many times Call Manager is in the equations so it gets a bit more complicated but if I was setting up the Fax Software to communicate directly to the PSTN Gateway I suppose I would choose H323 and the configurations does not changed much from above.
I use Xmedius Fax Software made by Sagem Interstar. I like Xmedius alot especially now that you can either install it on a traditional server, or it can now be installed on a Network Module on a Router.
Sorry, I know that did not help you much.
09-24-2008 07:14 AM
Thank you very much, I have worked out what the problem was and managed to get h323 to work, it was the ISDN dialling national all the time, must be due to the FAX server forcing it too as calls using CSIM Start were fine. I am now using ISDN maps on the ISDN interface.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: