Hello Daniel
Attachment is the full ngrep output for the sample call.
On Wed, Apr 27, 2016 at 6:51 PM, Daniel-Constantin Mierla <mico...@gmail.com
> wrote:
> Hello,
>
> can you make the full ngrep trace for the call (from initial invite sent
> by kamailio, with all following sip messages) and send it over here?
> Cheers,
> Daniel
>
>
> On 27/04/16 17:16, huseyin kalyoncu wrote:
>
> Hello Daniel
>
> I did some more tests and my previous statement is wrong.
> Actually it do call set_contact_alias on 200 reply for INVITEs
> but somehow it has no change.
> I really missing something here.
>
> On Wed, Apr 27, 2016 at 3:35 PM, huseyin kalyoncu < <hkalyo...@gmail.com>
> hkalyo...@gmail.com> wrote:
>
>> Hello Daniel
>>
>> You are right. 200OK messages are also with private IPs.
>> I think the problem is that
>> since I call dlg_bridge with Kamailio's own IP
>> It sends INVITE messages to itself first then it routes INVITE msg to
>> user location.
>> Because of this i see two record routes in the INTIVE headers and 200
>> reply headers.
>>
>> if (is_reply()) {
>> if(isbflagset(FLB_NATB)) {
>> if(is_first_hop())
>> set_contact_alias();
>> }
>> }
>>
>> But according to this code in NATMANAGE block, it only set contact if it
>> is first hope.
>> Since these messages have two record routes, this code block does not
>> modify contact field
>> Am I right? or Am I missing something else?
>>
>> Thanks
>> Huseyin
>>
>>
>> On Wed, Apr 27, 2016 at 12:50 PM, Daniel-Constantin Mierla <
>> <mico...@gmail.com>mico...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> dlg_bridge is not using the location table at all, because it has to use
>>> the contact from 200ok of INVITE.
>>>
>>> Have you used set_contact_alias() for natted 200ok received for INVITE?
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 27/04/16 11:15, huseyin kalyoncu wrote:
>>>
>>> Hello Daniel
>>>
>>> This is the sample output from our location table;
>>>
>>> kamailio=# select username,contact,received,user_agent from location
>>> where username='5678*0012';
>>> username | contact | received |
>>> user_agent
>>>
>>> -----------+---------------------------------+-----------------------+---------------------
>>> 5678*0012 | sip:5678* <http://0012@192.168.1.21:5090>
>>> 0012@192.168.1.21:5090 | sip:DEVICE_PUBLIC_ADDRESS:5090 |
>>> Cisco/SPA504G-7.6.1
>>> (1 row)
>>>
>>>
>>> After calling dlg_bridge Kamailio firing INVITE and rings the device.
>>> After answering on this device Kamailio firing REFER message.
>>> But as you can see from ngrep output below, Kamailio is trying to send
>>> this message to address in the contact field which is a private IP.
>>>
>>> U 2016/04/27 10:58:25.745935 KAMAILIO_PUBLIC_ADDRESS:5090 ->
>>> 192.168.1.21:5090
>>> REFER sip:5678* <http://0012@192.168.1.21:5090>0012@192.168.1.21:5090
>>> SIP/2.0.
>>> Via: SIP/2.0/UDP
>>> KAMAILIO_PUBLIC_ADDRESS:5090;branch=z9hG4bK0ab8.1c5e622e4af6b7b6c9ede7ade4a50bf8.0.
>>> Via: SIP/2.0/UDP
>>> KAMAILIO_PUBLIC_ADDRESS;rport=5060;branch=z9hG4bK0ab8.c8a54413000000000000000000000000.0.
>>> To: <sip:5678*0012@KAMAILIO_PUBLIC_ADDRESS>;tag=199aaa02310a0799i1.
>>> From: <sip:click2call@KAMAILIO_PUBLIC_ADDRESS>
>>> ;tag=0d71401ca91009b00be5953e2813d7e4-7471.
>>> CSeq: 11 REFER.
>>> Call-ID: 63dc8c8a5ea88a30-868@KAMAILIO_PUBLIC_ADDRESS.
>>> Max-Forwards: 69.
>>> Content-Length: 0.
>>> User-Agent: Kamailio.
>>> Referred-By: sip:click2call@KAMAILIO_PUBLIC_ADDRESS.
>>> Refer-To: sip:5678*0002@KAMAILIO_PUBLIC_ADDRESS.
>>> Contact: <sip:click2call@KAMAILIO_PUBLIC_ADDRESS:5060>.
>>>
>>>
>>>
>>> On Wed, Apr 27, 2016 at 10:47 AM, Daniel-Constantin Mierla <
>>> <mico...@gmail.com>mico...@gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> can you send the ngrep trace for such case? I would like to look at the
>>>> headers to understand properly what do you mean.
>>>>
>>>> Cheers,
>>>>
>>>> Daniel
>>>>
>>>> On 26/04/16 15:23, huseyin kalyoncu wrote:
>>>>
>>>> Hello
>>>>
>>>> I am trying to implement click 2 call functionality on Kamailio
>>>> with dlg_bridge.
>>>> But It seems that Kamailio routes REFER messages to devices according
>>>> to Contact field of location table instead of Received field.
>>>> But if the the IP in the Contact field is private REFER messages are
>>>> failing so
>>>> does the dlg_bridge.
>>>>
>>>>
>>>> I called dlg_bridge in the config like this:
>>>>
>>>> dlg_bridge("sip:$param1", "sip:$param2",
>>>> "sip:IP_ADDRESS_OF_KAMAILIO:5060");
>>>>
>>>> It rings the device in $param1 but after answering on that device
>>>> Kamailio fails to send REFER if the Contact field for that device is
>>>> Private IP.
>>>> So it fails to initiate a call.
>>>>
>>>> How can I force Kamailio to use Received field for REFER messages
>>>> instead of Contact field?
>>>>
>>>> Thanks
>>>> Huseyin
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>>>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>> --
>>>> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda
>>>> - http://www.linkedin.com/in/miconda
>>>> Kamailio World Conference, Berlin, May 18-20, 2016 -
>>>> http://www.kamailioworld.com
>>>>
>>>>
>>>> _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>> sr-users@lists.sip-router.org
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> --
>>> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda
>>> - http://www.linkedin.com/in/miconda
>>> Kamailio World Conference, Berlin, May 18-20, 2016 -
>>> http://www.kamailioworld.com
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda -
> http://www.linkedin.com/in/miconda
> Kamailio World Conference, Berlin, May 18-20, 2016 -
> http://www.kamailioworld.com
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
U 2016/04/27 18:26:25.440314 195.200.82.100:5060 -> 195.200.82.100:5060
INVITE sip:5678*0012@195.200.82.100 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 10 INVITE.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 70.
Content-Length: 147.
User-Agent: Kamailio.
Contact: <sip:click2call@195.200.82.100>.
Content-Type: application/sdp.
.
v=0.
o=kamailio-bridge 0 0 IN IP4 0.0.0.0.
s=kamailio.
c=IN IP4 0.0.0.0.
t=0 0.
m=audio 9 RTP/AVP 8 0.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
U 2016/04/27 18:26:25.445182 195.200.82.100:5060 -> 195.200.82.100:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0;rport=5060.
To: <sip:5678*0012@195.200.82.100>.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 10 INVITE.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Server: Kamailio.
Content-Length: 0.
.
U 2016/04/27 18:26:25.445786 195.200.82.100:5090 -> 176.40.9.170:5090
INVITE sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Record-Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Record-Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKd10e.cb3be507608b2fbdaf04da06aee9e770.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 10 INVITE.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 69.
Content-Length: 169.
User-Agent: Kamailio.
Contact: <sip:click2call@195.200.82.100>.
Content-Type: application/sdp.
.
v=0.
o=kamailio-bridge 0 0 IN IP4 0.0.0.0.
s=kamailio.
c=IN IP4 0.0.0.0.
t=0 0.
m=audio 16420 RTP/AVP 8 0.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
a=nortpproxy:yes.
U 2016/04/27 18:26:25.510630 176.40.9.170:5090 -> 195.200.82.100:5090
SIP/2.0 100 Trying.
To: <sip:5678*0012@195.200.82.100>.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 10 INVITE.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKd10e.cb3be507608b2fbdaf04da06aee9e770.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
Record-Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Record-Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Server: Cisco/SPA504G-7.6.1.
Content-Length: 0.
.
U 2016/04/27 18:26:25.547785 176.40.9.170:5090 -> 195.200.82.100:5090
SIP/2.0 180 Ringing.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 10 INVITE.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKd10e.cb3be507608b2fbdaf04da06aee9e770.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
Record-Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Record-Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Contact: "0012" <sip:5678*0012@192.168.1.21:5090>.
Server: Cisco/SPA504G-7.6.1.
Content-Length: 0.
.
U 2016/04/27 18:26:25.550457 195.200.82.100:5060 -> 195.200.82.100:5060
SIP/2.0 180 Ringing.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 10 INVITE.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
Record-Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Record-Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Contact: "0012" <sip:5678*0012@192.168.1.21:5090;alias=176.40.9.170~5090~1>.
Server: Cisco/SPA504G-7.6.1.
Content-Length: 0.
.
U 2016/04/27 18:26:28.223122 176.40.9.170:5090 -> 195.200.82.100:5090
SIP/2.0 200 OK.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 10 INVITE.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKd10e.cb3be507608b2fbdaf04da06aee9e770.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
Record-Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Record-Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Contact: "0012" <sip:5678*0012@192.168.1.21:5090>.
Server: Cisco/SPA504G-7.6.1.
Content-Length: 208.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE.
Supported: replaces.
Content-Type: application/sdp.
.
v=0.
o=- 4279560 4279560 IN IP4 192.168.1.21.
s=-.
c=IN IP4 192.168.1.21.
t=0 0.
m=audio 10350 RTP/AVP 0 101.
a=rtpmap:0 PCMU/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:20.
a=recvonly.
U 2016/04/27 18:26:28.227068 195.200.82.100:5060 -> 195.200.82.100:5060
SIP/2.0 200 OK.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 10 INVITE.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
Record-Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Record-Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Contact: "0012" <sip:5678*0012@192.168.1.21:5090;alias=176.40.9.170~5090~1>.
Server: Cisco/SPA504G-7.6.1.
Content-Length: 230.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE.
Supported: replaces.
Content-Type: application/sdp.
.
v=0.
o=- 4279560 4279560 IN IP4 195.200.82.100.
s=-.
c=IN IP4 195.200.82.100.
t=0 0.
m=audio 18330 RTP/AVP 0 101.
a=rtpmap:0 PCMU/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
a=ptime:20.
a=recvonly.
a=nortpproxy:yes.
U 2016/04/27 18:26:28.229625 195.200.82.100:5060 -> 195.200.82.100:5060
ACK sip:5678*0012@192.168.1.21:5090;alias=176.40.9.170~5090~1 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
CSeq: 10 ACK.
Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
User-Agent: Kamailio.
Content-Length: 0.
.
U 2016/04/27 18:26:28.229766 195.200.82.100:5060 -> 195.200.82.100:5060
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100>.
.
U 2016/04/27 18:26:28.231225 195.200.82.100:5090 -> 192.168.1.21:5090
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKe10e.fd2b5a550bc657c40d96f645f2258028.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 69.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100:5060>.
.
U 2016/04/27 18:26:28.231982 195.200.82.100:5090 -> 176.40.9.170:5090
ACK sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Max-Forwards: 10.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKd10e.cb3be507608b2fbdaf04da06aee9e770.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKd10e.c3dfa707000000000000000000000000.0.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
CSeq: 10 ACK.
User-Agent: Kamailio.
Content-Length: 0.
.
U 2016/04/27 18:26:28.680192 195.200.82.100:5060 -> 195.200.82.100:5060
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100>.
.
U 2016/04/27 18:26:28.680217 195.200.82.100:5090 -> 192.168.1.21:5090
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKe10e.fd2b5a550bc657c40d96f645f2258028.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 69.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100:5060>.
.
U 2016/04/27 18:26:29.680194 195.200.82.100:5060 -> 195.200.82.100:5060
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100>.
.
U 2016/04/27 18:26:29.680221 195.200.82.100:5090 -> 192.168.1.21:5090
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKe10e.fd2b5a550bc657c40d96f645f2258028.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 69.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100:5060>.
.
U 2016/04/27 18:26:31.680268 195.200.82.100:5060 -> 195.200.82.100:5060
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100>.
.
U 2016/04/27 18:26:31.680285 195.200.82.100:5090 -> 192.168.1.21:5090
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKe10e.fd2b5a550bc657c40d96f645f2258028.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 69.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100:5060>.
.
U 2016/04/27 18:26:35.680271 195.200.82.100:5060 -> 195.200.82.100:5060
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Route:
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Max-Forwards: 70.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100>.
.
U 2016/04/27 18:26:35.680289 195.200.82.100:5090 -> 192.168.1.21:5090
REFER sip:5678*0012@192.168.1.21:5090 SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKe10e.fd2b5a550bc657c40d96f645f2258028.0.
Via: SIP/2.0/UDP
195.200.82.100;rport=5060;branch=z9hG4bKe10e.3ebea453000000000000000000000000.0.
To: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
From: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
CSeq: 11 REFER.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
Max-Forwards: 69.
Content-Length: 0.
User-Agent: Kamailio.
Referred-By: sip:click2call@195.200.82.100.
Refer-To: sip:2@195.200.82.100.
Contact: <sip:click2call@195.200.82.100:5060>.
.
U 2016/04/27 18:26:35.768104 176.40.9.170:5090 -> 195.200.82.100:5090
BYE sip:click2call@195.200.82.100 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.21:5090;branch=z9hG4bK-52f6b6cd.
From: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
To: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 101 BYE.
Max-Forwards: 70.
Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
User-Agent: Cisco/SPA504G-7.6.1.
Content-Length: 0.
.
U 2016/04/27 18:26:35.775247 195.200.82.100:5090 -> 176.40.9.170:5090
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP
192.168.1.21:5090;branch=z9hG4bK-52f6b6cd;rport=5090;received=176.40.9.170.
From: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
To: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 101 BYE.
Proxy-Authenticate: Digest realm="195.200.82.100",
nonce="VyDpZ1cg6DtCHN7k+sF9kJe5E7kJEeM7".
Server: Kamailio.
Content-Length: 0.
.
U 2016/04/27 18:26:35.829205 176.40.9.170:5090 -> 195.200.82.100:5090
BYE sip:click2call@195.200.82.100 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.21:5090;branch=z9hG4bK-71815ad1.
From: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
To: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 102 BYE.
Max-Forwards: 70.
Route:
<sip:195.200.82.100:5090;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>,
<sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes>.
Proxy-Authorization: Digest
username="5678*0012",realm="195.200.82.100",nonce="VyDpZ1cg6DtCHN7k+sF9kJe5E7kJEeM7",uri="sip:click2call@195.200.82.100",algorithm=MD5,response="de1d19ccaf21367a4ac257e0bc6597f6".
User-Agent: Cisco/SPA504G-7.6.1.
Content-Length: 0.
.
U 2016/04/27 18:26:35.837892 195.200.82.100:5090 -> 195.200.82.100:5060
BYE
sip:195.200.82.100;r2=on;lr;ftag=0d71401ca91009b00be5953e2813d7e4-3cf0;nat=yes
SIP/2.0.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKec7c.384f4c63f904de41e673f3a5530293a4.0.
Via: SIP/2.0/UDP
192.168.1.21:5090;rport=5090;received=176.40.9.170;branch=z9hG4bK-71815ad1.
From: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
To: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 102 BYE.
Max-Forwards: 69.
Route: .
User-Agent: Cisco/SPA504G-7.6.1.
Content-Length: 0.
.
U 2016/04/27 18:26:35.840070 195.200.82.100:5060 -> 195.200.82.100:5090
SIP/2.0 404 Not here.
Via: SIP/2.0/UDP
195.200.82.100:5090;branch=z9hG4bKec7c.384f4c63f904de41e673f3a5530293a4.0;rport=5090.
Via: SIP/2.0/UDP
192.168.1.21:5090;rport=5090;received=176.40.9.170;branch=z9hG4bK-71815ad1.
From: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
To: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 102 BYE.
Server: Kamailio.
Content-Length: 0.
.
U 2016/04/27 18:26:35.843052 195.200.82.100:5090 -> 176.40.9.170:5090
SIP/2.0 404 Not here.
Via: SIP/2.0/UDP
192.168.1.21:5090;rport=5090;received=176.40.9.170;branch=z9hG4bK-71815ad1.
From: <sip:5678*0012@195.200.82.100>;tag=18607f6057a107a7i1.
To: <sip:click2call@195.200.82.100>;tag=0d71401ca91009b00be5953e2813d7e4-3cf0.
Call-ID: 3c0fd5c518a2e0dd-21769@195.200.82.100.
CSeq: 102 BYE.
Server: Kamailio.
Content-Length: 0.
.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
