Hi,
I fixed some uac From rewriting issues in commit e1d1c774c9ac0b4d,
however even with the latest versions I'm still seeing corruption in
From headers when they are rewritten for the whole dialogue
(from_restore_mode=auto, the default).
I spent some time analyzing the problem and the problem seems to be
connected with the fact that only the bitwise difference of the
original and modified URI are stored (XOR). The only purpose for this
appears to be the idea to save only the difference in the rr params
instead of two full URIs.
However, it appears that in many cases (especially call transfer) the
From header will be altered during dialogue. This is explicitly allowed
in RFC 3261 § 20.20:
The From header field indicates the initiator of the request. This
may be different from the initiator of the dialog.
I've seen this in practise with few commercial SIP stacks. Sometimes
the changes are minor, or even trivial - but with the difference
encoding having even one character changed (e.g. case), being deleted or
added will result in the whole header being corrupted.
I'm now wondering if we should just store both URIs in the rr params.
While taking little more space, it should fix us sending garbage to the
wire (which usually results in dropped call as the remote will reject
the garbage messages).
Any better ideas?
Cheers,
Timo
Hi
I'm trying to configure kamailio version 3.3.0 to be a Session Border
Controller which only purpose is to handle far-end-nat.
On the far end site I have a SIP client with IP '192.168.1.2' which is
NAT'ed to IP 'zz.zz.85.230'. The SIP ALG is disabled on the NAT
firewall. The SIP client is communicating with the kamailio server and
the Kamailio server is forwarding every thing to an Avaya SIP server
'xx.xx.173.15' and vice versa. The kamilio is konfigured to do this
stateless.
The REGISTER and SUBSCRIBE part works fine. The kamailio is using the
'Via:' field and I also needed to do subst on the 'Contact:' field in
order for our SIP server to communicate back to the kamailio. But when
I get to the NOTIFY packet from the SIP server to the kamailio there
is no 'Via:' field or any other information about the SIP clients
IP/port and the Kamailio just sends back 'SIP/2.0 404 Not here.' to
the SIP server.
I guess that this can not be solved with a statless kamailio?
I guess that I need some kind of state table in the kamailio - is that
possible without doing REGISTER directly with the kamailio?
Any other good ideas are welcome?
Cheers,
Martin
Tell me if need more info the issue?
-----
#
T xx.xx.173.15:38059 -> yy.yy.159.211:5060 [AP]
NOTIFY sip:2001012@yy.yy.159.211:5060;transport=TCP SIP/2.0.
Call-ID: NjQ5ZDNlYzRjOWFjMzMzN2JlYzAwMTg4ODYwZTJlYWY..
From: "2001012"
<sip:2001012@bsosip.domain.dk>;tag=-667195155*1*016asm-callprocessing.sar229435981~1342570131099~1170998434~1.
To: "2001012" <sip:2001012@bsosip.domain.dk>;tag=7ca0af7d.
CSeq: 3 NOTIFY.
Contact: <sip:xx.xx.173.14:15060>.
Via: SIP/2.0/TCP
xx.xx.173.15;branch=z9hG4bK4DEAAD0E478B838008189457-AP;ft=xx.xx.173.15~13c4.
Via: SIP/2.0/UDP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838008189457.
Via: SIP/2.0/TCP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838018189455.
Event: message-summary.
Content-Type: application/simple-message-summary.
Content-Length: 69.
Subscription-State: active;expires=299.
Max-Forwards: 68.
User-Agent: AVAYA-SM-6.1.4.0.614005.
.
Messages-Waiting: no.
Message-Account: sip:2001012@bsosip.domain.dk.
##
T yy.yy.159.211:5060 -> xx.xx.173.15:38059 [AP]
SIP/2.0 404 Not here.
Call-ID: NjQ5ZDNlYzRjOWFjMzMzN2JlYzAwMTg4ODYwZTJlYWY..
From: "2001012"
<sip:2001012@bsosip.domain.dk>;tag=-667195155*1*016asm-callprocessing.sar229435981~1342570131099~1170998434~1.
To: "2001012" <sip:2001012@bsosip.domain.dk>;tag=7ca0af7d.
CSeq: 3 NOTIFY.
Via: SIP/2.0/TCP
xx.xx.173.15;branch=z9hG4bK4DEAAD0E478B838008189457-AP;ft=xx.xx.173.15~13c4;rport=38059.
Via: SIP/2.0/UDP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838008189457.
Via: SIP/2.0/TCP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838018189455.
Server: kamailio (3.3.0 (i386/linux)).
Content-Length: 0.
.
#
T xx.xx.173.15:38059 -> yy.yy.159.211:5060 [A]
......
#
T yy.yy.159.211:5060 -> xx.xx.173.15:38059 [AP]
SIP/2.0 404 Not here.
Call-ID: NjQ5ZDNlYzRjOWFjMzMzN2JlYzAwMTg4ODYwZTJlYWY..
From: "2001012"
<sip:2001012@bsosip.domain.dk>;tag=-667195155*1*016asm-callprocessing.sar229435981~1342570131099~1170998434~1.
To: "2001012" <sip:2001012@bsosip.domain.dk>;tag=7ca0af7d.
CSeq: 3 NOTIFY.
Via: SIP/2.0/TCP
xx.xx.173.15;rport=38059;branch=z9hG4bK4DEAAD0E478B838008189457-AP;ft=xx.xx.173.15~13c4.
Via: SIP/2.0/UDP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838008189457.
Via: SIP/2.0/TCP xx.xx.173.14:15070;branch=z9hG4bK4DEAAD0E478B838018189455.
Server: kamailio (3.3.0 (i386/linux)).
Content-Length: 0.
-----
Dear All Experts,
I am following the steps given at
http://kb.asipto.com/kamailio:presence:k31-made-simple. I want to
compile kamailio with stun support. So guide me that what will be the
command to do it. As per the
given command :
*make PREFIX=/usr/local/kamailio-3.1-xcap FLAVOUR=kamailio \
include_modules="db_mysql presence presence_xml xhttp xcap_server" cfg
what text should i use to make stun module.
*
--
Best Regards,
Vijay Thakur
(Assistant Manager - Networks)
Mobile : +91 8744018065
Mail : vijay.thakur(a)loopmethods.com
Loop IT Methods Private Limited
1st Floor, B-10, Sector-7, Noida, (U.P) India
Ph: +91 120 305 3481,82 (INDIA), +1 347 468 8631 (USA), +61 390 011 178 (AUS)
Fax: +91 971 728 330
Web: www.loopmethods.com
LOOP Disclaimer -------------------------------------------------------------------------------------------------
This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
-----------------------------------------------------------------------------------------------------------------
Hello,
Kamailio v3.2.4 is out -- this is a minor release packaged from previous
stable branch, GIT 3.2. Anyone running 3.2.x should update to it in
order to benefit of latest fixes, there is no change required to be done
in database structure or configuration file, just re-install over the
old deployment. As usual, a backup is recommended to be in the safe side.
More details about this release at:
* http://www.kamailio.org/w/2012/07/kamailio-v3-2-4-released/
New installations should start with latest stable series 3.3.x, at this
time latest Kamailio version being v3.3.0.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Hello,
please keep the mailing list cc-ed, private emails from mailing list
discussions will be ignored.
On 7/19/12 8:28 AM, Durmuş Ali Öztürk wrote:
> Hi Daniel,
>
> Thank you for your advise. I have found the problem, I thought it is
> enough to subscribe with my own ID but fact is I have to subscribe to
> the buddies of my contact list.This was not clear for me at the beginning.
ok, great you found it.
>
> It is better to subscribe only to the presence.wmi? Or should I
> susbcribe to presence and presence.wmi?
Do you mean presence mwi? mwi is for message waiting indication, like
voicemail, so you get notifications when someone leaves you a message on
the media server.
Cheers,
Daniel
>
> Best Regards,
> Ali
>
> 2012/7/18 Daniel-Constantin Mierla <miconda(a)gmail.com
> <mailto:miconda@gmail.com>>
>
> Hello,
>
> when you updated the presence rules via xcap, did you executed the
> function to update the notifiers as well? I mean the two function at:
>
> http://kamailio.org/docs/modules/stable/modules_k/presence.html#id2496049
>
> Cheers,
> Daniel
>
>
>
> On 7/18/12 9:29 AM, Durmuş Ali Öztürk wrote:
>> Hi All,
>>
>> I am trying to subscribe to the presence event but unfortunaly I
>> am getting following Notify with the "Subscription-State:
>> pending" status.
>>
>> NOTIFY sip:5000@192.168.127.138:55583
>> <http://sip:5000@192.168.127.138:55583> SIP/2.0
>> Via: SIP/2.0/UDP 192.168.127.230;branch=z9hG4bK6a8e.19cd7bb7.0
>> To: sip:5000@192.168.127.230
>> <mailto:sip%3A5000@192.168.127.230>;tag=2786be25cb234561b8dea2e067fd769c-5000
>> From: sip:5000@192.168.127.230
>> <mailto:sip%3A5000@192.168.127.230>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6a8e
>> CSeq: 2 NOTIFY
>> Call-ID: e4ec6031-99e1-de11-8845-5000@vvt-laptop
>> Content-Length: 0
>> User-Agent: kamailio (3.2.3 (i386/linux))
>> Max-Forwards: 70
>> Event: presence
>> Contact: <sip:192.168.127.230:5060;transport=udp>
>> Subscription-State: pending;expires=3670
>>
>>
>> For the implemantation I followed the guide from
>> http://kb.asipto.com/kamailio:presence:k31-made-simple
>>
>> The xcap table has already the needed resource-lists
>> and pres-rules record.
>>
>> Is there another guide exists for the presence module which can
>> be helpfully for me?
>>
>> Thank you in advance
>> ali
>>
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -http://www.asipto.com
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda
> Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -http://asipto.com/u/katu
> Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -http://asipto.com/u/kpw
>
>
--
Daniel-Constantin Mierla -http://www.asipto.com
http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -http://asipto.com/u/kpw
Hi All,
I am trying to subscribe to the presence event but unfortunaly I am getting
following Notify with the "Subscription-State: pending" status.
NOTIFY sip:5000@192.168.127.138:55583 SIP/2.0
Via: SIP/2.0/UDP 192.168.127.230;branch=z9hG4bK6a8e.19cd7bb7.0
To: sip:5000@192.168.127.230;tag=2786be25cb234561b8dea2e067fd769c-5000
From: sip:5000@192.168.127.230;tag=a6a1c5f60faecf035a1ae5b6e96e979a-6a8e
CSeq: 2 NOTIFY
Call-ID: e4ec6031-99e1-de11-8845-5000@vvt-laptop
Content-Length: 0
User-Agent: kamailio (3.2.3 (i386/linux))
Max-Forwards: 70
Event: presence
Contact: <sip:192.168.127.230:5060;transport=udp>
Subscription-State: pending;expires=3670
For the implemantation I followed the guide from
http://kb.asipto.com/kamailio:presence:k31-made-simple
The xcap table has already the needed resource-lists and pres-rules record.
Is there another guide exists for the presence module which can be
helpfully for me?
Thank you in advance
ali
Hi,
Kamailio server is behind our company's softswitch and acts as a sip
application server.
I notice that there are calls that the softswitch replied with 503 "service
unavailable" and kamailio sent to the originator leg 500 "service
unavaileable".
When kamailio recieved 504 or 502 it sends them back as is. shouldn't it be
the same with 503?
It also does not have a "to tag" in the CDR. And the "to tag" in the 503
that was recieved is not equal to the 500 reply "to tag" kamailio sent
back.
any ideas?
BR,
Uri
A whole ago, it was mentioned on the list that there was some bug or issue in Topoh that precluded the use of the actual host IP of the proxy as the Topoh spoof address.
Is that still true in 3.3? Or has that been fixed some time ago?
Thanks!
-- Alex
--
Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/
Kamailio 3.3.0
I have a variable $var(s:dst). It can store either a number or IP.
How do I check to determine whether it is a number of IP?
I tried the following and it did not work:
If ($var(s:dst) =~ "^\d+\.\d+\.\d+\.\d+$"){
It is a IP.
}else{
It is a Number
}
Thanks
Gary