[Spce-user] Please let me knowwhyIfaced401/403(Unauthorized/Invalid To-URI Detected).

[David Ho]

Jon,
 
I've already followed up the document that you provide "The sip:provider CE Handbook 2.7" so I'm followed setup 1 to 6 chapter and almost setting same like the document.
And now I'm tried to modify values of Peering Servers several times and you could know where I'm modified the values at "6.4.4. Authenticating and Registering against Peering Servers".
the URL following;
http://www.sipwise.com/doc/2.7/spce/ar01s06.html#_authenticating_and_registering_against_peering_servers
 
So manytimes, SIPWISE server denied my PSTN gateway caused by Unauthorized(401).
And I found what is problemed via sems log file("/var/log/ngcp/sem/sems.log") it appeared error message before I mentioned same like following;
-----------------------------------------------------------------------------------------------------------------
Mar 20 08:44:14 spce sems[2164]: [#7f601e77d700] [doRegistration, AmSipRegistration.cpp:139] ERROR: failed to send registration.
-----------------------------------------------------------------------------------------------------------------
So 'doRegistration function in AmSipRegistration.cpp file occurred ERROR message.
If you were me, how could solve the error occurred?
 
And it is another one that I afraid thing.
the log files in SIPWISE as kamailio-lb.log and kamailio-options-proxy.log increased capacity too much.
my kamailio-lb.log file capacity is over than 28MB and kamailio-options-proxy.log file capacity is more than 7MB.
The reason of the log too much increased capacity caused by stacked approax. four to five log messages per a second!
Is it alright to leave it even though it will be huge capacity log file after than this log file could occurr system error for leak of hard disk capacity.
 
David


-----------------------원본메일-----------------------
보낸사람 : "Jon Bonilla (Manwe)" <jbonilla at sipwise.com>
받는사람: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
참 조: David Ho <rea1ity at kaist.ac.kr>
보낸날짜: 2013-03-20 19:35:53 GMT +0900 (Asia/Seoul)
제목: Re: [Spce-user] Please let me knowwhyIfaced401/403(Unauthorized/Invalid To-URI Detected).

El Wed, 20 Mar 2013 19:18:21 +0900 (KST)

David Ho<rea1ity at kaist.ac.kr> escribió:



> 

> p{margin:0;padding:0;}

> 

> 

> Oh my GOD!

> You are right.

> I think that I faced seriousley critical problemed.

> When I opened the other files as "kamailio-options-proxy_log" and

> "kamailio-proxy_log" and "kamailio-lb_log" at "/var/log/ngcp/" path, There

> have so many logs made it appear New request and request reply per a second.

> Moreover, there have the user that I didn't set it but it could working

> internally. I.E."R=sip:nagios at voip.sipwise.local F=sip:sipsak at 127.0.0.1:8485

> T=sip:nagios at voip.sipwise.local" My SIPWISE server operate it downloaded from

> vmware image. So may I have some missing to configurate of sipwise. :( I'm

> just tried to configured it as following SIPWISE document version 2.7 because

> I don't know well about VoIP. Now I understand why the document recommended

> manually install SIPWISE.





No, what you achieve manually installing the provider is more or less the same

as you get with the vmware image. The internal sipsak user you have found is an

internal user for monitoring the system. 



> Maybe, this problem must be solve first before that

> I configuration of peer registration modified. Anyway, I set a peer same like

> the image files that I attached it name is "test-gw-1.png". 





you need to go step by step. Follow the handbook, create you doain, create and

account, create two subscribers and call from one subscriber to the other. Once

you're there we'll talk about peering servers.



I think you are mixing too many things so either you follow the handbook

quick-start or you'll need to learn about Voip (or both).





cheers,



Jon



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130321/c752c8f0/attachment-0001.html>