[OpenSIPS-Users] Siptrace Issue
Seth Schultz
sschultz at scholarchip.com
Fri Feb 8 18:55:45 CET 2013
Perfect!
Thanks,
Seth
On 2/8/2013 12:52 PM, Bogdan-Andrei Iancu wrote:
> Seth, the backports are already done, so SVN 1.9 and 1.8 were updated.
> Tarballs are nightly generated, so shortly they will be updated too.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
>
> On 02/08/2013 07:39 PM, Seth Schultz wrote:
>> No problem at all. Will you please let me know once these changes
>> have been pushed into both 1.9 and 1.8 sources?
>>
>> Thanks,
>> Seth
>>
>> On 2/8/2013 11:42 AM, Bogdan-Andrei Iancu wrote:
>>> Hi Seth,
>>>
>>> perfect !!! I will make the backports to 1.9 and 1.8 .
>>>
>>> And many thanks for the help in troubleshooting this problem.
>>>
>>> Best regards,
>>>
>>> Bogdan-Andrei Iancu
>>> OpenSIPS Founder and Developer
>>> http://www.opensips-solutions.com
>>>
>>>
>>> On 02/08/2013 06:31 PM, Seth Schultz wrote:
>>>> Bogdan-Andrei,
>>>>
>>>> I think that did the trick! Errors have cleared up, and I am
>>>> seeing the full trace on my capture server now. I will keep
>>>> playing with this in my development environment and let you know if
>>>> I run into any more issues.
>>>>
>>>> Will these patches work on the 1.8.2 branch?
>>>>
>>>> Thanks again for all the help. This is the reason I love using
>>>> opensips!
>>>>
>>>> Seth
>>>>
>>>> On 2/8/2013 9:42 AM, Bogdan-Andrei Iancu wrote:
>>>>> Hi Seth,
>>>>>
>>>>> it was yet another char* to str conversion error. Please see the
>>>>> additional patch to be applied on top of the previous one. It
>>>>> should solve this issue.
>>>>>
>>>>> Thanks and regards,
>>>>>
>>>>> Bogdan-Andrei Iancu
>>>>> OpenSIPS Founder and Developer
>>>>> http://www.opensips-solutions.com
>>>>>
>>>>>
>>>>> On 02/07/2013 09:25 PM, Seth Schultz wrote:
>>>>>> Alexander,
>>>>>>
>>>>>> I am not so much worried about the port range. I am trying to
>>>>>> determine where that port is coming from in the first place.
>>>>>> Nothing on my end should ever be advertising anything other than
>>>>>> port 5060. I believe it is getting corrupted somewhere, just not
>>>>>> sure how to track it down.
>>>>>>
>>>>>> Thanks,
>>>>>> Seth
>>>>>>
>>>>>> Seth Schultz
>>>>>> E-Mail: sschultz at scholarchip.com
>>>>>> Phone: 212.255.8005 x 124
>>>>>> Fax: 212.255.8091
>>>>>>
>>>>>> On 2/7/2013 2:13 PM, Alexandr Dubovikov wrote:
>>>>>>> I can make a patch to ignore the port range, but I think
>>>>>>> something wrong in
>>>>>>> the socket structure: the port number is too high.
>>>>>>>
>>>>>>> Wbr,
>>>>>>> Alexandr
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: users-bounces at lists.opensips.org
>>>>>>> [mailto:users-bounces at lists.opensips.org] On Behalf Of Seth Schultz
>>>>>>> Sent: Thursday, February 07, 2013 7:40 PM
>>>>>>> To: Bogdan-Andrei Iancu
>>>>>>> Cc: OpenSIPS users mailling list
>>>>>>> Subject: Re: [OpenSIPS-Users] Siptrace Issue
>>>>>>>
>>>>>>> Bogdan,
>>>>>>>
>>>>>>> The patch did solve the error I was receiving, however, now I am
>>>>>>> receiving a
>>>>>>> new error "ERROR:siptrace:pipport2su: invalid port number; must
>>>>>>> be in
>>>>>>> [1024,65536]". I captured some information from the branch
>>>>>>> route and I also
>>>>>>> modified the error message to display the port number.
>>>>>>> I also added abort(); just after the error message to capture a
>>>>>>> core file.
>>>>>>> I have no idea where this port number is coming from.
>>>>>>>
>>>>>>> Feb 7 13:33:17 opensips-vm /sbin/opensips[15149]: ----- BRANCH:
>>>>>>> 172.16.1.105 <null> domain=172.16.1.1 port=5060 transport=udp
>>>>>>> uri=sip:172.16.1.1
>>>>>>> Feb 7 13:33:17 opensips-vm /sbin/opensips[15149]:
>>>>>>> ERROR:siptrace:pipport2su: port = 5060060 invalid port number;
>>>>>>> must be in
>>>>>>> [1024,65536] Feb 7 13:33:17 opensips-vm /sbin/opensips[15146]:
>>>>>>> ERROR:siptrace:pipport2su: port = 5060600 invalid port number;
>>>>>>> must be in
>>>>>>> [1024,65536] Feb 7 13:33:19 opensips-vm /sbin/opensips[15140]:
>>>>>>> ERROR:siptrace:pipport2su: port = 5060060 invalid port number;
>>>>>>> must be in
>>>>>>> [1024,65536]
>>>>>>>
>>>>>>>
>>>>>>> Thanks for all your help. I truly appreciate it!
>>>>>>> Seth
>>>>>>>
>>>>>>> On 2/7/2013 6:52 AM, Bogdan-Andrei Iancu wrote:
>>>>>>>> Hi Seth,
>>>>>>>>
>>>>>>>> Thanks a lot for your help - I found and hopefully fixed the
>>>>>>>> bug - I
>>>>>>>> made the commit on SVN trunk only and I would ask you to test
>>>>>>>> it first
>>>>>>>> (see the attached patch). Let me know if works fine for you and
>>>>>>>> i will
>>>>>>>> do the backport .
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>> http://www.opensips-solutions.com
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>
>>
More information about the Users
mailing list