CME FAX ISSUE

[mkhriesa]

DEAR

we have CME 11 with 2 FXS for fax , and SIP trunk , we configured the fax and its receiving but not sending :

for outgoing:

dial-peer voice 304 voip
 destination-pattern 5......$
 session protocol sipv2
 session target ipv4:213.139.43.143
 session transport udp
 incoming called-number .
 voice-class sip bind control source-interface GigabitEthernet0/0/1
 voice-class sip bind media source-interface GigabitEthernet0/0/1
 dtmf-relay rtp-nte sip-kpml
 codec g711ulaw
 no vad

for incoming

dial-peer voice 33 pots
 destination-pattern 1234
 port 0/2/1

dial-peer voice 133 pots
 destination-pattern 1235
 port 0/2/0

please advise if any command is missing , attach  debug ccsip

[RICK CLEMENTS]

We had an issue very much like this.  We tried everything under the sun to make it work. Then in frustration one of our Field techs decide to read the FAX manufacturer's manual.  Come to find out, the FAX machine itself had  a setting in it for services over a VoIP connection.  The FAX machine that we were using was a Brother brand machine.  Once he set the machine to talk over a VoIP provided analog circuit (Cisco FXE port) all problems disappeared.

[R0g22]

From the logs I see T.38 being used. CME sends a RE-INVITE to initiate a fax switchover, your ITSP sends a 200 OK with T.30 caps as well. Don't have the complete logs though. Please take a log for the following debugs -

debug ccsip message
debug voice ccapi inout
debug voip vtsp all
debug fax relay t30 all-level-1

[mkhriesa]

Hi,

the Fax sent successfully for this number: 065000990

and not working for this number : 065100315

dial peer used on both scenario :

dial-peer voice 22 voip
 destination-pattern 0[23456].......$
 session protocol sipv2
 session target ipv4:213.139.43.175
 voice-class sip bind control source-interface GigabitEthernet0/0/1
 voice-class sip bind media source-interface GigabitEthernet0/0/1
 dtmf-relay rtp-nte sip-kpml
 codec g711ulaw
 no vad

dial-peer voice 33 pots
 destination-pattern 1234
 port 0/2/1

attached is the requested logs , appreciate your feedback

[mkhriesa]

working debug

[R0g22]

Adding relevant parts of the log -

Working -

002046: Feb 14 07:32:58.703: 0/2/1 344581167 fr-entered=10(ms) >> fax relay state
timestamp=344582117 fr-msg-det TSI
timestamp=344582867 fr-msg-det DCS
timestamp=344587117 fr-msg-tx CFR   << confirmation to receive. (fax pages can be transmitted)
timestamp=344611647 fr-msg-det EOP << end of procedure received
timestamp=344613957 fr-msg-tx MCF  << message confirmation
timestamp=344615647 fr-msg-det DCN << disconnect

Non-working

001480: Feb 14 07:27:16.945: 0/2/1 344239428 fr-entered=10(ms)
timestamp=344240388 fr-msg-det TSI
timestamp=344241138 fr-msg-det DCS
timestamp=344245108 fr-msg-tx CFR   << confirmation to receive. Post this things change
timestamp=344269248 fr-msg-det PPS << partial page signal
timestamp=344275998 fr-msg-det PPS << partial page signal
timestamp=344282758 fr-msg-det DCN << no response from us. Disconnect received

"det" are the T.30 messages being picked up by DSP. "tx" are the ones being sent

Was the non-working fax a multi-page fax ? Can you attach a "show run" from the CME please.

[mkhriesa]

Attached show run

[R0g22]

Thanks. Please add the following to your outbound DP which is 22 -

dial-peer voice X voip
fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw
fax-relay ecm disable
fax nsf 000000
fax-relay sg3-to-g3

Test you faxes post that. If it still does not work, please take a log for the same set of debugs with the new configuration in place.

[mkhriesa]

hi

same result , attached logs for fax1 and fax2 not working 065100315

, and logs for working number   065000990

after changes

[mkhriesa]

Hi  Nipun    

Did you check the logs? I alrady engaged Telco and they send me the attached tracing , also asked to try with alaw but no luck , also they asked why we send header 1234!!

[mkhriesa]

Hi  Nipun    

Did you check the logs? I alrady engaged Telco and they send me the attached tracing , also asked to try with alaw but no luck , also they asked why we send header 1234!!

[R0g22 · Accepted solution]

Which header are they talking about??

[mkhriesa · Accepted solution]

solved , we added on dial peer 22

 fax protocol pass-through g711alaw

thanks

[R0g22]

Good to hear that. So your ISP was doing T.38 for some and pass-through for some ? Weird.