similar to: Can not calculate far_max_ifp before far_max_datagram has been set

Hello, I need help to solve a problem that I am having using Asterisk 13, PJSIP and T38. My setup is as follows: SIP Provider --> Asterisk 13 --> Patton --> Physical Fax I need to get the fax directly in T38 to Patton. The provider sends me the fax in T38. If I receive the T38 fax on Asterisk (using an hylafax device), I can properly receive the fax. If I send a T38 fax with Asterisk

On 06/04/2017 at 01:41 PM Telium Technical Support wrote: > Just a guess (without knowing about your network), but are the two ends > points on public networks and visible to one another? If not the reinvite > may be passing an internal (nat'ed) address to the other and the connection > will fail...just a though t38modem -tt -o /var/log/t38modem.log --no-h323 -u 91 --sip-listen

On 1 July 2016 at 17:41, Joshua Colp <jcolp at digium.com> wrote: > > >> exten => 1234,Set(CALLERID(all)="Jon Doe" <+123456789>) >> same => n,Dial(PJSIP/phone123, 30) >> > > Your exten line has no priority, is that how it is in your dialplan? > Actually no, I stole that line from an earlier email to this list. Mine has a priority.

Hello! I'm trying to send a fax via T.38 to a destination, which should be T.38 capable. My provider supports T.38, too. Unfortunately, it doesn't work. This means: Call is started and SDP is negotiated w/ alaw. Callee sends reinvite - for alaw again (and not for T.38)!! After about 30s, callee hangs up because of missing data (this is true, because I don't send alaw coded fax data.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, 2 weks ago I asked questions about PJSIP and T.38 but got no replies. I upgraded Asterisk to git as of yesterday (309dd2a), and I'm still having the same issues. In the trace below, I'm sending a fax from Hylafax server through iaxmodem on Asterisk-13 (tiare) to a second Asterisk (11.18.0 t0gw) connected to the PSTN via ISDN; the

I upgraded our Asterisk 13 LTS to Asterisk 16 Certified 16.8 yesterday and converted form SIP to PJSIP using the python script as a start and then mofiying from there.  I ran into an issue when testing that incoming calls from MagicJack would go silent after about 10 seconds.  This happened while in the automated attendant area.  This problem did not occur with Asterisk 13 LTS.  I reverted PJSIP

Hi, Got problems with incoming SIP calls. Scenario: Server1: 3cx or any other server Server2: Asterisk 16.2.1 . PJPROJECT 2.8 Server2 registers on Server1 with SIP ID 1121. Registration is OK. Server2 outgoing calls are OK. INVITE, unauthorized, INVITE with password, OK, RINGING,... Troubles with incoming calls / incoming INVITE's . I can not identify endpoint by IP, I have multiple

Hi, I'm using Asterisk 13.x and have defined a pjsip TCP IPv6 transport: [transport-tcp-ipv6] type=transport protocol=tcp bind=[2001:1234:5678:abcd::2]:5060 I also have an IPv4 version of that: [transport-tcp-ipv4] type=transport protocol=tcp bind=10.75.22.8:5060 I've then configured an endpoint to use it: [outgoing] type = endpoint context = default dtmf_mode = none disallow = all

Hello! I'm still trying to get a working t.38 configuration w/ pjsip. I'm now able to send t.38 faxes to my own extension: hylafax -> t38modem -> extension -> extension -> t38modem -> hylafax. The fax is sent by t38modem. The receiving part of t38modem accepts the call, sends ReInvite for t.38 and things are working as expected. Now, let's do the nearly same

Asterisk 13.8 Is CALLERID(all) supposed to wok for pjsip? When I do this: exten => 1234,Set(CALLERID(all)="Jon Doe" <+123456789>) same => n,Dial(PJSIP/phone123, 30) I expect the callerid to be as set, but is always seems to be "phone123", the name of the endpoint. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 06/05/2017 at 11:30 AM, Joshua Colp wrote: > On Sun, Jun 4, 2017, at 10:40 AM, Michael Maier wrote: >> On 06/04/2017 at 01:41 PM Telium Technical Support wrote: >>> Just a guess (without knowing about your network), but are the two ends >>> points on public networks and visible to one another? If not the reinvite >>> may be passing an internal (nat'ed)

The Asterisk Development Team has announced the release of Asterisk 13.4.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.4.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: New

The Asterisk Development Team has announced the release of Asterisk 13.4.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.4.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: New

Hi, 1. Has anyone got any success when send a TIFF file form one zoiper softphone to another ? I tried using Zoiper 2.18 free edition in windows but I'm seeing 415 Unsupported media replies. 2. Here (http://www.voipinfo.org/wiki/view/Asterisk+T.38), you can read : "Also, try using: t38_udptl=yes t38pt_rtp=no t38pt_tcp=no ... in the general section of the sip.conf and under the VoIP

Hello all, I'm setting up a couple of test boxes and I'm running into a problem. What I need help with is determining whether I'm going something wrong or if I need to post a bug report. I have two asterisk 13.0-beta 3 machines set up with extensions connected to each as such: 3700 ----> AST-A <------> AST-B <---- 3800 & 3801 When I place a call from 3800 to

Asterisk Project Security Advisory - AST-2019-004 Product Asterisk Summary Crash when negotiating for T.38 with a declined stream Nature of Advisory Remote Crash Susceptibility Remote

Asterisk Project Security Advisory - Product Asterisk Summary Re-invite with T.38 and malformed SDP causes crash. Nature of Advisory Remote Crash Susceptibility Remote Authenticated Sessions Severity Minor

Hi List Asterisk 16.28.0 in use. PJSIP in use Two endpoints Both using IPv6 One Endpoint on UDP, the other via TLS. Both with: t38_udptl=yes ;fax_detect=yes ;fax_detect_timeout=30 rtp_ipv6=yes Both sides are T.38 capable and detect fax tone so no need for fax detection on asterisk. Voice calls between the two work fine. But on a Fax call, I see this situation: A <=> Asterisk

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for your reply Larry. Le 27/07/2015 01:22, Larry Moore a ?crit : > I think the "488 Not acceptable here" is occurring because the channel > connecting through is not T.38 capable, that will be the IAX channel > from iaxmomdem. This is what T38gateway is supposed to do. And I'm very happy to report that after one more

> Asterisk Project Security Advisory - ASA-2007-010 > > +------------------------------------------------------------------------+ > | Product | Asterisk | > |--------------------+---------------------------------------------------| > | Summary | Two stack buffer overflows in SIP