Re: Xmedius T.38 Fax

bclarke · ‎10-27-2004

I have been trying to get Xmedius working with various gateways over the last week, and their tech support has been less than helpfull.

If anyone out there has a know working hardware/software solution I would love to see it.

I used the suggested dial peer statements with both analog FXO ports and digital PRI ports with similar results.

We have not even tried incoming fax yet, only outgoing.

The problem we see is that once the Fax server connects via H.323 to the router it will start the call and either not send anything at all or send 1/4 of the page and stop.

Xmedius says its the receiving fax machines or the lines, but they work fine for regular faxing.

Anyway any help or tips would be great

mcotrone · ‎10-27-2004

Can you post your gatway configs?

Thanks

Mike

bclarke · ‎10-27-2004

Sure, I have tried several changes, here is the latest. With this config we can send faxes, but most fail or only output 1/2 of the page.

version 12.2

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname cpr-pstn-gw2

!

logging queue-limit 100

!

ip subnet-zero

!

no ip domain lookup

!

ip cef

!

no voice hpi capture buffer

no voice hpi capture destination

!

interface FastEthernet0/0

ip address 10.11.0.5 255.255.255.0

speed auto

full-duplex

h323-gateway voip bind srcaddr 10.11.0.5

!

voice-port 2/0

!

voice-port 2/1

!

voice-port 3/0

!

voice-port 3/1

!

dial-peer cor custom

!

dial-peer voice 201 voip

preference 1

incoming called-number .

destination-pattern [1-9]

session target ipv4:10.0.1.123

dtmf-relay h245-signal

codec g711ulaw

fax rate 9600

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

no vad

!

dial-peer voice 200 pots

preference 5

incoming called-number .

destination-pattern [1-9]

port 2/0

!

bclarke · ‎10-27-2004

Ideally once we have a stable working config, I would to be able share the PRI line and Gateway with Callmanager, I think I will have to use H.323 instead of MGCP with CM, I have not been able to get a call out when the gateway port is controlled by CM with MGCP and Xmedius with H.323

Here is our config with the PRI , CM MGCP, and H.323

!

voice service voip

fax protocol t38 nse force ls-redundancy 0 hs-redundancy 0 fallback cisco

h323

!

ccm-manager switchback immediate

ccm-manager fallback-mgcp

ccm-manager redundant-host 10.11.0.11

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server 10.11.0.10

!

controller T1 1/0

framing esf

linecode b8zs

cablelength short 133

pri-group timeslots 1-24 service mgcp

description SYS 103

!

controller T1 1/1

shutdown

framing esf

linecode b8zs

description SYS 101

!

interface Serial1/0:23

no ip address

no logging event link-status

isdn switch-type primary-ni

isdn incoming-voice voice

isdn bind-l3 ccm-manager

no cdp enable

!

control-plane

!

voice-port 1/0:23

!

mgcp

mgcp call-agent 10.11.0.10 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

mgcp package-capability sst-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax rate 14400

no mgcp explicit hookstate

mgcp fax t38 gateway force

mgcp rtp payload-type g726r16 static

!

mgcp profile default

!

sccp local FastEthernet0/0

sccp

sccp ccm 10.11.0.10 priority 1

sccp ccm 10.11.0.11 priority 2

sccp mtp sessions 48

!

dspfarm transcoder maximum sessions 24

dspfarm codec g729 vad disable

dspfarm

!

dial-peer cor custom

!

dial-peer voice 100 pots

application mgcpapp

port 1/0:23

!

dial-peer voice 101 pots

application mgcpapp

!

dial-peer voice 201 voip

preference 1

destination-pattern [1-9]

session target ipv4:10.0.1.123

incoming called-number .

dtmf-relay h245-signal

codec g711ulaw

fax rate 14400

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

!

dial-peer voice 200 pots

destination-pattern [1-9]

incoming called-number .

direct-inward-dial

port 1/0:23

!

rickb · ‎11-09-2004

Below is a working config on a 3640 Router:

Current configuration : 1908 bytes

!

version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname VGW1

!

boot system flash c3725-is-mz.123-1a.bin

enable password

!

voice-card 1

no dspfarm

!

ip subnet-zero

!

isdn switch-type primary-ni

!

voice service voip

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

!

voice class codec 1

codec preference 1 g711ulaw

!

no voice hpi capture buffer

no voice hpi capture destination

!

controller T1 1/0

framing esf

linecode b8zs

pri-group timeslots 1-24

!

controller T1 1/1

framing esf

linecode b8zs

pri-group timeslots 1-24

!

interface FastEthernet0/0

ip address 10.10.1.55 255.255.255.0

speed 100

full-duplex

h323-gateway voip bind srcaddr 10.10.1.55

!

interface FastEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

interface Serial1/0:23

no ip address

no logging event link-status

isdn switch-type primary-ni

isdn incoming-voice voice

no isdn incoming alerting add-PI

no cdp enable

!

interface Serial1/1:23

no ip address

no logging event link-status

isdn switch-type primary-ni

isdn incoming-voice voice

no isdn incoming alerting add-PI

no cdp enable

!

ip http server

ip classless

ip route 0.0.0.0 0.0.0.0 10.10.1.51

!

voice-port 1/0:23

!

voice-port 1/1:23

!

dial-peer cor custom

!

dial-peer voice 38 voip

description Incoming faxes to XMedius via T.38

incoming called-number .

destination-pattern ....

session target ipv4:10.10.1.13

dtmf-relay h245-signal

codec g711ulaw

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco

!

dial-peer voice 100 pots

description Outbound calls to Second PRI

preference 1

destination-pattern T

fax rate voice

direct-inward-dial

port 1/1:23

forward-digits all

!

line con 0

line aux 0

line vty 0 4

exec-timeout 0 0

password

login

!

end

bclarke · ‎11-09-2004

Thanks, We did get it working pretty well with a 2600 router and an Analog Line after reloading on a new server.

I recently switched it back to the "production" gateway which is a AGM Card in a CAT 4500 and its hit or miss. with partially transmitted pages.

Tech support at Xmedius says its because the PRI has Clock slips. I can not seem to get rid of the slips, tried various timing settings and cable length settings.

I checked the PRIs back at my office and they slip too, must be a SBC thing. The users do not complain of poor voice quality