Jump to content
Vodia PBX forum
JaeJay

Inbound T.38 Fax to Exchange UM

Recommended Posts

First off, my sincerest of apologies if I am posting something here that has been 1) already answered and I've ever so blindly missed 2) something that is painfully simple and I am just waaay overthinking it or 3) do anything in this post that could generate an onslaught of people to virtually tar and feather me forum style.

 

Okay, now that is out of the way, on to the good stuff. I've been reading this forum for months now, as well as googled till I can google no more in search of the ellusive answer to (what seems to be?) getting Inbound T.38 faxing from my ITSP (Callcentric) to my Exchange UM Server, and on to the destined mailbox with my beloved PBXnSIP (loved more and more each day!) sitting right in the middle of ITSP and Exchange.

 

I feel as if I am very close, either that or my fear will shortly be proven and I have very little idea what the heck is actually going on. However, When sending a fax from the PSTN (310) 305-1073, to a DID on my callcentric account (310) 496-7515, Callcentric delivers the call as expected, PBXnSIP (localhost) sees it, sends the INVITE to across my Exchange UM trunk to the Exchange UM Server (oim-lax-ums-002), where I have added as a secondary fax-enabled extension 7515 (and faxing is enabled on the Exchange dial plan as well), the voicemail box picks up, Exchange says hey you aren't talking, you're beeping in CNG, I need to change. At that point, I think it looks like everything switches over to T38, and then just like magic, boom, absolutely nothing happens. :D

 

I can hear the voicemail greeting thru the PSTN fax on via the speaker.

 

<Simulation of Voice> "Hello this is me, I'm a voicemail box, please oh please let the fax just work!" </the end>

 

I can see the T38 switch happening (I think) from the logfile (see below)

 

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 204.11.192.23:5080;branch=z9hG4bK-dcbcf5a31b41b4dedebcd0e68c48fd79

From: <sip:13103051073@66.193.176.35>;tag=3434448420-488153

To: <sip:13104967515@ss.callcentric.com>;tag=4dd28c48d5

Call-ID: 24085721-3434448420-488126@msw2.telegeny.net

CSeq: 1 INVITE

Contact: <sip:17772471483@192.168.12.129:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.1.0.3037

Content-Type: application/sdp

Content-Length: 196

 

v=0

o=- 23537 23537 IN IP4 192.168.12.129

s=-

c=IN IP4 192.168.12.129

t=0 0

m=audio 56518 RTP/AVP 0 101

a=rtpmap:0 pcmu/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2008/10/31 06:27:37: SIP Rx udp:204.11.192.23:5080:

ACK sip:17772471483@192.168.12.129:5060;transport=udp SIP/2.0

v: SIP/2.0/UDP 204.11.192.23:5080;branch=z9hG4bK-d07ae536da0612b3ab058fe9274dafa8

f: <sip:13103051073@66.193.176.35>;tag=3434448420-488153

t: <sip:13104967515@ss.callcentric.com>;tag=4dd28c48d5

i: 24085721-3434448420-488126@msw2.telegeny.net

CSeq: 1 ACK

Max-Forwards: 15

m: <sip:2b8dc718852a6f6b11d4e2f782f147ca@204.11.192.23:5080;transport=udp>

l: 0

 

 

[9] 2008/10/31 06:27:38: SIP Rx tcp:192.168.12.114:5065:

INVITE sip:7515@192.168.12.126:57932;transport=tcp SIP/2.0

FROM: <sip:7515@oim-lax-ums-002.omegaidentitymedia.net;user=phone>;epid=D1809C5B9B;tag=513be24042

TO: <sip:7515@oim-lax-ums-002.omegaidentitymedia.net;user=phone>;tag=7619

CSEQ: 1 INVITE

CALL-ID: 444a52d7@pbx

MAX-FORWARDS: 70

VIA: SIP/2.0/TCP 192.168.12.114:5065;branch=z9hG4bKf31bc4d2

CONTACT: <sip:OIM-LAX-UMS-002.omegaidentitymedia.net:5065;transport=Tcp;maddr=192.168.12.114;ms-opaque=6b221c7eb4bdd3da>;automata

CONTENT-LENGTH: 290

USER-AGENT: RTCC/3.0.0.0

CONTENT-TYPE: application/sdp

 

v=0

o=- 0 1 IN IP4 192.168.12.114

s=session

c=IN IP4 192.168.12.114

t=0 0

m=audio 0 RTP/AVP 0 8 101 13

a=rtpmap:0 PCMU/8000/1

a=rtpmap:8 PCMA/8000/1

a=rtpmap:101 telephone-event/8000

m=image 55320 udptl t38

a=T38FaxRateManagement:transferredTCF

a=T38FaxUdpEC:t38UDPRedundancy

 

I can read that Exchange got a call that it thought was a fax, by looking at the Event Log on the UM Server, curiously saying no pages were received (see event log item directly below):

 

Log Name: Application

Source: MSExchange Unified Messaging

Date: 10/31/2008 6:28:26 AM

Event ID: 1028

Task Category: UMCore

Level: Information

Keywords: Classic

User: N/A

Computer: OIM-LAX-UMS-002.omegaidentitymedia.net

Description:

The fax call from "7515" for "Jeremiah L. Maudlin" at number "7515" was received but no pages were received. The fax call was 48.7017504 seconds long. The fax call was received from UM IP gateway "192.168.12.126".

<Provider Name="MSExchange Unified Messaging" />

<EventID Qualifiers="32772">1028</EventID>

<Level>4</Level>

<Task>2</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2008-10-31T13:28:26.000Z" />

<EventRecordID>18101</EventRecordID>

<Channel>Application</Channel>

<Computer>OIM-LAX-UMS-002.omegaidentitymedia.net</Computer>

<Security />

</System>

<EventData>

<Data>7515</Data>

<Data>Jeremiah L. Maudlin</Data>

<Data>7515</Data>

<Data>48.7017504</Data>

<Data>192.168.12.126</Data>

</EventData>

</Event>

 

Alas, no fax in my inbox, an agry PSTN fax machine that says "would you give it up already!" and starts beeping at me, and one confused IT guy sitting at his desk shaking his head and ever so hopeful that a forum post will lead to his rescue. :P

 

A couple other quick items of note:

Exchange 2007 SP1 UM, CA, MB, and HT roles all on 4 seperate servers

PBXnSIP 3.0.3037 w/ Permanent License, 3 Trunks, a number of accounts, 1 Dial Plan

Fully OCS Integrated w/o issue (horray! thanks to pbxnsip dev & Jan B. for excellent work!)

Callcentric SIP Trunk w/ ~30 DIDs

Exchange globalcfg.xml file changes:

<EnableInbandFaxDetection>true</EnableInbandFaxDetection>

<UseT38UDPRedundancyForFax>true</UseT38UDPRedundancyForFax>

(As for two items above, I have tried various combinations of true/false, and this seems to get me closest to success)

 

I've also attached the complete PBXnSIP log (Level 9) to this post for review from a failed Fax call just a few moments ago. Thanks in advance to all, it is most appreciated!

SIPLogT38Failure.txt

Share this post


Link to post
Share on other sites

Hello JaeJay,

 

with Service Pack 1 for Exchange 2007 or one of its terrible RollUp Packages one, two or 3, or 4 for SP1 (isnt it a horror for all exchange admins? :D , incl. me) T38 FAX is broken or unreliable again, like in the Beta-Times (2006).

 

Even the big manufactures for certified gateway's have this problem. AudioCodes, Dialogic and Ferrari-Electronic confirm that it was working perfect before SP1 with the RTM version.

 

I tested it with pbxnsip for days, then tried it directly with our AudioCodes Mediant 1000 to Exchange UM. But no way :P .

 

MS is working on a new fix.

 

But there is also another thing suspected causing T.38 Exchang UM problems called Microsoft Forefront for Exchange, which is a antivirus scanner for Exchange 2007.

 

At the moment we have to wait :( till MS is finishing its homework...

 

Please try following Johann Deutinger (Ferrari-Electronic) | MCTS Exchange 2007 / OCS 2007 in the Microsoft Technet Forums here

 

http://forums.microsoft.com/TechNet/ShowPo...0&SiteID=17

 

He is a legend in FAX integration! And he is one of the most active persons pressing MS to get this issues fixed :)

 

Best regards,

 

Jan

Share this post


Link to post
Share on other sites

We are running rollup 7 and having the same issues. We have tried 4 different carriers as well as a t.38 fax locally.

 

I see the t.38 establish but it fails like above... does anyone have Exchange t.38 fax working? anyone?

Share this post


Link to post
Share on other sites
We are running rollup 7 and having the same issues. We have tried 4 different carriers as well as a t.38 fax locally.

 

I see the t.38 establish but it fails like above... does anyone have Exchange t.38 fax working? anyone?

 

We are working on a solution that transcodes inband into RFC4733 DTMF. In theory it is working, but in the real life we still have problems. Stay tuned, we want to include this into the 3.3.2 build.

Share this post


Link to post
Share on other sites
We are working on a solution that transcodes inband into RFC4733 DTMF. In theory it is working, but in the real life we still have problems. Stay tuned, we want to include this into the 3.3.2 build.

 

This is awesome news!!! Can't wait to give it a test run when you guys' have finished. Thanks!!!

Share this post


Link to post
Share on other sites
T.38 is not supported in Exchange 2010... FYI might be a dead item for development.

 

:( Is that the end of FAX? How else would they transport FAX reliably? I would open a bottle if there is something that actually works without headaches and can even be run through SRTP (secure FAX!!!).

Share this post


Link to post
Share on other sites

How's this looking :-D Still hoping, fingers crossed, eyes crossed, toes crossed, that this is still on the roadmap from you guys! Is this inclusion in 3.3.2 still a possibility? :lol:

 

Thanks!

 

We are working on a solution that transcodes inband into RFC4733 DTMF. In theory it is working, but in the real life we still have problems. Stay tuned, we want to include this into the 3.3.2 build.

Share this post


Link to post
Share on other sites
How's this looking :-D Still hoping, fingers crossed, eyes crossed, toes crossed, that this is still on the roadmap from you guys! Is this inclusion in 3.3.2 still a possibility? :lol:

 

Thanks!

 

Transcoding feature has been successfully added and tested in couple of beta sites already. Yes, it will be in the new 3.x release.

Share this post


Link to post
Share on other sites

Need another beta site? :lol:

 

Transcoding feature has been successfully added and tested in couple of beta sites already. Yes, it will be in the new 3.x release.

Share this post


Link to post
Share on other sites

Not sure what to tell you I see T38 being passed. But MS T38 message are missing alot of info.

We are just going to use a different application for T38.. Seeing how T38 is not supported in Exchange 2010 and not working properly we are not going to use Exchange for fax anymore.

Share this post


Link to post
Share on other sites
what FAX solution do you advise to use with PBXnSIP integrated in OCS 2007 R2?

 

Well, if you want to use Microsoft stuff then you probably need to check out Exchange. Otherwise

there is FAX software, for example faxback (see

http://www.pbxnsip.com/news/pbxnsip-faxback.php,

http://kb.faxback.com/HOWTO+-+pbxnsip+Integration,

http://forum.pbxnsip.com/index.php?showtopic=1358,

http://forum.pbxnsip.com/index.php?showtopic=1316).

Share this post


Link to post
Share on other sites
Well, if you want to use Microsoft stuff then you probably need to check out Exchange. Otherwise

there is FAX software, for example faxback (see

http://www.pbxnsip.com/news/pbxnsip-faxback.php,

http://kb.faxback.com/HOWTO+-+pbxnsip+Integration,

http://forum.pbxnsip.com/index.php?showtopic=1358,

http://forum.pbxnsip.com/index.php?showtopic=1316).

 

Ok, Thank you!

Share this post


Link to post
Share on other sites

Hello!

I install faxback and I have a trouble with recieving faxes. I try to send fax from analog fax-sip provider (with T.38) - pbxnsip - NET SatisFAXtion

here is a log:

 

1.1.1.3 - faxback

1.1.1.5 - pbxnsip

1.1.1.101 - sip provider

 

[7] 2010/02/05 08:28:11: Last message repeated 2 times

[6] 2010/02/05 08:28:11: Received DTMF F

[7] 2010/02/05 08:28:11: Attendant: Calling extension 777

[7] 2010/02/05 08:28:11: SIP Tx udp:1.1.1.3:5060:

INVITE sip:777@1.1.1.3:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport

From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

To: <sip:777@pbx.case.ru>

Call-ID: 6ec1ef94@pbx

CSeq: 21702 INVITE

Max-Forwards: 70

Contact: <sip:777@1.1.1.5:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

Alert-Info: <http://127.0.0.1/Bellcore-dr3>

Content-Type: application/sdp

Content-Length: 327

 

v=0

o=- 13668 13668 IN IP4 1.1.1.5

s=-

c=IN IP4 1.1.1.5

t=0 0

m=audio 63512 RTP/AVP 0 8 9 18 2 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:18 g729/8000

a=fmtp:18 annexb=no

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[7] 2010/02/05 08:28:11: SIP Rx udp:1.1.1.3:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport

From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

Call-ID: 6ec1ef94@pbx

CSeq: 21702 INVITE

Contact: <sip:IPFax@1.1.1.3:5060>

User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929

Content-Length: 0

 

 

[7] 2010/02/05 08:28:11: SIP Rx udp:1.1.1.3:5060:

SIP/2.0 180 Ringing

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport

From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

Call-ID: 6ec1ef94@pbx

CSeq: 21702 INVITE

Contact: <sip:IPFax@1.1.1.3:5060>

User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929

Content-Length: 0

 

 

[7] 2010/02/05 08:28:11: SIP Rx udp:1.1.1.3:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-77d89e821eab1998222b24bcb014ca34;rport

From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

Call-ID: 6ec1ef94@pbx

CSeq: 21702 INVITE

Contact: <sip:IPFax@1.1.1.3:5060>

User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929

Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY

Content-Type: application/sdp

Content-Length: 210

 

v=0

o=IPFax 0 0 IN IP4 1.1.1.3

s=SIP Fax Call

i=IPFax

c=IN IP4 1.1.1.3

t=0 0

m=audio 49248 RTP/AVP 0 101

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:20

a=sendrecv

 

[7] 2010/02/05 08:28:11: Call 6ec1ef94@pbx#5943: Clear last INVITE

[7] 2010/02/05 08:28:11: Set packet length to 20

[6] 2010/02/05 08:28:11: Send codec=pcmu/8000 afrer answer

[6] 2010/02/05 08:28:11: Sending RTP for 6ec1ef94@pbx#5943 to 1.1.1.3:49248

[7] 2010/02/05 08:28:11: SIP Tx udp:1.1.1.3:5060:

ACK sip:IPFax@1.1.1.3:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-37ac123baf4fee949d4eaf868c72d713;rport

From: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

To: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

Call-ID: 6ec1ef94@pbx

CSeq: 21702 ACK

Max-Forwards: 70

Contact: <sip:777@1.1.1.5:5060;transport=udp>

Content-Length: 0

 

 

[7] 2010/02/05 08:28:11: Determine pass-through mode after receiving response

[7] 2010/02/05 08:28:11: 6ec1ef94@pbx#5943: RTP pass-through mode

[7] 2010/02/05 08:28:11: 7007803330339123745-1265347685@172.30.77.25#f72475646e: RTP pass-through mode

[7] 2010/02/05 08:28:11: 7007803330339123745-1265347685@172.30.77.25#f72475646e: Media-aware pass-through mode

[7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.3:5060:

INVITE sip:8632370680@pbx.case.ru:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011

From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

Call-ID: 6ec1ef94@pbx

CSeq: 21703 INVITE

Max-Forwards: 70

Contact: <sip:777@1.1.1.3:5060>

User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929

Session-Expires: 3600;refresher=uas

Supported: timer,replaces,billing,presence,*

Allow: INVITE, ACK, BYE, CANCEL, REFER, NOTIFY

Content-Type: application/sdp

Content-Length: 347

 

v=0

o=IPFax 0 1 IN IP4 1.1.1.3

s=SIP Fax Call

i=IPFax

c=IN IP4 1.1.1.3

t=0 0

m=image 49200 udptl t38

a=T38FaxVersion:0

a=T38MaxBitRate:14400

a=T38FaxRateManagement:transferredTCF

a=T38FaxMaxBuffer:200

a=T38FaxMaxDatagram:72

a=T38FaxFillBitRemoval:0

a=T38FaxTranscodingMMR:0

a=T38FaxTranscodingJBIG:0

a=T38FaxUdpEC:t38UDPRedundancy

 

[0] 2010/02/05 08:28:15: UDP: bind() to port 54900 failed

[7] 2010/02/05 08:28:15: UDP: Opening socket on :57948

[7] 2010/02/05 08:28:15: UDP: Opening socket on :57140

[7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.101:5060:

INVITE sip:8632370680@1.1.1.101:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-290b90ac185fe1cdcaf1380f07c14040;rport

From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 27403 INVITE

Max-Forwards: 70

Contact: <sip:2688634@1.1.1.5:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

Content-Type: application/sdp

Content-Length: 331

 

v=0

o=- 54151 54152 IN IP4 1.1.1.5

s=-

c=IN IP4 1.1.1.5

t=0 0

m=image 57140 udptl t38

a=T38FaxVersion:0

a=T38MaxBitRate:14400

a=T38FaxRateManagement:transferredTCF

a=T38FaxMaxBuffer:200

a=T38FaxMaxDatagram:72

a=T38FaxFillBitRemoval:0

a=T38FaxTranscodingMMR:0

a=T38FaxTranscodingJBIG:0

a=T38FaxUdpEC:t38UDPRedundancy

 

[7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.3:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011

From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

Call-ID: 6ec1ef94@pbx

CSeq: 21703 INVITE

Content-Length: 0

 

 

[7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.101:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 1.1.1.5:5060;received=1.1.1.5;branch=z9hG4bK-290b90ac185fe1cdcaf1380f07c14040;rport=5060

From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 27403 INVITE

 

 

[5] 2010/02/05 08:28:15: Passthrough: Changing destination

[7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.101:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 1.1.1.5:5060;received=1.1.1.5;branch=z9hG4bK-290b90ac185fe1cdcaf1380f07c14040;rport=5060

From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 27403 INVITE

Content-Type: application/sdp

Contact: <sip:8632370680@1.1.1.101:5060;transport=udp>;user=phone

Supported: timer,100rel

Content-Length: 103

 

v=0

o=MG4000|2.0 3420 6706 IN IP4 1.1.1.101

s=-

c=IN IP4 1.1.1.101

t=0 0

m=image 52860 udptl t38

 

[7] 2010/02/05 08:28:15: Call 7007803330339123745-1265347685@172.30.77.25#f72475646e: Clear last INVITE

[7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.3:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011

From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

Call-ID: 6ec1ef94@pbx

CSeq: 21703 INVITE

Contact: <sip:777@1.1.1.5:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.4.0.3201

Content-Type: application/sdp

Content-Length: 92

 

v=0

o=- 13668 13669 IN IP4 1.1.1.5

s=-

c=IN IP4 1.1.1.5

t=0 0

m=image 57948 udptl t38

 

[7] 2010/02/05 08:28:15: SIP Tx udp:1.1.1.101:5060:

ACK sip:8632370680@1.1.1.101:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-91155c8a0f5db5c3c077e16dd28ac96c;rport

From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 27403 ACK

Max-Forwards: 70

Contact: <sip:2688634@1.1.1.5:5060;transport=udp>

Content-Length: 0

 

 

[7] 2010/02/05 08:28:15: Determine pass-through mode after receiving response

[7] 2010/02/05 08:28:15: SIP Rx udp:1.1.1.3:5060:

ACK sip:777@1.1.1.5:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1011

From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

Call-ID: 6ec1ef94@pbx

CSeq: 21703 ACK

Max-Forwards: 70

User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929

Content-Length: 0

 

 

[5] 2010/02/05 08:28:26: SIP port accept from 1.1.7.8:63891

[7] 2010/02/05 08:28:26: SIP Rx tcp:1.1.7.8:63891:

OPTIONS sip:1.1.1.5:5060 SIP/2.0

FROM: <sip:s-caseexch.case.ru:5060;transport=Tcp;ms-opaque=2cb7e09927aa4652>;epid=FC0ADCD96D;tag=b9a0d84671

TO: <sip:1.1.1.5:5060>

CSEQ: 18599 OPTIONS

CALL-ID: b819daf2a97c490ebf7d55910cc06236

MAX-FORWARDS: 70

VIA: SIP/2.0/TCP 1.1.7.8:63891;branch=z9hG4bK27c8619a

ACCEPT: application/sdp

CONTENT-LENGTH: 0

USER-AGENT: RTCC/3.1.0.0

 

 

[7] 2010/02/05 08:28:26: SIP Tx tcp:1.1.7.8:63891:

SIP/2.0 200 Ok

Via: SIP/2.0/TCP 1.1.7.8:63891;branch=z9hG4bK27c8619a

From: <sip:s-caseexch.case.ru:5060;transport=Tcp;ms-opaque=2cb7e09927aa4652>;tag=b9a0d84671;epid=FC0ADCD96D

To: <sip:1.1.1.5:5060>;tag=f7ce52c8fc

Call-ID: b819daf2a97c490ebf7d55910cc06236

CSeq: 18599 OPTIONS

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Content-Length: 0

 

 

[7] 2010/02/05 08:28:30: SIP Rx udp:1.1.1.101:5060:

INVITE sip:2688634@1.1.1.5:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1

Call-ID: 7007803330339123745-1265347685@172.30.77.25

From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

Content-Type: application/sdp

CSeq: 2 INVITE

Contact: <sip:8632370680@1.1.1.101:5060;transport=udp>;user=phone

Allow: INVITE,CANCEL,BYE,ACK,REFER,UPDATE,INFO

Supported: timer,100rel

Max-Forwards: 69

Content-Length: 222

 

v=0

o=MG4000|2.0 3420 6707 IN IP4 1.1.1.101

s=-

c=IN IP4 1.1.1.101

t=0 0

m=audio 52860 RTP/AVP 0 101 13

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=silenceSupp:off - - - -

a=ptime:20

a=rtpmap:13 CN/8000

 

[7] 2010/02/05 08:28:30: Set packet length to 20

[7] 2010/02/05 08:28:30: SIP Tx udp:1.1.1.101:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1

From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 2 INVITE

Content-Length: 0

 

 

[6] 2010/02/05 08:28:41: SIP TCP/TLS timeout on 1.1.1.4:41773, closing connection

[7] 2010/02/05 08:28:57: SIP Rx udp:1.1.1.3:5060:

BYE sip:777@1.1.1.5:5060 SIP/2.0

Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1012

From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

Call-ID: 6ec1ef94@pbx

CSeq: 21704 BYE

Max-Forwards: 70

User-Agent: Net Satisfaxtion/IP_FAX-8.5.4225.929

Content-Length: 0

 

 

[7] 2010/02/05 08:28:57: SIP Tx udp:1.1.1.3:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 1.1.1.3:5060;branch=z9hG4bK1012

From: <sip:777@pbx.case.ru>;tag=IPF_PORT_0024_1010

To: <sip:8632370680@pbx.case.ru:5060;user=phone>;tag=5943

Call-ID: 6ec1ef94@pbx

CSeq: 21704 BYE

Contact: <sip:777@1.1.1.5:5060;transport=udp>

User-Agent: pbxnsip-PBX/3.4.0.3201

RTP-RxStat: Dur=46,Pkt=734,Oct=43912,Underun=0

RTP-TxStat: Dur=46,Pkt=910,Oct=155327

Content-Length: 0

 

 

[7] 2010/02/05 08:28:57: Other Ports: 1

[7] 2010/02/05 08:28:57: Call Port: 7007803330339123745-1265347685@172.30.77.25#f72475646e

[7] 2010/02/05 08:28:57: SIP Tx udp:1.1.1.101:5060:

BYE sip:8632370680@1.1.1.101:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 1.1.1.5:5060;branch=z9hG4bK-8c7f32049f3c81d47cc43e0eea58e3a2;rport

From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 27404 BYE

Max-Forwards: 70

Contact: <sip:2688634@1.1.1.5:5060;transport=udp>

RTP-RxStat: Dur=52,Pkt=1210,Oct=206927,Underun=0

RTP-TxStat: Dur=42,Pkt=3162,Oct=461528

Content-Length: 0

 

 

[7] 2010/02/05 08:28:57: SIP Rx udp:1.1.1.101:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 1.1.1.5:5060;received=1.1.1.5;branch=z9hG4bK-8c7f32049f3c81d47cc43e0eea58e3a2;rport=5060

From: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

To: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 27404 BYE

Contact: <sip:8632370680@1.1.1.101:5060;transport=udp>;user=phone

Supported: timer,100rel

Content-Length: 0

 

 

[7] 2010/02/05 08:28:57: Call 7007803330339123745-1265347685@172.30.77.25#f72475646e: Clear last request

[5] 2010/02/05 08:28:57: BYE Response: Terminate 7007803330339123745-1265347685@172.30.77.25

[7] 2010/02/05 08:29:02: SIP Rx udp:1.1.1.101:5060:

CANCEL sip:2688634@1.1.1.5:5060;transport=udp SIP/2.0

Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1

CSeq: 2 CANCEL

Call-ID: 7007803330339123745-1265347685@172.30.77.25

From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

Max-Forwards: 69

Content-Length: 0

 

 

[7] 2010/02/05 08:29:02: SIP Tx udp:1.1.1.101:5060:

SIP/2.0 481 Call/Transaction Does Not Exist

Via: SIP/2.0/UDP 1.1.1.101:5060;branch=z9hG4bK5jh8d610700gvec8h7g0.1

From: <sip:8632370680@1.1.1.101:5060;user=phone>;tag=26237

To: <sip:2688634@1.1.1.5:5060;user=phone>;tag=f72475646e

Call-ID: 7007803330339123745-1265347685@172.30.77.25

CSeq: 2 CANCEL

Content-Length: 0

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...