Displaying 3 results from an estimated 3 matches for "t38_enabl".
Did you mean:
t38_enabled
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 negotiation. It's likely in the realm of Asterisk where it
is doing tha...
2010 Jun 29
0
T.38 Peer Negotiation Fails
...yyy.yyy:16468
chan_sip.c: Strict routing enforced for session
1057817983_43059159 at xxx.xxx.xxx.xxx
On a known good/working T.38 configured Asterisk PBX elsewhere (with
Affinity as the ITSP), I also see the "Strict routing" message, yet
T.38 negotiation achieves t38state 5 (chan_sip.c: T38_ENABLED) and
calls are successful.
I've been comparing Asterisk debug from both systems as well as
wireshark captures, but I can't figure out why Asterisk is not
sending the Linksys ATA's IP address.
Broadvox uses a Sonus switch and gateway with separate IP addresses
for SIP and media. Affi...
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