similar to: Outbound T.38 via RTP with pjsip does not work as expected

Displaying 20 results from an estimated 5000 matches similar to: "Outbound T.38 via RTP with pjsip does not work as expected"

2017 Jun 04
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
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
2017 Jun 04
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
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
2017 Jun 05
3
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
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)
2015 Feb 02
0
Asterisk 13, PJSIP and T38 problem
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
2017 Jun 05
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Mon, Jun 5, 2017, at 12:00 PM, Joshua Colp wrote: > On Mon, Jun 5, 2017, at 11:49 AM, Michael Maier wrote: > > 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
2017 Jun 16
3
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Fri, Jun 16, 2017, at 10:49 AM, Michael Maier wrote: <snip> > > t38modem and asterisk are using > > m=image 35622 udptl t38 > ^^^^^ > > Provider uses > > m=image 35622 UDPTL t38 > ^^^^^ > > Could this be a problem? If I'm sending internal only, it's always > lowercase. Looking at the tests we have we
2017 Jun 11
3
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Sun, Jun 11, 2017, at 08:16 AM, Michael Maier wrote: <snip> > I did some further investigations and fixed a local problem. Now, > asterisk is able to successfully activate T.38 - unfortunately just for > very shot time because of a phantom package it receives! What was the local problem? > Let's go into details: > I'm starting at the point where asterisk / fax
2015 Jul 27
2
PJSIP T.38 issues
-----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
2017 Jun 16
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Fri, Jun 16, 2017, at 02:13 AM, Michael Maier wrote: > Has anybody any idea why asterisk drops the media stream in the 200 OK? > The channel has been T38_ENABLED before! Or is it necessary to add more > debug code? Who does the negotiating? > Only asterisk or is pjsip doing some parts, too? Asterisk does the T.38 negotiation and produces the answer SDP, PJSIP does the SDP
2017 Jun 05
3
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Mon, Jun 5, 2017, at 04:26 PM, Michael Maier wrote: > On 06/05/2017 at 06:29 PM, Joshua Colp wrote: > > On Mon, Jun 5, 2017, at 01:22 PM, Michael Maier wrote: > >> > >> Do you have any idea where to start to look at? Adding additional output > >> in the source code? Which functions could be interesting? I may add own > >> debug code to see why things
2019 Apr 22
2
Incoming SIP call, outgoing SIP registration. 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
2016 Jul 04
2
CALLERID on pjsip doesn't work?
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.
2020 Jun 01
1
Asterisk 16 Certified 16.8 and MagicJack Incoming Calls
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
2018 Dec 12
3
Outbound call: caller gets no ringback on session progress
Hello! An extension registered at asterisk 13.23 initiates an external call (pjsip). After the Invite, the callee (-> ISP) sends a 100 Trying 183 Session Progress (*without* SDP) Asterisk now sends to the extension: 183 Session Progress (*with* SDP) 183 Session Progress (*with* SDP) (really two times) The callee meanwhile sends 180 Ringing (*without* SDP) which is
2017 May 13
2
pjsip: asterisk can't decide which codec to use
On 05/12/2017 at 08:49 PM, Joshua Colp wrote: > On Fri, May 12, 2017, at 02:46 PM, Michael Maier wrote: > > <snip> > >> >> If I'm doing exactly the same call originated with another extension, >> there can't be seen these frequent changes. But the strange thing is, >> that in both cases the part between extension and asterisk doesn't show
2015 Feb 04
0
Can not calculate far_max_ifp before far_max_datagram has been set
Hello, I use Asterisk 13.1 with a SIP trunk with a provider When transmitting or receiving a fax in T.38 through the trunk with the provider I always get this warning: WARNING [8204]: udptl.c: 852 calculate_far_max_ifp: UDPTL (no tag): Can not calculate far_max_ifp before far_max_datagram has been set After the warning begins exchanging packets UDPTL, but all with sequence number 0 or 256. The
2017 Jun 15
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On 06/14/2017 at 10:17 PM, Joshua Colp wrote: > On Wed, Jun 14, 2017, at 05:09 PM, Michael Maier wrote: > > <snip> > >> >> I can now say, that asterisk / pjsip seams to work *mostly* as expected. >> Just one exception - and that's the package in question, which can't be >> seen in tcpdump. >> >> I extended the above patch by adding
2017 Jun 05
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Mon, Jun 5, 2017, at 01:22 PM, Michael Maier wrote: > > Do you have any idea where to start to look at? Adding additional output > in the source code? Which functions could be interesting? I may add own > debug code to see why things are happening as they happen here. The logic for T.38 negotiation lives all in the res_pjsip_t38 module and the request to negotiate works using a
2017 Jun 11
2
asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'
On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: <snip> > > > > PJSIP uses a dispatch model. The request is queued up, acted on, and > > then that's it. The act of acting on it removes it from the queue. > > That's the *expected* behavior ... . I rechecked again and again. All > existing tcpdumps. The "resent" package isn't part of
2017 May 12
3
pjsip: asterisk can't decide which codec to use
Hello! I'm facing completely choppy sound. The wireshark trace shows, that there are a lot of codec changes without any trigger (means no options or reinvite or any other package). Background: The call is initiated by asterisk and is received by the same asterisk conference room via Phone extension -> asterisk -> provider A -> provider B -> asterisk. Asterisk initially sends