Rightfax and t.38 integration

[sasha611v]

Is there any interop doc that show how to integrate a rightfax with the mitel 3300? I am working on an issue where mitel is returning 503 service unavailable on outbound t.38 faxes however inbound is working fine. I cant find any documentation to verify that I have this setup correctly

When I sniff the traffic between the 3300 and rightfax I see this but do not see anything in mitels logs regarding sip errors. Can anyone decipher any reason for the 503 service unavailable based off of this? Running MCD ver 10

10.0.1.20 = Rightfax
10.0.1.25 = Mitel


INVITE sip:5555555555@10.0.1.25:5060 SIP/2.0
From: 9724194000 <sip:9725554000@10.0.1.20>;tag=8b17090-1401000a-13c4-55013-28aa0-1bbe2d99-28aa0
To: <sip:94697421275@10.0.1.25:5060>
Call-ID: 8296f98-1401000a-13c4-55013-28aa0-55bac64b-28aa0
CSeq: 1 INVITE
Via: SIP/2.0/UDP 10.0.1.20:5060;branch=z9hG4bK-28aa0-9ed8466-174777
Contact: <sip:10.0.1.20:5060>
Max-Forwards: 70
User-Agent: Brktsip/6.5.2B5 (Dialogic)
Content-Type: application/sdp
Content-Length: 209

v=0
o=- 2209159146 0322327000 IN IP4 10.0.1.20
s=no_session_name
t=0 0
m=audio 56476 RTP/AVP 0
c=IN IP4 10.0.1.20
a=rtpmap:0 pcmu/8000
m=audio 56476 RTP/AVP 8
c=IN IP4 10.0.1.20
a=rtpmap:8 pcma/8000
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.0.1.20:5060;branch=z9hG4bK-28aa0-9ed8466-174777
From: 9724194000 <sip:9725554000@10.0.1.20>;tag=8b17090-1401000a-13c4-55013-28aa0-1bbe2d99-28aa0
To: <sip:5555555555@10.0.1.25:5060>;tag=0_1175638944-93275789
Call-ID: 8296f98-1401000a-13c4-55013-28aa0-55bac64b-28aa0
CSeq: 1 INVITE
Content-Length: 0

SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 10.0.1.20:5060;branch=z9hG4bK-28aa0-9ed8466-174777
From: 9724194000 <sip:9725554000@10.0.1.20>;tag=8b17090-1401000a-13c4-55013-28aa0-1bbe2d99-28aa0
To: <sip:94697421275@10.0.1.25:5060>;tag=0_1175638944-93275789
Call-ID: 8296f98-1401000a-13c4-55013-28aa0-55bac64b-28aa0
CSeq: 1 INVITE
Contact: <sip:10.0.1.25>
Server: Mitel-3300-ICP 10.2.1.13
Content-Length: 0

ACK sip:5555555555@10.0.1.25:5060 SIP/2.0
From: 9724194000 <sip:9724194000@10.0.1.20>;tag=8b17090-1401000a-13c4-55013-28aa0-1bbe2d99-28aa0
To: <sip:94697421275@10.0.1.25:5060>;tag=0_1175638944-93275789
Call-ID: 8296f98-1401000a-13c4-55013-28aa0-55bac64b-28aa0
CSeq: 1 ACK
Via: SIP/2.0/UDP 10.0.1.20:5060;branch=z9hG4bK-28aa0-9ed8466-174777
Contact: <sip:10.0.1.20:5060>
Max-Forwards: 70
User-Agent: Brktsip/6.5.2B5 (Dialogic)
Content-Length: 0

 

[LoopyLou]

Mitel has a SIP document which lists all the devices they have tested and have config notes for. You will have to get it from Mitel on Line and check for your product. Not great on SIP but my question would be do you have T.38 licenses on the 3300? 503 service unavailable could be saying you are asking for a t.38 connnection to the 3300 and it can't deliver because it either doesn't have t.38 licensing or it doesn't have the additional DSP resources the t.38 needs. That's all the assistance I can lend.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[sasha611v]

Thanks, it gets me started in the right direction. Im pretty sure we are good on the licensing but will start looking down the dsp path on this.