[Spce-user] A little help please

Fri Jul 12 22:07:03 EDT 2013

I was watching both log files at the same time, and nothing was happening
in the proxy log during the incoming calls. Only information I could see
was coming in in kamailio-lb.log

I can usually figure these things out on my own when I understand the
signal/call flow, I've never used ngcp or kamailio before so I'm having
some issues understanding which moduels comes first, which comes second,
how they integrate, so I'm having some troubles monitoring via logs where
exactly the call fails. I know this is learning pains, so with help from
people like you we'll get through it. I appreciate your time.

Do you still want me to post the proxy log even though nothing happens in
it during the incoming call?

Here are the contents of kamailio-lb.log during the incoming request:

/usr/sbin/kamailio[10906]: INFO: <script>: Outbound Register request from
b2bua - R=sip:sip.provider.trunk.com ID=3D03DA93-51E0511C00083FD3-42FCD700
/usr/sbin/kamailio[10906]: INFO: <script>: Forcing Outbound Register
request for known call-id to 'sip:24.23.22.21:5060' -
R=sip:sip.provider.trunk.com ID=3D03DA93-51E0511C00083FD3-42FCD700
/usr/sbin/kamailio[10906]: INFO: <script>: Relaying request,
du='sip:24.23.22.21:5060', fs='udp:10.0.0.40:5060' -
R=sip:sip.provider.trunk.com ID=3D03DA93-51E0511C00083FD3-42FCD700
/usr/sbin/kamailio[10899]: INFO: <script>: Reply from Outbound - S=200 -
OK M=REGISTER IP=udp:24.23.22.21:5060
ID=3D03DA93-51E0511C00083FD3-42FCD700
/usr/sbin/kamailio[10899]: INFO: <script>: NATed reply detected -
ID=3D03DA93-51E0511C00083FD3-42FCD700
/usr/sbin/kamailio[10899]: INFO: <script>: Sending reply,
fs='udp:127.0.0.1:5060' - ID=3D03DA93-51E0511C00083FD3-42FCD700
/usr/sbin/kamailio[10908]: INFO: <script>: New request - M=OPTIONS
R=sip:nagios at voip.sipwise.local F=sip:sipsak at 10.0.0.40:6736
T=sip:nagios at voip.sipwise.local IP=udp:127.0.0.1:6736
ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10908]: INFO: <script>: NAT check disabled by
administrator for source IP '127.0.0.1' - M=OPTIONS
R=sip:nagios at voip.sipwise.local F=sip:sipsak at 10.0.0.40:6736
T=sip:nagios at voip.sipwise.local IP=127.0.0.1:6736 ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10908]: INFO: <script>: Relaying request,
du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' -
R=sip:nagios at voip.sipwise.local ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10911]: INFO: <script>: Reply from Inbound - S=100 -
Trying M=OPTIONS IP=udp:127.0.0.1:5062 ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10911]: INFO: <script>: Forcing outbound socket
'udp:127.0.0.1:5060' recovered from P-Out-Socket - R=<null>
ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10911]: INFO: <script>: Sending reply,
fs='udp:127.0.0.1:5060' - ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10907]: INFO: <script>: Reply from Inbound - S=200 -
Alive M=OPTIONS IP=udp:127.0.0.1:5062 ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10907]: INFO: <script>: Forcing outbound socket
'udp:127.0.0.1:5060' recovered from P-Out-Socket - R=<null>
ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10907]: INFO: <script>: Sending reply,
fs='udp:127.0.0.1:5060' - ID=2070232014 at 10.0.0.40
/usr/sbin/kamailio[10900]: INFO: <script>: New request - M=INVITE
R=sip:5554443322 at 10.0.0.40:5060;transport=udp
F=sip:9998887766 at 99.88.77.66:5060;transport=udp
T=sip:5554443322 at 10.0.0.40:5060 IP=udp:24.23.22.21:5060
ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10900]: INFO: <script>: Relaying request,
du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' -
R=sip:5554443322 at 10.0.0.40:5060;transport=udp ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10910]: INFO: <script>: Reply from Inbound - S=100 -
Trying M=INVITE IP=udp:127.0.0.1:5062 ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10910]: INFO: <script>: Forcing outbound socket
'udp:10.0.0.40:5060' recovered from P-Out-Socket - R=<null>
ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10910]: INFO: <script>: Sending reply,
fs='udp:10.0.0.40:5060' - ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10909]: INFO: <script>: Reply from Inbound - S=500 -
I'm terribly sorry, server error occurred (6/SL) M=INVITE
IP=udp:127.0.0.1:5062 ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10909]: INFO: <script>: Forcing outbound socket
'udp:10.0.0.40:5060' recovered from P-Out-Socket - R=<null>
ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10909]: INFO: <script>: Sending reply,
fs='udp:10.0.0.40:5060' - ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10904]: INFO: <script>: Reply from Inbound - S=500 -
I'm terribly sorry, server error occurred (6/TM) M=INVITE
IP=udp:127.0.0.1:5062 ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10904]: INFO: <script>: Forcing outbound socket
'udp:10.0.0.40:5060' recovered from P-Out-Socket - R=<null>
ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10904]: INFO: <script>: Sending reply,
fs='udp:10.0.0.40:5060' - ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10901]: INFO: <script>: New request - M=ACK
R=sip:5554443322 at 10.0.0.40:5060;transport=udp
F=sip:9998887766 at 99.88.77.66:5060;transport=udp
T=sip:5554443322 at 10.0.0.40:5060 IP=udp:24.23.22.21:5060
ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10901]: INFO: <script>: Perform normal inbound routing
- R=sip:5554443322 at 10.0.0.40:5060;transport=udp ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10901]: INFO: <script>: Relaying request,
du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' -
R=sip:5554443322 at 10.0.0.40:5060;transport=udp ID=F66DD6D2 at 99.88.77.66
Jul 12 14:55:29 voipgw /usr/sbin/kamailio[10902]: INFO: <script>: New
request - M=ACK R=sip:5554443322 at 10.0.0.40:5060;transport=udp
F=sip:9998887766 at 99.88.77.66:5060;transport=udp
T=sip:5554443322 at 10.0.0.40:5060 IP=udp:24.23.22.21:5060
ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10902]: INFO: <script>: Perform normal inbound routing
- R=sip:5554443322 at 10.0.0.40:5060;transport=udp ID=F66DD6D2 at 99.88.77.66
/usr/sbin/kamailio[10902]: INFO: <script>: Relaying request,
du='sip:127.0.0.1:5062', fs='udp:127.0.0.1:5060' -
R=sip:5554443322 at 10.0.0.40:5060;transport=udp ID=F66DD6D2 at 99.88.77.66

When I was calling of my cellphone it was just hanging up, when I call
from my SIP phone (different provider, separate network from the one I'm
trying to configure) I get a message "The number you are calling it
temporarily unavailable" which I am assuming is part of the ngcp package?
right after I get the standards asterisk "All circuits are currently busy
now" which is from the PBX on the initiating end (not the asterisk part of
ngcp setup).

To me it sounds like the call is coming in, but then for some reason ngcp
doesn't know where to route it? Could it be that my ReWrite Rules are
causing this?

Thank you again.

Paul

On Fri, July 12, 2013 3:59 am, Andrew Pogrebennyk wrote:
> Paul,
> posting /var/log/ngcp/kamailio-proxy.log would help.
>
> On 07/12/2013 05:59 PM, Paul wrote:
>
>> Andreas,
>>
>>
>> You are correct. I caught that right after I sent this message, when I
>> was following the manual to get a sip peering (register a trunk) it told
>> me to edit reg_agent.tt2 as doing it from the GUI wasn't enough. I
>> removed those entries causing the errors and am attempting to register
>> my trunk and not sure where I'm encountering my problem, any helps
>> GREATLY appreciated as
>> I'm getting a little frustrated... wayy to much new config to learn :)
>>
>>
>> Here's my situation:
>>
>>
>> - Trunk @ my provider with DID
>> - I edited reg_agent.tt2 and added
>> - domain=provider.trunk.domain.com
>> - user = <username provided for me by provider>
>> - pass = <same as above>
>> - left the other lines untouched
>>
>>
>> I also have this trunk entered in Sip Peering in the GUI but to be
>> honest can't get a clear understanding in what the connection is between
>> them, and maybe that's why this isn't working.
>>
>> Currently when I dial my DID from my cell it hits kamailio, I see the
>> call coming in, logs end with "Performing normal inbound routing", so
>> the call should continue to a user I have assigned the incoming DID to,
>> and that user is a trunk registered on one of my PBXs down the line
>> (FreeSwitch).
>>
>>
>> My Freeswitch never gets the call as I'm monitoring the logs. So my
>> guess then (if kamailio isn't denying the call) is that the ReWrite
>> rules aren't compatible with the format the call is coming in on?
>>
>> Call comes in as a 10 digit (north america) NXX-NXX-NXXX what ReWrite
>> rules would convert it to E.164 (which I believe ngcp is expecting?) so
>> that it continues getting routed properly? And would I add this rule
>> under Inbound Callee or Caller? I'm assuming Caller?
>>
>>
>> Thanks again for your quick response!
>>
>>
>> Paul
>>
>>
>> On Fri, July 12, 2013 1:04 am, Andreas Granig wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> On 07/12/2013 04:39 PM, Paul wrote:
>>>
>>>
>>>> Forgive my noob question, I have near 0 experience with ngcp. I
>>>> keep getting the following errors in my logs and can't figure out
>>>> where it's coming from, I have nothing in Sip Peerings that isn't
>>>> working, but this keeps repeating every second in my logs. Not sure
>>>> where these REGISTER
>>>> requests are coming form.
>>>
>>> Looks like you've configured either peer_auth_* preferences for one
>>> of your subscribers, or you've configured peer registration in your
>>> reg_agent.tt2 of sems? Can you show us what you put there?
>>>
>>> Andreas
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> http://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
>>
>
>