fonny Posted April 2, 2013 Report Share Posted April 2, 2013 SnonONE v5.0.7 MacOS & Patton SmartNode 4554 When setup with voicemailbox enabled I am redirected to the right mailbox and message is delivered to the configured mailaddress. With voicemailbox set to FAX I get an error "488 Not Acceptable Here." v=0 o=- 1752513057 1752513058 IN IP4 192.168.1.103 s=- c=IN IP4 192.168.1.103 t=0 0 m=image 56890 udptl t38 a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPRedundancy [5] 2013/04/02 17:45:37: SIP Rx udp:192.168.1.9:5060: SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 192.168.1.103:5060;branch=z9hG4bK-b077e69e5a22086611f4541e5dd92bc7;rport=5060;received=192.168.1.103 From: <sip:034441972@192.168.1.103:5060>;tag=39e2561067 To: <sip:anonymous@192.168.1.103:5060>;tag=380fd4226b Call-ID: 8fcf9e7c4800232d CSeq: 7365 INVITE Server: Patton SN4554 2BIS EUI 00A0BA063AA5 R5.7 2011-03-10 SIP M5T SIP Stack/4.0.30.30 Content-Length: 0 Any idea what can be wrong here? SnomONE, Patton trace & trunk settings attached snomone_trace2.txt patton_sn4554_trace2.txt trunk_settings.txt Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 2, 2013 Report Share Posted April 2, 2013 Hmm. Almost looks like FAX is not enabled on the gateway. The traces look "beautiful". AFAIK other Patton installations do work fine with FAX and T.38. Quote Link to comment Share on other sites More sharing options...
fonny Posted April 3, 2013 Author Report Share Posted April 3, 2013 Hmm. Almost looks like FAX is not enabled on the gateway. The traces look "beautiful". AFAIK other Patton installations do work fine with FAX and T.38. Here the Patton config. Any idea of firmware rev. of the other Patton installations? 20130401_patton.txt Quote Link to comment Share on other sites More sharing options...
Steve B Posted April 3, 2013 Report Share Posted April 3, 2013 First thing that jumped out at me was you have the G729 Codec as number 1, that would compress the audio if I am not mistaken... Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 3, 2013 Report Share Posted April 3, 2013 Can't really say anything about Patton... However the PBX does attempt to switch to T.38, so a lot of things went right before this step. The G729 codec cannot be the problem. I don't understand why Patton would reject the T.38 re-INVITE. Maybe there is a way to get a more detailed log from the gateway why it does that. Quote Link to comment Share on other sites More sharing options...
fonny Posted April 4, 2013 Author Report Share Posted April 4, 2013 Thanks to the great support of Patton, the mistery is solved. It's great to define an alternate voip profile but doesn't help when you don't use it ;( in 'context cs interface sip' it missed the line 'use profile voip VOIP'. The gateway was always using the default voip profile which only allowed g711 but no t38. Attached the running config if it can help someone. 20130404_patton.txt Quote Link to comment Share on other sites More sharing options...
Vodia support Posted April 4, 2013 Report Share Posted April 4, 2013 Thanks for the contribution. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.