Solved: T.37 on-ramp with voip dial peer?

toddcarp123 · ‎05-22-2008

I have a MGCP gateway registerd with CM 5.1 with a PRI. I'd like to use T.37 onramp to forward inbound faxes to Unity, but onramp is not supported with MGCP.

I have a translation pattern in CM pointing a test DID to a separate H.323 gateway which is a 3725 running 12.4(15)T5. The gateway is configured as follows:

!

dial-peer voice 20 mmoip

service fax_on_vfc_onramp_app out-bound

destination-pattern 1765

information-type fax

session target mailto:.....

!

dial-peer voice 10 voip

service onramp

incoming called-number 1765

!

The call routing seems to be working based on the following dial-peer trace:

10:06:08: //-1/80CDA72B2600/DPM/dpAssociateIncomingPeerCore:

Calling Number=1234567890, Called Number=1765, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

10:06:08: //-1/80CDA72B2600/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=10

10:06:08: //-1/80CDA72B2600/DPM/dpAssociateIncomingPeerCore:

Calling Number=1234567890, Called Number=1765, Voice-Interface=0x0,

Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

Peer Info Type=DIALPEER_INFO_SPEECH

10:06:08: //-1/80CDA72B2600/DPM/dpAssociateIncomingPeerCore:

Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=10

10:06:08: //-1/80CDA72B2600/DPM/dpMatchPeersCore:

Calling Number=, Called Number=1765, Peer Info Type=DIALPEER_INFO_FAX

10:06:08: //-1/80CDA72B2600/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=1765

10:06:08: //-1/80CDA72B2600/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

10:06:08: //-1/80CDA72B2600/DPM/dpMatchPeersInfotype:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=20

The issue is that the call just hangs with no audio. All the documentation shows pots dial-peers for the inbound calls. I'm wondering if this works with voip dial peers and is there anything else I should try.

Thanks,

Todd

Michael Hanes · ‎05-28-2008

T.37 onramp calls must match a POTS dial-peer. Others have gotten around this type of issue by using a T1 cross-over cable between 2 POTS ports in a back-to-back type of configuration. Basically the gateway takes incoming H.323 call routes it to a T1 port that is connected right back into another T1 port on the same gateway. When the call re-enters the gateway, it can then match the required T.37 onramp POTS dial-peer. Granted, this is not the most elegant solution but it has had some success in scenarios similar to yours.

Regards,

David

View solution in original post

sdekooter · ‎05-24-2008

The IOS architecture doesn't seem to allow this behaviour. T37 should always bypass DSP in order to convert the call.

Michael Hanes · ‎05-28-2008

T.37 onramp calls must match a POTS dial-peer. Others have gotten around this type of issue by using a T1 cross-over cable between 2 POTS ports in a back-to-back type of configuration. Basically the gateway takes incoming H.323 call routes it to a T1 port that is connected right back into another T1 port on the same gateway. When the call re-enters the gateway, it can then match the required T.37 onramp POTS dial-peer. Granted, this is not the most elegant solution but it has had some success in scenarios similar to yours.

Regards,

David

toddcarp123 · ‎05-28-2008

Wow! Great idea! I'll give it a try.

Thanks!

metalium2007 · ‎05-12-2009

Hello,

Can we do the same back2back connection with only one gateway, to do the trick? (one gateway with several E1/T1 ports) ?

Thanks!

paolo bevilacqua · ‎05-12-2009

As David said above...

into another T1 port on the same gateway