Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Issue with Fax machine receiving fax from SIP Gateway

Hello,

We have a fax machine on an mgcp controlled vg 224 and it is has severe issue receiving faxes that come in from the PSTN.

Flowpath:

PSTN -> 2851 GW PRI circuit ->SIP Trunk from GW to CUCM 7.1.3 -> MGCP controlled VG 224 using g711 passthur, T38 inhibited, to a Fax machine.

Note, voice calls seem fine when testing with an analog handset.

debug ccsip messages shows the following:

*Apr 13 18:21:21.729: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 500 Internal Server Error

The topology is there are two Gateways for this site and each has a SIP Trunk to CUCM. IP's ending in .220 for one and .221 for the second gateway.

Inbound calls come in a PRI on the .221 Note: each router has a PRI, one gets local, the other gets LD and INTL, dial-peers are sip -h323.

It appears to me that the two SIP Trunks are causing an issue with this one fax machine, it appears the internal server error is due to calls getting routed based on both the .20 and the .221 which is causing a routing issue, it seems,, which is odd as other faxes on other Vg 224's at same site seem to be working fine. There at least two faxes on this same VG having this issue. Short debug follows:

Sent:

INVITE sip:62993@xx.xx.169.220:5060 SIP/2.0

Via: SIP/2.0/UDP xx.xx.169.221:5060;branch=z9hG4bK23A171145

Remote-Party-ID: <sip:xxx3869800@xx.xx.169.221>;party=calling;screen=no;privacy=off

From: <sip:xxx3869800@xx.xx.169.221>;tag=5546D6C-1154

To: <sip:62993@xx.xx.169.220>

Date: Fri, 13 Apr 2012 18:21:21 GMT

Call-ID: 4E1FF68C-84CC11E1-91ABBA4D-E011E85F@xx.xx.169.221

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 1310557676-2227966433-2166947865-806423056

User-Agent: Cisco-SIPGateway/IOS-12.x

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Max-Forwards: 70

Timestamp: 1334341281

Contact: <sip:xxx3869800@xx.xx.169.221:5060>

Expires: 180

Allow-Events: telephone-event

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 333

v=0

o=CiscoSystemsSIP-GW-UserAgent 2441 307 IN IP4 xx.xx.169.221

s=SIP Call

c=IN IP4 xx.xx.169.221

t=0 0

m=audio 16748 RTP/AVP 0 18 100 101

c=IN IP4 xx.xx.169.221

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:100 X-NSE/8000

a=fmtp:100 192-194

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

*Apr 13 18:21:21.693: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP xx.xx.169.221:5060;branch=z9hG4bK23A171145

From: <sip:xxx3869800@xx.xx.169.221>;tag=5546D6C-1154

To: <sip:62993@xx.xx.169.220>

Date: Fri, 13 Apr 2012 18:22:03 GMT

Call-ID: 4E1FF68C-84CC11E1-91ABBA4D-E011E85F@xx.xx.169.221

Timestamp: 1334341281

CSeq: 101 INVITE

Allow-Events: telephone-event

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

*Apr 13 18:21:21.701: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:62993@xx.xx.169.221:5060 SIP/2.0

Via: SIP/2.0/UDP xx.xx.169.220:5060;branch=z9hG4bK1651C4A8

Remote-Party-ID: <sip:xxx3869800@xx.xx.169.220>;party=calling;screen=no;privacy=off

From: <sip:xxx3869800@xx.xx.169.220>;tag=54FBAF8-1C26

To: <sip:62993@xx.xx.169.221>

Date: Fri, 13 Apr 2012 18:22:03 GMT

Call-ID: 674FB818-84CC11E1-B3FC93ED-99EDEFF2@xx.xx.169.220

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 1310557676-2227966433-2166947865-806423056

User-Agent: Cisco-SIPGateway/IOS-12.x

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Timestamp: 1334341323

Contact: <sip:xxx3869800@xx.xx.169.220:5060>

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 69

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 334

v=0

o=CiscoSystemsSIP-GW-UserAgent 1765 2391 IN IP4 xx.xx.169.220

s=SIP Call

c=IN IP4 xx.xx.169.220

t=0 0

m=audio 17586 RTP/AVP 0 18 100 101

c=IN IP4 xx.xx.169.220

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:100 X-NSE/8000

a=fmtp:100 192-194

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

*Apr 13 18:21:21.717: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP xx.xx.169.220:5060;branch=z9hG4bK1651C4A8

From: <sip:xxx3869800@xx.xx.169.220>;tag=54FBAF8-1C26

To: <sip:62993@xx.xx.169.221>

Date: Fri, 13 Apr 2012 18:21:21 GMT

Call-ID: 674FB818-84CC11E1-B3FC93ED-99EDEFF2@xx.xx.169.220

Timestamp: 1334341323

CSeq: 101 INVITE

Allow-Events: telephone-event

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

*Apr 13 18:21:21.717: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:62993@xx.xx.169.220:5060 SIP/2.0

Via: SIP/2.0/UDP xx.xx.169.221:5060;branch=z9hG4bK23A1846C

Remote-Party-ID: <sip:xxx3869800@xx.xx.169.221>;party=calling;screen=no;privacy=off

From: <sip:xxx3869800@xx.xx.169.221>;tag=5546D94-1F27

To: <sip:62993@xx.xx.169.220>

Date: Fri, 13 Apr 2012 18:21:21 GMT

Call-ID: 4E26114D-84CC11E1-91B1BA4D-E011E85F@xx.xx.169.221

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 1310557676-2227966433-2166947865-806423056

User-Agent: Cisco-SIPGateway/IOS-12.x

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Timestamp: 1334341281

Contact: <sip:xxx3869800@xx.xx.169.221:5060>

Expires: 180

Allow-Events: telephone-event

Max-Forwards: 68

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 332

v=0

o=CiscoSystemsSIP-GW-UserAgent 208 564 IN IP4 xx.xx.169.221

s=SIP Call

c=IN IP4 xx.xx.169.221

t=0 0

m=audio 17044 RTP/AVP 0 18 100 101

c=IN IP4 xx.xx.169.221

a=rtpmap:0 PCMU/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:100 X-NSE/8000

a=fmtp:100 192-194

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

*Apr 13 18:21:21.729: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 500 Internal Server Error

Via: SIP/2.0/UDP xx.xx.169.221:5060;branch=z9hG4bK23A1846C

From: <sip:xxx3869800@xx.xx.169.221>;tag=5546D94-1F27

To: <sip:62993@xx.xx.169.220>;tag=54FBB1C-2B

Date: Fri, 13 Apr 2012 18:22:03 GMT

Call-ID: 4E26114D-84CC11E1-91B1BA4D-E011E85F@xx.xx.169.221

Timestamp: 1334341281

CSeq: 101 INVITE

Allow-Events: telephone-event

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

*Apr 13 18:21:21.737: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

ACK sip:62993@xx.xx.169.220:5060 SIP/2.0

Via: SIP/2.0/UDP xx.xx.169.221:5060;branch=z9hG4bK23A1846C

From: <sip:xxx3869800@xx.xx.169.221>;tag=5546D94-1F27

To: <sip:62993@xx.xx.169.220>;tag=54FBB1C-2B

Date: Fri, 13 Apr 2012 18:21:21 GMT

Call-ID: 4E26114D-84CC11E1-91B1BA4D-E011E85F@xx.xx.169.221

Max-Forwards: 70

CSeq: 101 ACK

Allow-Events: telephone-event

Content-Length: 0

Please advise if we are running into an issue here due to the two SIP trunks and two gateways fo this site.

Note, calls come in on the .221 router.

Best Regards,

Chuck

1 REPLY
Hall of Fame Super Gold

Issue with Fax machine receiving fax from SIP Gateway

For fax machines, you should use H.323 or SIP, and T.38. Dong this way, you can also bypass CM completely.

Usign MGCP and fax pass-thour is not recommended, and as you're expereinced, likely to cause problems.

220
Views
0
Helpful
1
Replies