@Thanh:
Just a wild guess, could it be the register message was sent to the wrong
server? While you are at it, it would be beneficial to check the logs on the
registra if available.
@Andreas:
Thanks for the tip! I didn't know that you can use msg_params_find() and your
code is much more cleaner :-)
Kun-Yao
On 13/06/2013, at 6:35 PM, ThanhTruong
<ngoc217th...@yahoo.com<mailto:ngoc217th...@yahoo.com>>
wrote:
hi,
When I register direct from softphone to kamailio, I see sip message via ngrep
(port 5062). BUT with mod_sofia (nua_register) I only see sending message and
receiving message in FS, but no sip message in ngrep capture, I think this is
issue.
IN FS, it show me it send message and get back via 5062 port. So, I dont know
why it is.
:(
Thanks,
ThanhTruong
________________________________
From: "Huang, Kun-Yao" <kxh...@dolby.com<mailto:kxh...@dolby.com>>
To:
"sofia-sip-devel@lists.sourceforge.net<mailto:sofia-sip-devel@lists.sourceforge.net>"
<sofia-sip-devel@lists.sourceforge.net<mailto:sofia-sip-devel@lists.sourceforge.net>>
Sent: Thursday, June 13, 2013 3:22 PM
Subject: Re: [Sofia-sip-devel] sip register message construct
If you can successful register something with the registra, I would suggest
capturing the successful SIP packets and compare them with the failed ones
might shed some light to the problem.
I would guess that it is more likely a configuration issue.
Kun-Yao
On 13/06/2013, at 6:13 PM, ThanhTruong
<ngoc217th...@yahoo.com<mailto:ngoc217th...@yahoo.com>>
wrote:
hi,
i can use softphone to register direct to kamailio with this port (5062).
i cant see REGISTER message send to kamailio via port 5062 when I used this
function (only see REGISTER message sent in FS, and receive in FS )
And I only get response as:
send 577 bytes to udp/[192.168.1.112]:5062 at 08:12:48.666723:
------------------------------------------------------------------------
REGISTER sip:192.168.1.112:5062<x-msg://420/> SIP/2.0
Via: SIP/2.0/UDP 192.168.1.112;rport;branch=z9hG4bKUHXHvX14a1gmN
Max-Forwards: 70
From: <sip:101@192.168.1.112:5062<x-msg://420/>>;tag=XKj7SQgvpZUBe
To: <sip:101@192.168.1.112:5062<x-msg://420/>>;tag=2641766a
Call-ID: e06eb8e6-4ea3-1231-cc82-3e508d3991e2
CSeq: 2 REGISTER
Contact: <sip:101@192.168.1.112<x-msg://420/>>
User-Agent: FreeSWITCH-mod_sofia/1.5.2b+git~20130527T075833Z~f3541e00f4
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Content-Length: 0
------------------------------------------------------------------------
recv 321 bytes from udp/[192.168.1.112]:5062 at 08:12:48.667688:
------------------------------------------------------------------------
SIP/2.0 404 Not here
Via: SIP/2.0/UDP 192.168.1.112;rport=5060;branch=z9hG4bKUHXHvX14a1gmN
From: <sip:101@192.168.1.112:5062<x-msg://420/>>;tag=XKj7SQgvpZUBe
To: <sip:101@192.168.1.112:5062<x-msg://420/>>;tag=2641766a
Call-ID: e06eb8e6-4ea3-1231-cc82-3e508d3991e2
CSeq: 2 REGISTER
Server: kamailio (4.0.1 (x86_64/linux))
Content-Length: 0
------------------------------------------------------------------------
send 577 bytes to udp/[192.168.1.112]:5062 at 08:12:49.666830:
------------------------------------------------------------------------
REGISTER sip:192.168.1.112:5062<x-msg://420/> SIP/2.0
Via: SIP/2.0/UDP 192.168.1.112;rport;branch=z9hG4bKUHXHvX14a1gmN
Max-Forwards: 70
From: <sip:101@192.168.1.112:5062<x-msg://420/>>;tag=XKj7SQgvpZUBe
To: <sip:101@192.168.1.112:5062<x-msg://420/>>;tag=2641766a
Call-ID: e06eb8e6-4ea3-1231-cc82-3e508d3991e2
CSeq: 2 REGISTER
Contact: <sip:101@192.168.1.112<x-msg://420/>>
User-Agent: FreeSWITCH-mod_sofia/1.5.2b+git~20130527T075833Z~f3541e00f4
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Content-Length: 0
------------------------------------------------------------------------
Do you have nay idea ?
Thanks,
ThanhTruong
________________________________
From: "Huang, Kun-Yao" <kxh...@dolby.com<mailto:kxh...@dolby.com>>
To:
"sofia-sip-devel@lists.sourceforge.net<mailto:sofia-sip-devel@lists.sourceforge.net>"
<sofia-sip-devel@lists.sourceforge.net<mailto:sofia-sip-devel@lists.sourceforge.net>>
Sent: Thursday, June 13, 2013 3:04 PM
Subject: Re: [Sofia-sip-devel] sip register message construct
I don't think CSeq not being 1 would be a problem.
Have you every successful registered everything against that registra?
Kun-Yao
------------------------------------------------------------------------------
This SF.net<http://SF.net> email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net<mailto:Sofia-sip-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
------------------------------------------------------------------------------
This SF.net<http://SF.net> email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
