Hi!
I’m having some issues with dispatcher and cannot get why it’s not working
Idea is to use ds_next_dst right after ds_select_dst
I’m having it like this
modparam("dispatcher", "list_file", "/tmp/dispatcher.list")
modparam("dispatcher", "flags", 2) # Enable dispather failover
modparam("dispatcher", "xavp_dst", "_dispacher_dst_list_")
…
ds_select_dst(«1», «0»);
…
# Some extra check on $du here
…
ds_next_dst();
But get in logs
WARNING: dispatcher [dispatch.c:2285]: ds_update_dst(): no xavp uri field in next destination record
But contents of /tmp/dispatcher.list is
1 sip:172.28.0.12:5060
1 sip:172.28.0.19:5060
Can I somehow dump xavp_dst var to check if ds_select_dst is correct?
kamailio 5.2.0-dev6
Regards, Igor
Hello,
I'll be the first to admit I'm a complete novice to Kamailio, but I'm learning due to necessity. I'm working on setting up Kamailio as a sip proxy (SBC?). Any help would be massively appreciated.
The desired setup would be for Kamailio to as an external connection point to authenticate the connection and reverse proxy/NAT the rest of the traffic to the asterisk server, hiding internal topology as we go.
Right now I'm using dispatcher with NAT and ALIAS to push connections to proxy@{PROXY IP} to proxy@{ASTERISK EXTERNAL IP}.
I'm running into an issue where a "Message" is being sent, forwarded to the Asterisk server and responded to. Then Asterisk spawns a new call ID "To" the proxy rather than the original requestor which of course gets a 484 response. How can I somehow associate these two messages and complete the route?
MESSAGE sip:proxy@{ASTERISK<sip:proxy@%7bASTERISK> EXTERNAL IP} SIP/2.0
Via: SIP/2.0/UDP {PROXY IP}:5060;branch=z9hG4bK0542.4d3d95c66b82f5825d9b90ba7ae88191.0
Via: SIP/2.0/UDP {CLIENT IP}:37916;received={CLIENT EXTERNAL IP};rport=37916;branch=z9hG4bKPj9b82293b-8ac4-4314-9cb8-d76716746e
Max-Forwards: 69
From: <sip:{CLIENT IP}<sip:%7bCLIENT%20IP%7d>>;tag=8aabdd54-6312-4ba4-bbe4-e713d2cf55a7
To: <sip:proxy@{PROXY IP}<sip:proxy@%7bPROXY%20IP%7d>>
Call-ID: 9d7bc193-55d9-479b-8c34-3663c3a8bf3b
CSeq: 50215 MESSAGE
Accept: text/plain, application/im-iscomposing+xml
User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f)
X-Digium-User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f)
X-Digium-AppServer-RequestType: Preconfig
X-Digium-AppServer-Preconfig-Id: ca0175e891557c4e9d6f7314cdbf4044
X-Digium-Software-Version: 4.1.1 (2fccfc8f)
X-Digium-AppServer-ID: mobileui0000000004
Content-Type: text/plain
Content-Length: 182
P-hint: outbound
Message Contents
MESSAGE sip:{PROXY<sip:%7bPROXY> IP}:5060 SIP/2.0
Via: SIP/2.0/UDP {ASTERISK EXTERNAL IP}:5060;rport;branch=z9hG4bKPj6c1bdda3-2b78-4ae2-ac19-5ec2ca8b8928
From: <sip:proxy@{ASTERISK INTERNAL IP}<sip:proxy@%7bASTERISK%20INTERNAL%20IP%7d>>;tag=79cb0374-5b41-4550-9158-304a18bb1ee6
To: <sip:{PROXY IP}<sip:%7bPROXY%20IP%7d>>
Contact: <sip:asterisk@{ASTERISK EXTERNAL IP}:5060<sip:asterisk@%7bASTERISK%20EXTERNAL%20IP%7d:5060>>
Call-ID: 94c778a4-d3b3-42c1-ac26-25664d9d37bc
CSeq: 4076 MESSAGE
X-Digium-AppServer-ResponseType: PreconfigResponse
X-Digium-AppServer-Password: ofPnRi4Pt/tGqdSYNn97tiO8ju/maPvAsG7ZeESGyUUWUgvF0xlMuhAUDVzJE866dv0+QeOowFTawa6UQJKQsQ==
X-Digium-AppServer-Session: 471800327353850017
X-Digium-AppServer-Message-Salt: 85DA16A6C8F17E46
X-Digium-AppServer-Message-Sequence: 0
X-Digium-AppServer-ID: mobileui0000000004
Max-Forwards: 70
User-Agent: Asterisk PBX 13.1.0-6.7.rl.1516160751.a9f0643
Content-Type: text/plain
Content-Length: 600
MESSAGE CONTENT
Hello,
I'll be the first to admit I'm a complete novice to Kamailio, but I'm learning due to necessity. I'm working on setting up Kamailio as a sip proxy (SBC?).
The desired setup would be for Kamailio to as an external connection point to authenticate the connection and reverse proxy/NAT the rest of the traffic to the asterisk server, hiding internal topology as we go.
Right now I'm using dispatcher with NAT and ALIAS to push connections to proxy@{PROXY IP} to proxy@{ASTERISK EXTERNAL IP}.
I'm running into an issue where a "Message" is being sent, forwarded to the Asterisk server and responded to. Then Asterisk spawns a new call ID "To" the proxy rather than the original requestor which of course gets a 484 response. How can I somehow associate these two messages and complete the route?
MESSAGE sip:proxy@{ASTERISK EXTERNAL IP} SIP/2.0
Via: SIP/2.0/UDP {PROXY IP}:5060;branch=z9hG4bK0542.4d3d95c66b82f5825d9b90ba7ae88191.0
Via: SIP/2.0/UDP {CLIENT IP}:37916;received={CLIENT EXTERNAL IP};rport=37916;branch=z9hG4bKPj9b82293b-8ac4-4314-9cb8-d76716746e
Max-Forwards: 69
From: <sip:{CLIENT IP}>;tag=8aabdd54-6312-4ba4-bbe4-e713d2cf55a7
To: <sip:proxy@{PROXY IP}>
Call-ID: 9d7bc193-55d9-479b-8c34-3663c3a8bf3b
CSeq: 50215 MESSAGE
Accept: text/plain, application/im-iscomposing+xml
User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f)
X-Digium-User-Agent: Digium Android Softphone 4.1.1 (2fccfc8f)
X-Digium-AppServer-RequestType: Preconfig
X-Digium-AppServer-Preconfig-Id: ca0175e891557c4e9d6f7314cdbf4044
X-Digium-Software-Version: 4.1.1 (2fccfc8f)
X-Digium-AppServer-ID: mobileui0000000004
Content-Type: text/plain
Content-Length: 182
P-hint: outbound
Message Contents
MESSAGE sip:{PROXY IP}:5060 SIP/2.0
Via: SIP/2.0/UDP {ASTERISK EXTERNAL IP}:5060;rport;branch=z9hG4bKPj6c1bdda3-2b78-4ae2-ac19-5ec2ca8b8928
From: <sip:proxy@{ASTERISK INTERNAL IP}>;tag=79cb0374-5b41-4550-9158-304a18bb1ee6
To: <sip:{PROXY IP}>
Contact: <sip:asterisk@{ASTERISK EXTERNAL IP}:5060>
Call-ID: 94c778a4-d3b3-42c1-ac26-25664d9d37bc
CSeq: 4076 MESSAGE
X-Digium-AppServer-ResponseType: PreconfigResponse
X-Digium-AppServer-Password: ofPnRi4Pt/tGqdSYNn97tiO8ju/maPvAsG7ZeESGyUUWUgvF0xlMuhAUDVzJE866dv0+QeOowFTawa6UQJKQsQ==
X-Digium-AppServer-Session: 471800327353850017
X-Digium-AppServer-Message-Salt: 85DA16A6C8F17E46
X-Digium-AppServer-Message-Sequence: 0
X-Digium-AppServer-ID: mobileui0000000004
Max-Forwards: 70
User-Agent: Asterisk PBX 13.1.0-6.7.rl.1516160751.a9f0643
Content-Type: text/plain
Content-Length: 600
MESSAGE CONTENT
Hi,
On an active/passive kamailio cluster, we use keepalived to move a virtual
IP between the nodes and all signaling goes to that VIP.
One of our DID providers requires us to register with every single DID we
have from them in order to receive calls for such DID (NOTE: we only want
to have the "active" kamailio sending outbound registrations to the
carrier).
My idea was to have keepalived enable all the outbound registrations when
the current node changes to MASTER and disable them when it changes to
BACKUP.
Is there a quick "enable all" or "disable all" for uac module outbound
registrations or do I have to "know in advanced" all of them and
enable/disable one by one?
In the docs we have:
*8.4. uac.reg_disable*
*Disable a remote registration record based on a filter. The command has
two parameter: attribute and value. The attribute can be: l_uuid,
l_username, r_username or auth_username. The value is what should be
matcheg against the value of the attribute in the remote registration
record.*
I don't know if there is an "all" or maybe if a wildcard would work, but
from the description it doesn't seem to.
Any ideas? Do you guys think this is taking a correct approach?
All suggestions are more than welcome!!
Thanks,
Joel.
Hello All,
If the below Requests from 40.40.40.40(Asterisk) is received by 10.10.10.10(Kamailio)
Request Line: INFO sip:3145553313@10.10.10.10:5060;alias=30.30.30.30~43508~2 SIP/2.0
Shouldn't Kamailio forward this request to 30.30.30.30? so that the '200 OK' can sent back to Asterisk for the response.
(In this scenario) Would it be ok to just force a '200 OK' back to Asterisk from Kamailio?
Thank you,
Recently encountered a delay issue, packets arrive on system but Kamailio doesn't process right away. Here are a few details, any direction on what I can do to narrow down is appreciated.
The receive queue normally sits at 0 or has random spike, when this issue occurs receive queue remains high like the below output.
Version 5.1.5
ss -4 -n -l | grep 5060
udp UNCONN 321536 0 207.241.130.2:5060 *:*
tcp LISTEN 0 128 207.241.130.2:5060 *:*
-dan
Hi i serach for a config to convert IPv6 to ipv4. My Provider give me only
IPv4 and i have 4000 Customer which have ipv6. Anybody have expierience and
a running config ?