Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
406
Views
0
Helpful
6
Replies

BRI to PRI FAX with Faxsoftware

pwenger
Level 3
Level 3

‎01-08-2008 11:12 AM - edited ‎03-15-2019 08:06 AM

I've got the following ennvironement: Act Faxsoftware<----->Eicon 4 BRI ISDN Card<----->Cisco2851 MGCP- BRI interface<---->same Cisco2851 MGCP- PRI<---->PSTN. We use this scenario just for FAX.

Incoming faxes from PSTN is no problem, but it's not possible to send a fax to the PSTN.

Any idea why??

See below the relevant configuration of the router and a debug isdn q931 output.

ROUTER#sh run

Building configuration...

network-clock-participate slot 1

network-clock-participate wic 0

network-clock-participate wic 1

network-clock-participate wic 2

!

ip cef

!

no ip domain lookup

multilink bundle-name authenticated

!

isdn switch-type primary-net5

!

voice service voip

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

!

voice-card 0

no dspfarm

!

voice-card 1

no dspfarm

!

controller E1 0/0/0

pri-group timeslots 1-31 service mgcp

!

!

translation-rule 1

Rule 1 ^0.% 00

!

!

translation-rule 2

Rule 1 7007 061967007

Rule 2 7005 061967005

Rule 3 77106 0619677106

!

interface Loopback0

ip address 172.24.y.x 255.255.255.255

!

interface GigabitEthernet0/0

ip address 172.24.a.b 255.255.255.252

!

interface Serial0/0/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn overlap-receiving T302 5000

isdn incoming-voice voice

isdn bind-l3 ccm-manager

isdn send-alerting

isdn sending-complete

no cdp enable

!

interface BRI0/1/1

description to_DIVA_SERVER

no ip address

isdn switch-type basic-net3

isdn protocol-emulate network

isdn layer1-emulate network

isdn incoming-voice voice

isdn bind-l3 ccm-manager service mgcp

isdn send-alerting

isdn sending-complete

isdn skipsend-idverify

no clns route-cache

!

control-plane

!

voice-port 0/0/0:15

translate calling 1

cptone DE

timeouts interdigit 5

!

voice-port 0/1/1

translate calling 1

compand-type a-law

cptone DE

!

ccm-manager fallback-mgcp

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server 172.24.4.11

ccm-manager config

!

mgcp

mgcp call-agent 172.24.4.11 2427 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

mgcp package-capability pre-package

no mgcp package-capability res-package

no mgcp package-capability fxr-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp validate call-agent source-ipaddr

mgcp fax t38 inhibit

mgcp rtp payload-type g726r16 static

mgcp bind control source-interface Loopback0

mgcp bind media source-interface Loopback0

!

mgcp profile default

!

dial-peer voice 10 pots

destination-pattern 0T

translate-outgoing calling 2

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 1 pots

trunkgroup DIVA_SERVER

service mgcpapp

direct-inward-dial

forward-digits all

!

end

-----------------------------------------------------------------------------------------------

Jan 8 18:46:38.871: ISDN BR0/1/1 Q931: RX <- DISCONNECT pd = 8 callref = 0xDD

Cause i = 0x8090 - Normal call clearing

Jan 8 18:46:38.883: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0xC951

Cause i = 0x8090 - Normal call clearing

Jan 8 18:46:38.883: ISDN BR0/1/1 Q931: TX -> RELEASE pd = 8 callref = 0x5D

Jan 8 18:46:38.899: ISDN BR0/1/1 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xDD

Cause i = 0x8090 - Normal call clearing

Jan 8 18:46:38.931: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x4951

Jan 8 18:46:38.943: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0xC951

Regards

Peter

Labels:
0 Helpful
6 Replies 6

pcameron
Cisco Employee
Cisco Employee

‎01-09-2008 04:53 AM

You must add the network-clock-select e1 0/0/0 command to the config to ensure the DSP's use the clock reference that is derived from the E1 RX bit stream on the E1 interface. This is then used to drive the BRI ports. Without this command, the BRI's will use the internal oscillator and there will likely be clock slips on all of the interfaces, including the E1. This will break fax and modem operation. Do a show controllers e1 and you see clock slips being registered.

The other thing to watch out for is that when a port is under MGCP control, the DSP's are always connected to the actual voice port. These may add delay or degradation to fax/modem calls. If you change to H323 operation, the router is capable of performing a pure TDM connection between the B channels on the PRI and the BRI ports - once the call connects the DSP is removed from the signal path and the B channels are cross connected across the router's TDM backplane. Refer here for more background -

http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00804794c6.shtml

0 Helpful

pwenger
Level 3
Level 3
In response to pcameron

‎01-09-2008 07:52 AM

Thanks for your answer!

I entered the command network-clock-select e1 0/0/0, but nothing changed. Will I have to reset MGCP?

As I understand you, there is no way with MGCP?

Well, fact is, I don't like to change to h323 as I have to reconfigure the whole system.

Regards

Peter

0 Helpful

p-siadoua
Level 1
Level 1
In response to pwenger

‎06-17-2009 01:50 AM

hi

i have to configure a fax server with BRI card on a ISR 3845. I have done the same configuration in MGCP but i can't have my an active layer 2.

Pamela

0 Helpful

pwenger
Level 3
Level 3
In response to p-siadoua

‎06-17-2009 02:31 AM

Hi Pamela

make sure, the command isdn protocol-emulate network is still in the config of the router. After a reboot of CUCM this command is automaticly removed.

The explanation for the reason you find in this conversation . http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=General&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cc1ccfa

Regards

Peter

0 Helpful

p-siadoua
Level 1
Level 1
In response to pwenger

‎06-17-2009 07:46 AM

Thanks Peter,

But it doesn't change, i still have the same problem. Do you know why the status of the BRI PORT ON CUCM web interface, is " Unregistered"?

this is a show isdn extract :

ISDN BRI0/2/0 interface

******* Network side configuration *******

dsl 8, interface ISDN Switchtype = basic-net3

L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 64, Ces = 1, SAPI = 0, State = TEI_ASSIGNED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 8 CCBs = 0

The Free Channel Mask: 0x80000003

%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 9. Layer 3 output may not apply

Pamela

Thx

0 Helpful

pwenger
Level 3
Level 3
In response to p-siadoua

‎06-17-2009 12:45 PM

Pamela

what do you see with show mgcp status? Check the configuration of the gateway in CUCM(hostname). Check the mgcp configuration of the gateway. Is there a firewall or acl between CUCM and gateway?

Cheers

Peter

0 Helpful
Getting Started

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:

Customers Also Viewed These Support Documents