Re: Xmedius IP Fax and Callmanager

Tom Dillon · ‎07-09-2004

Hi, I am installing Xmedius fax server and I can successfully establish an h323 session between the server and 2651XM router running 12.3(8)T IOS code. I have a T1 connection to the PSTN and I can send/receive faxes from the Xmedius server through the 2651 to the PSTN.

I am trying to figure out a way to send a fax from a Callmanager connected fax machine to Xmedius via VoIP. Xmedius does not support a direct connection to Callmanager using a H323 gateway. It appears that my only choice is a VoIP to VoIP connection. (Xmedius------2651------CCM) I have tried a variety of voip dial-peer configurations that each have the corresponding session target ip address of Xmedius and Callmanager. But, I cannot get the call to setup. I continue to get a Q931 release message of "no route to destination".

Has anyone connected Xmedius to Callmanager using VoIP?

Thanks,

Tom.

andrew.chapman · ‎07-11-2004

Tom,

Could you post your running-config here so that we could take a look?

Thanks

Andy

Tom Dillon · ‎07-12-2004

I just loaded c2600-js2-mz.123-8.T.bin, Cisco's Multiservice IP-to-IP gateway IOS load to possibly get the VoIP to VoIP call setup working. Note: I had to disable fax relay "fax rate disable" on the pots dial-peer to get reliable inbound/outbound fax to work with multiple pages to Xmedius. Here's the code that works for Xmedius to PSTN, but I am unable to Callmanager to setup a call to Xmedius. Another point, I am still in test mode, so I have not placed a production load on the Xmedius server :-)

Thanks,

Tom.

no network-clock-participate wic 0

voice-card 0

dspfarm

no local-bypass

!

ip cef

isdn switch-type primary-5ess

!

voice service voip

no allow-connections any to pots

no allow-connections pots to any

allow-connections h323 to h323

!

voice class h323 1

h225 timeout tcp establish 3

!

controller T1 0/0

framing esf

linecode b8zs

ds0-group 0 timeslots 1-16 type e&m-wink-start

description SBC Supertrunk 46HCQA212182-001 16 Channels active last 8 busyout

!

controller T1 0/1

framing esf

linecode b8zs

!

interface FastEthernet0/0

description "Uplink"

ip address x.x.x.x 255.255.255.0

duplex auto

speed auto

!

interface FastEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

no ip http server

ip classless

ip route 0.0.0.0 0.0.0.0 x.x.x.1

ip tacacs source-interface FastEthernet0/0

!

voice-port 0/0:0

!

dial-peer cor custom

!

dial-peer voice 1 pots

description SBC Supertrunk T1 timeslots 1-16

destination-pattern .T

fax rate disable

forward-digits 7

!

dial-peer voice 11 voip

description Callmanager Subscriber 874 875 and 876 office code

destination-pattern 87[4-6]....

voice-class h323 1

session target ipv4:x.x.x.x

incoming called-number .

dtmf-relay h245-alphanumeric

codec g711ulaw

fax rate disable

ip qos dscp cs5 media

no vad

!

dial-peer voice 8549799 voip

description Xmedius DIDs 854-9000 through 854-9799

destination-pattern 8549[0-7]..

session target ipv4:x.x.x.x

incoming called-number .

dtmf-relay h245-signal

codec g711ulaw

fax rate 14400

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

no vad

andrew.chapman · ‎07-13-2004

Hi Tom,

Trying to rack my brains on this one. Have you tried creating a voip dial-peer on the gateway with just the DID's (9XXX) of the XMedius fax server for the destination pattern. Creating a route pattern of 9XXX within CCM and testing from there?

Sure I've had this working somewhere else....

Let me know your thoughts.

Cheers

Andy

Tom Dillon · ‎07-14-2004

I am now able to get a call setup between Callmanager and Xmedius via the two voip dial-peers. However, I am unable to get the Fax CED signal when the call is answered.

I added the following statements to the global config that finally allowed the voip to voip calls:

voice service voip

allow-connections h323 to h323

Here’s the current dial-peers that I am using:

dial-peer voice 11 voip

description Callmanager subscriber

preference 1

destination-pattern 87[4-6]....

voice-class h323 1

session target ipv4:x.x.x.x

incoming called-number .

dtmf-relay h245-alphanumeric

codec g711ulaw

fax rate 14400

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

no vad

dial-peer voice 8549799 voip

description Xmedius DIDs 854-9000 through 854-9799

destination-pattern 8549[0-7]..

session target ipv4:x.x.x.x

incoming called-number .

dtmf-relay h245-signal

codec g711ulaw

fax rate 14400

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

no vad

When I call a number routed to Xmedius from Callmanager the call is setup and answered by Xmedius, but I am not hearing a Fax CED signal.

I am using a standard group-3 fax machine that is connected to a FXS port on a VG200. I am thinking my current problem with no Fax CED signal is caused by fax t38 protocol defined on the voip dial-peer statements. I need it coded for the Xmedius dial-peer and I was told by the vendor that I need the two dial-peers to match. I am not sure how each call leg behaves with the T38 protocol. I know I am not running T38 from Callmanager to the fax machine connected to the FXS port.

The pots dial-peer to the PSTN has the fax rate disabled and I needed this to get multiple fax pages transmitted. My Xmedius voip dial-peer and the pots dial-peer works without problems so far. Here’s the pots dial-peer:

dial-peer voice 1 pots

description SBC Supertrunk T1 timeslots 1-16

destination-pattern .T

fax rate disable

forward-digits 7

Thanks for all the help,

Tom.

perezagg · ‎09-07-2004

Tom,

Have you found an answer?

Regards

Gregorio

tvanblon · ‎07-14-2004

What type of gateway is the Callmanager connected fax machine on? XMedius only supports h.323. You could try setting the XMedius server up in CM as an inter-cluster trunk to force h.323, maybe worth a try.

aalejo · ‎09-07-2004

Hi

XMedius Fax server needs t38 and CallManager does not support t38.

XMedius Fax server needs to see the gateway directly.

Alex

alan.basinger · ‎09-21-2004

Tom,

All you need to do is define the correct dial peers in the gateways. The call manager will set up the fax call in the gateway and get out of the way.

The Xmedius server does not have to talk to the call manager at all, just the gateway.

It would look something like this :

(SNIP)

!

voice class h323 1

h225 timeout tcp establish 3

!

(SNIP)

!

interface FastEthernet0/0

ip address 10.10.10.6 255.255.255.0

h323-gateway voip interface

h323-gateway voip bind srcaddr 10.10.10.6

!

(SNIP)

!

dial-peer voice 999999 voip

huntstop

preference 1

destination-pattern 555.... (the fax number(s))

progress_ind setup enable 3

session target ipv4:172.16.2.1 (the xmedius server)

dtmf-relay h245-signal

codec g711ulaw

fax rate 14400

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

ip qos dscp cs5 media

no vad

!

(SNIP)

Hope this helps....

Alan Basinger

Tom Dillon · ‎09-21-2004

Thanks Alan for the reply. I have made your recommended changes from home and I will test tomorrow at work. I haven't worked on Xmedius install for more than month. We upgraded CCM to 4.0(1) in August, which went very well. I had to stop working on Xmedius until CCM 4.0(1) upgrade was completed.

alan.basinger · ‎09-22-2004

No problem,

If you have any questions or need any help contact me offline @

alan-dot-basinger-at-cipcomm-dot-com

Alan

bclarke · ‎10-21-2004

Hi, I am working on my first Xmedius fax install.

I tested a few months ago on a 2650 router running MGCP with CallManager and 2 FXO interfaces.

I know that Xmedius uses H.323 to speak to the gateway,

My question is if I can share 1 gateway to the PSTN with Callmanager running MGCP and Xmedius using H.323? Seems like I could.

Also, being new to voip with Fax, Can I share the DID # for the user? For Example can the gateway route the Same DID # to either CallManager or Xmedius depending on whether its FAX or Voice call ?

Thanks