Pretty sure it needs to be set as an allowed codec under system >> servers
>> <server> >> SIP Trunking >> SIP

try blanking out the codec settings and then restarting necessary services.
if it works after you do that then it's a codec issue. Not sure what codec
to put in that text box though...

On Mon, Aug 29, 2011 at 11:18 AM, Tony Graziano <
[email protected]> wrote:

> ha ha voxitas.
>
> darn phone.
>
> voxitas sends to you with t .38. if you don't support t .38 on your gateway
> it will not work.
>
> I can send and receive and by receiving both to a plain paper for paperless
> fax in sipx with no problem.
>
> g711 will get you nowhere
>  On Aug 29, 2011 11:31 AM, "Tony Graziano" <[email protected]>
> wrote:
> > moxie pest works without a problem
> > On Aug 29, 2011 11:29 AM, "Ly Tran" <[email protected]> wrote:
> >> Well, Voxitas finally got our DIDs that we have set aside for faxing
> > "configured" for t.38 faxing. I'm not sure what that all meant, since we
> > already had the DIDs for over a year. They said they had to port it over
> > from Verizon to L3. It took over a month... and yet we still can't get an
> > inbound fax through. Anyone know of a faxing service that uses t.38 that
> we
> > can use to test faxing to ours? Unfortunately, we can't use our internal
> fax
> > since our ata doesn't support t.38.
> >>
> >> Ly Tran
> >>
> >> From: [email protected] [mailto:
> > [email protected]] On Behalf Of Tony Graziano
> >> Sent: Thursday, July 21, 2011 2:27 PM
> >> To: Discussion list for users of sipXecs software
> >> Subject: Re: [sipx-users] T.38 Faxing on SipX 4.4 Setup
> >>
> >> Eh. I depends on whether or not the ITSp guarantees inbound or outbound
> > routes to t.38 for you.
> >>
> >> This is a discussion about itsp declarations and what they do or dont
> do.
> >>
> >> If the itsp originates or terminates the call via a PRI in their control
> > and tunrs it into t.30 at the handoff to your system, it is essentially
> 100%
> > t.38 and "should convert' everything in either direction if they have
> good
> > enough mojo.
> >>
> >> BUT this was about a particular t.38 codec not being accepted by an
> itsp,
> > probably because it had not been turned on in the itsp account.
> >>
> >> I have started testing with one carrier last week and am testing with
> > another one this week. When I have successful results and how-to's they
> will
> > be posted. That's really a different thread though.
> >>
> >>
> >> On Thu, Jul 21, 2011 at 2:59 PM, Jeff Gilmore <[email protected]
> > <mailto:[email protected]>> wrote:
> >> I had a problem like this on outbound faxing on a pre-4.4 version, and I
> > found that it depended on what number I called whether or not I could get
> > T38.
> >>
> >> I spoke to my ITSP and they said that their equipment supports T38, but
> > that they have peering arrangements with various carriers to various
> > locations. Some of those peerings were SIP based, and some of them don't
> > support T38.
> >>
> >> So I could get T38 when calling a fax located in my ITSPs office, but
> not
> > to some phone numbers elsewhere (but the call would go through as G711U
> and
> > work most of the time).
> >>
> >> It is possible that your fax machine's originating number is served by
> > someone between you and your sipX box that doesn't handle T38.
> >>
> >> Jeff
> >>
> >> On Jul 20, 2011, at 7:37 PM, Tony Graziano wrote:
> >>
> >>
> >> I dunno what a netlogic switch is. It doesn't matter.
> >>
> >> They send the invite in g711, we send a reinvite in t.38.
> >>
> >> Look at frame 26, reinvite t.38.
> >>
> >> Now look at frame 30. They don't accept the codec. 488 not acceptable
> > simply means a codec we are asking for (only t.38 in the re-invite) is
> not
> > in their list.
> >>
> >> Either they do not support t.38 OR reinvite, or don't have the account
> > configured properly. Up to the 488 there is nothing wrong with any of the
> > transaction at all.
> >>
> >>
> >> On Wed, Jul 20, 2011 at 6:28 PM, Ly Tran <[email protected]<mailto:
> > [email protected]>> wrote:
> >> Attached is a capture of a fax call using t.38. Can someone shed some
> > light on what may be happening? Not sure what the "488 Not acceptable
> here".
> > Appears that ITSP may be using Asterisk?
> >>
> >> From: [email protected]<mailto:
> > [email protected]> [mailto:
> > [email protected]<mailto:
> > [email protected]>] On Behalf Of Tony Graziano
> >>
> >> Sent: Tuesday, July 19, 2011 5:01 AM
> >> To: Discussion list for users of sipXecs software
> >> Subject: Re: [sipx-users] T.38 Faxing on SipX 4.4 Setup
> >>
> >>
> >> the fax did goes in unified messaging and only appears if an email
> address
> > is entered. you need to create a fax "line" and DID there.
> >>
> >> i.e. user 200, unified messaging FAX is 300 and DID is
> > 19725551212<tel:19725551212>
> >>
> >> sipx does t.38, which means the itsp needs to send the call using t.38
> or
> > send it g.711 and upon hearing CED tone from sipx, send a re-invite for
> > t.38. If the ITSP is using a SONUS switch you will likely not ever get a
> > successful fax either it seems.
> >>
> >> i would suggest a call trace or a sofia.log in debug if your itsp says
> > they are sending in t.38 and you have completion issues. Calling from a
> cell
> > SHOULD go silent after a few seconds, there is no CED confirmation from a
> > cellphone.
> >>
> >> who is the itsp?
> >> On Mon, Jul 18, 2011 at 11:51 AM, Ly Tran <[email protected]<mailto:
> > [email protected]>> wrote:
> >> Question about T.38 faxing on the new 4.4 SipX version. We just did an
> > update from 4.2 and voice is working correctly. Our ITSP has T.38
> support.
> > Is there anything
> >> Specific we have to do to configure faxing besides assigning an
> > extension/DID to a user profile? Do we also have to create a user in SipX
> > with this extension/DID alias?
> >> I tried a test fax to the DID assigned to my user account and it does
> not
> > complete. Tried dialing the DID with a mobile phone to see if I get the
> fax
> > tones, but it sounds
> >> Like it is incomplete... get what sounds like the start of nego (a beep)
> > then the call drops.
> >>
> >> Ly Tran
> >>
> >> _______________________________________________
> >> sipx-users mailing list
> >> [email protected]<mailto:[email protected]>
> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>
> >>
> >>
> >> --
> >> ======================
> >> Tony Graziano, Manager
> >> Telephone: 434.984.8430<tel:434.984.8430>
> >> sip: [email protected]<mailto:
> > [email protected]>
> >> Fax: 434.326.5325<tel:434.326.5325>
> >>
> >> Email: [email protected]<mailto:[email protected]
> >
> >>
> >> LAN/Telephony/Security and Control Systems Helpdesk:
> >> Telephone: 434.984.8426<tel:434.984.8426>
> >> sip: [email protected]<mailto:
> > [email protected]>
> >>
> >> Helpdesk Contract Customers:
> >> http://support.myitdepartment.net<http://support.myitdepartment.net/>
> >>
> >> Blog:
> >> http://blog.myitdepartment.net<http://blog.myitdepartment.net/>
> >>
> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> >>
> >>
> >> _______________________________________________
> >> sipx-users mailing list
> >> [email protected]<mailto:[email protected]>
> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>
> >>
> >>
> >> --
> >> ======================
> >> Tony Graziano, Manager
> >> Telephone: 434.984.8430<tel:434.984.8430>
> >> sip: [email protected]<mailto:
> > [email protected]>
> >> Fax: 434.326.5325<tel:434.326.5325>
> >>
> >> Email: [email protected]<mailto:[email protected]
> >
> >>
> >> LAN/Telephony/Security and Control Systems Helpdesk:
> >> Telephone: 434.984.8426<tel:434.984.8426>
> >> sip: [email protected]<mailto:
> > [email protected]>
> >>
> >> Helpdesk Contract Customers:
> >> http://support.myitdepartment.net<http://support.myitdepartment.net/>
> >>
> >> Blog:
> >> http://blog.myitdepartment.net<http://blog.myitdepartment.net/>
> >>
> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> >>
> >> _______________________________________________
> >> sipx-users mailing list
> >> [email protected]<mailto:[email protected]>
> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>
> >>
> >> _______________________________________________
> >> sipx-users mailing list
> >> [email protected]<mailto:[email protected]>
> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> >>
> >>
> >>
> >> --
> >> ======================
> >> Tony Graziano, Manager
> >> Telephone: 434.984.8430
> >> sip: [email protected]<mailto:
> > [email protected]>
> >> Fax: 434.326.5325
> >>
> >> Email: [email protected]<mailto:[email protected]
> >
> >>
> >> LAN/Telephony/Security and Control Systems Helpdesk:
> >> Telephone: 434.984.8426
> >> sip: [email protected]<mailto:
> > [email protected]>
> >>
> >> Helpdesk Contract Customers:
> >> http://support.myitdepartment.net
> >>
> >> Blog:
> >> http://blog.myitdepartment.net
> >>
> >> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> >>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
Josh Patten
eZuce
Solutions Architect
O.978-296-1005 X2050
M.979-574-5699
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to