[OpenSIPS-Users] media dispatcher to_tag error

[Jeff Pyle]

Hi Saúl,

I am not using 100rel.  I detest 100rel.

I don't have sufficient debugging enabled to see the session summary.  I'm pushing so many calls through the dispatcher now I'm afraid if I were to enable it, I'd crush the machine.

I may have solved the issue, though.  I noticed the following in 2.3.7's changelog:

  * Allow the to_tag field in the media_sessions table to be NULL

In my media_sessions table, it's still set to disallow NULL.  Apparently I didn't rebuild the table when I upgraded from something previous to 2.3.7.


- Jeff


On May 27, 2010, at 12:42 PM, Saúl Ibarra Corretgé wrote:

> Hi Jeff,
> 
> On 27/05/10 18:20, Jeff Pyle wrote:
>> Hello again,
>> 
>> I've almost got this thing working perfectly so I'm almost ready to stop bothering the list for a while.
>> 
>> Now that I'm able to take several hundred concurrent streams without a hitch, I'm seeing a lot of this in the dispatcher log:
>>   error: failed to insert record into database: Column 'to_tag' cannot be null
>> 
>> The error itself is very specific, but the cause is less so.  Is this as simple as modifying the table to accept a null value?  Or, is there something in the Opensips logic that is causing it?
>> 
>> Version 2.3.8, and Opensips 1.6 rev 6702.
>> 
> 
> Are you using 100rel and a 200OK reply without SDP? Also, can you paste 
> the syslog output (session summary) when that happens?
> 
> 
> -- 
> Saúl Ibarra Corretgé
> AG Projects
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users