Hello,
I'm having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@ sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060 <IP_ASTERISK/KAMAILIO>:4060.
When I'm doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
Hello,
Im still experienced this issue where the port looks to be rewritten.
Its like the ACK is not consider to be in loose route.
Any idea on this? Thanks.
Regards,
Igor.
De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : mercredi 20 août 2014 18:39 À : sr-users@lists.sip-router.org Objet : Relaying ACK to Asterisk
Hello,
Im having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@ sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060 <IP_ASTERISK/KAMAILIO>:4060.
When Im doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
On 9/23/14, 8:47 AM, Igor Potjevlesch wrote:
Hello,
I'm still experienced this issue where the port looks to be rewritten.
It's like the ACK is not consider to be in loose route.
I loops inside because you probably do not have the port number in the alias definition. Make sure you put like this: alias=IP_ASTERISK/KAMAILIO:5060
When doing the loose route it looks at the alias and sees a different port so it will route it to the Asterisk accordingly.
Any idea on this? Thanks.
Regards,
Igor.
*De :*Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] *Envoyé :* mercredi 20 août 2014 18:39 *À :* sr-users@lists.sip-router.org *Objet :* Relaying ACK to Asterisk
Hello,
I'm having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When I'm doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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
Hello,
I try with the alias=<IP_ASTERISK/KAMAILIO> :5060 but again, the ACK still not relayed.
Please note that Asterisk and Kamailio are on the same server.
Regards,
Igor.
De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé : mardi 23 septembre 2014 15:53 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/23/14, 8:47 AM, Igor Potjevlesch wrote:
Hello,
Im still experienced this issue where the port looks to be rewritten.
Its like the ACK is not consider to be in loose route.
I loops inside because you probably do not have the port number in the alias definition. Make sure you put like this: alias=IP_ASTERISK/KAMAILIO:5060
When doing the loose route it looks at the alias and sees a different port so it will route it to the Asterisk accordingly.
Any idea on this? Thanks.
Regards,
Igor.
De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : mercredi 20 août 2014 18:39 À : sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org Objet : Relaying ACK to Asterisk
Hello,
Im having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@ sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060 <IP_ASTERISK/KAMAILIO>:4060.
When Im doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
dump the whole ACK packet received by Kamailio, and the packet looped by Kamailio
regards Klaus
On 20.08.2014 18:38, Igor Potjevlesch wrote:
Hello,
I’m having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When I’m doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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
Hello Klaus,
Initial ACK sent by the UAC looks like this:
Request-Line: ACK sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060 SIP/2.0 Method: ACK Request-URI: sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060
Message Header Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-8b319388;rport Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-8b319388 RPort: rport From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=189f3d3bf3f9656o0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 189f3d3bf3f9656o0 To: sip:123@sip.fqdn.tld;tag=as091754f8 SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as091754f8 Call-ID: 39fe9b57-95f574a2@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 70 Route: <sip:<IP_ASTERISK/KAMAILIO>;lr=on> Route URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Route Host Part: <IP_ASTERISK/KAMAILIO> Route URI parameter: lr=on Proxy-Authorization: Digest username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGIx1Qhh5sqtS7GwGWBKTLvJX 7H3Oqe",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="103a027b58eb628ea 003dd827ea1d669" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGIx1Qhh5sqtS7GwGWBKTLvJX7H3Oqe" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "103a027b58eb628ea003dd827ea1d669" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Next, the ACK on lo interface who loops: User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) <-- here the Dst Port has already been modified by Kamailio.
Session Initiation Protocol (ACK) Request-Line: ACK sip:<IP_ASTERISK/KAMAILIO>;lr=on SIP/2.0 Method: ACK Request-URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Request-URI Host Part: <IP_ASTERISK/KAMAILIO> Message Header Via: SIP/2.0/UDP <IP_ASTERISK/KAMAILIO>;branch=z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Transport: UDP Sent-by Address: <IP_ASTERISK/KAMAILIO> Branch: z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-2182fea0;rport=5060 Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-2182fea0 RPort: 5060 From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=8ab714d39e8cfdefo0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 8ab714d39e8cfdefo0 To: sip:123@sip.fqdn.tld;tag=as116ed4ed SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as116ed4ed Call-ID: 66c39a3-eb259f5f@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 69 Proxy-Authorization: Digest username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGI/FQhh9AbPlF1XLMvEaetTC aGX9CM",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="55ca32ecf5ab7b328 95fd2e545d7033c" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGI/FQhh9AbPlF1XLMvEaetTCaGX9CM" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "55ca32ecf5ab7b32895fd2e545d7033c" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : mardi 23 septembre 2014 16:04 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
dump the whole ACK packet received by Kamailio, and the packet looped by Kamailio
regards Klaus
On 20.08.2014 18:38, Igor Potjevlesch wrote:
Hello,
Im having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When Im doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi!
1. Please post SIP messages in a more readable format. Your dump seems like Wireshark. Best way to get nice SIP messages is ngrep:
ngrep -t -q -P "" -Wbyline port 5060
Another good method is in Wireshark to activate "display RAW SIP message" in the SIP protocol dissector options. Then you can right-click and copy printable characters to the clipboard
2. It seems that Kamailio does not change the port in the RURI. Instead it copies the whole Route header into the RURI. This is usually only done when converting from loose-routing to strict routing, or when doing strict routing. Thus, for some reason it seems that Kamailio has problems with losse-routing this message.
You have to set the log level to "debug" and then watch the log message when routing the ACK. You should see some message be lr module how it routes the message. (there are a plenty of " == myself" messages when Kamailio tries to find out if a message is addressed to itself, eg if the URI in the Route header is itself - this may indicate errors in the alias= config).
regards Klaus
On 23.09.2014 17:34, Igor Potjevlesch wrote:
Hello Klaus,
Initial ACK sent by the UAC looks like this:
Request-Line: ACK sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060 SIP/2.0 Method: ACK Request-URI: sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060
Message Header Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-8b319388;rport Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-8b319388 RPort: rport From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=189f3d3bf3f9656o0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 189f3d3bf3f9656o0 To: sip:123@sip.fqdn.tld;tag=as091754f8 SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as091754f8 Call-ID: 39fe9b57-95f574a2@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 70 Route: <sip:<IP_ASTERISK/KAMAILIO>;lr=on> Route URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Route Host Part: <IP_ASTERISK/KAMAILIO> Route URI parameter: lr=on Proxy-Authorization: Digest username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGIx1Qhh5sqtS7GwGWBKTLvJX 7H3Oqe",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="103a027b58eb628ea 003dd827ea1d669" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGIx1Qhh5sqtS7GwGWBKTLvJX7H3Oqe" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "103a027b58eb628ea003dd827ea1d669" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Next, the ACK on lo interface who loops: User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) <-- here the Dst Port has already been modified by Kamailio.
Session Initiation Protocol (ACK) Request-Line: ACK sip:<IP_ASTERISK/KAMAILIO>;lr=on SIP/2.0 Method: ACK Request-URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Request-URI Host Part: <IP_ASTERISK/KAMAILIO> Message Header Via: SIP/2.0/UDP <IP_ASTERISK/KAMAILIO>;branch=z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Transport: UDP Sent-by Address: <IP_ASTERISK/KAMAILIO> Branch: z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-2182fea0;rport=5060 Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-2182fea0 RPort: 5060 From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=8ab714d39e8cfdefo0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 8ab714d39e8cfdefo0 To: sip:123@sip.fqdn.tld;tag=as116ed4ed SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as116ed4ed Call-ID: 66c39a3-eb259f5f@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 69 Proxy-Authorization: Digest username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGI/FQhh9AbPlF1XLMvEaetTC aGX9CM",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="55ca32ecf5ab7b328 95fd2e545d7033c" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGI/FQhh9AbPlF1XLMvEaetTCaGX9CM" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "55ca32ecf5ab7b32895fd2e545d7033c" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : mardi 23 septembre 2014 16:04 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
dump the whole ACK packet received by Kamailio, and the packet looped by Kamailio
regards Klaus
On 20.08.2014 18:38, Igor Potjevlesch wrote:
Hello,
I’m having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When I’m doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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 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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi Klaus,
Sorry for the bad format. I took a debug:
DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request: DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <ACK> DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:7000ABCDEFGHI@<IP_KAMAILIO_ASTERISK>:4060> DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-9982f067>; state=6 DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via DEBUG: <core> [receive.c:152]: receive_msg(): After parse_msg... DEBUG: <core> [receive.c:193]: receive_msg(): preparing to run routing scripts... DEBUG : sl_filter_ACK: to late to be a local ACK! ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=12 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=137 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=131 a=25 n=mf_process_maxfwd_header DEBUG: add_param: tag=as2da80cc9 DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 DEBUG: get_hdr_field: <To> [40]; uri=[sip:123@<sip.domain.tld>] DEBUG: to body [<sip:123@<sip.domain.tld>>] DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <102> <ACK> DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=144 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=137 a=26 n=sanity_check DEBUG: get_hdr_body : content_length=0 DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header DEBUG: add_param: tag=3f76daa87288aa1co0 DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=156 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=144 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=158 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=158 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=15 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=381 a=55 n=force_rport ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=391 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=382 a=25 n=nat_uac_test DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(10.141.0.5, 10.141.0.5, 0) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=391 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=29 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=18 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=29 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=210 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=168 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=207 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=171 a=24 n=loose_route DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=172 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=434 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=430 a=24 n=isdsturiset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=434 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=173 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=177 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=179 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=398 a=24 n=is_request ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=404 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=399 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=403 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=400 a=25 n=check_route_param ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=408 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=41 n=isflagset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=25 n=isbflagset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=406 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=94 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=91 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=97 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=94 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=101 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=97 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=104 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=101 a=24 n=t_relay DEBUG: t_newtran: msg id=2 , global msg id=1 , T on entrance=(nil) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=20645, isACK=1 DEBUG: t_lookup_request: e2e proxy ACK found DEBUG: totag for e2e ACK found: 0 DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fd048cb11c8, callback type 4, id 0 entered DEBUG: acc [acc_logic.c:571]: tmcb_func(): acc callback called for t(0x7fd048cb11c8) event type 4, reply code -4 DEBUG: pv [pv_core.c:977]: pv_get_pai(): no P-Asserted-Identity header DEBUG: tm [t_funcs.c:311]: t_relay_to(): SER: forwarding ACK statelessly DEBUG: <core> [resolve.c:1243]: srv_sip_resolvehost(): srv_sip_resolvehost: <IP_KAMAILIO_ASTERISK>:0 proto=0 DEBUG: <core> [resolve.c:1365]: srv_sip_resolvehost(): srv_sip_resolvehost: returning 0x899660 (<IP_KAMAILIO_ASTERISK>:5060 proto=1) DEBUG: MD5 calculated: a94f044fe5475bf0527047c599436de3 DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(10.141.0.5, 10.141.0.5, 0)
I guess that there are something useful here but if you can help to "decrypt".
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : mercredi 24 septembre 2014 10:21 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Hi!
1. Please post SIP messages in a more readable format. Your dump seems like Wireshark. Best way to get nice SIP messages is ngrep:
ngrep -t -q -P "" -Wbyline port 5060
Another good method is in Wireshark to activate "display RAW SIP message" in the SIP protocol dissector options. Then you can right-click and copy printable characters to the clipboard
2. It seems that Kamailio does not change the port in the RURI. Instead it copies the whole Route header into the RURI. This is usually only done when converting from loose-routing to strict routing, or when doing strict routing. Thus, for some reason it seems that Kamailio has problems with losse-routing this message.
You have to set the log level to "debug" and then watch the log message when routing the ACK. You should see some message be lr module how it routes the message. (there are a plenty of " == myself" messages when Kamailio tries to find out if a message is addressed to itself, eg if the URI in the Route header is itself - this may indicate errors in the alias= config).
regards Klaus
On 23.09.2014 17:34, Igor Potjevlesch wrote:
Hello Klaus,
Initial ACK sent by the UAC looks like this:
Request-Line: ACK sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060 SIP/2.0 Method: ACK Request-URI: sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060
Message Header Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-8b319388;rport Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-8b319388 RPort: rport From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=189f3d3bf3f9656o0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 189f3d3bf3f9656o0 To: sip:123@sip.fqdn.tld;tag=as091754f8 SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as091754f8 Call-ID: 39fe9b57-95f574a2@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 70 Route: <sip:<IP_ASTERISK/KAMAILIO>;lr=on> Route URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Route Host Part: <IP_ASTERISK/KAMAILIO> Route URI parameter: lr=on Proxy-Authorization: Digest
username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGIx1Qhh5sqtS7GwGWBKTLvJX
7H3Oqe",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="103a027b58eb628ea
003dd827ea1d669" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGIx1Qhh5sqtS7GwGWBKTLvJX7H3Oqe" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "103a027b58eb628ea003dd827ea1d669" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Next, the ACK on lo interface who loops: User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) <-- here the Dst Port has already been modified by Kamailio.
Session Initiation Protocol (ACK) Request-Line: ACK sip:<IP_ASTERISK/KAMAILIO>;lr=on SIP/2.0 Method: ACK Request-URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Request-URI Host Part: <IP_ASTERISK/KAMAILIO> Message Header Via: SIP/2.0/UDP
<IP_ASTERISK/KAMAILIO>;branch=z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0
Transport: UDP Sent-by Address: <IP_ASTERISK/KAMAILIO> Branch: z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-2182fea0;rport=5060 Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-2182fea0 RPort: 5060 From: 22 <sip:ABCDEFGHIJ@sip.fqdn.tld>;tag=8ab714d39e8cfdefo0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 8ab714d39e8cfdefo0 To: <sip:123@sip.fqdn.tld>;tag=as116ed4ed SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as116ed4ed Call-ID: 66c39a3-eb259f5f@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 69 Proxy-Authorization: Digest
username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGI/FQhh9AbPlF1XLMvEaetTC
aGX9CM",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="55ca32ecf5ab7b328
95fd2e545d7033c" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGI/FQhh9AbPlF1XLMvEaetTCaGX9CM" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "55ca32ecf5ab7b32895fd2e545d7033c" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus
Darilion
Envoyé : mardi 23 septembre 2014 16:04 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
dump the whole ACK packet received by Kamailio, and the packet looped by Kamailio
regards Klaus
On 20.08.2014 18:38, Igor Potjevlesch wrote:
Hello,
Im having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When Im doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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 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 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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 9/24/14, 12:41 PM, Igor Potjevlesch wrote:
Hi Klaus,
Sorry for the bad format. I took a debug:
DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request: DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <ACK> DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:7000ABCDEFGHI@<IP_KAMAILIO_ASTERISK>:4060> DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-9982f067>; state=6 DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via DEBUG: <core> [receive.c:152]: receive_msg(): After parse_msg... DEBUG: <core> [receive.c:193]: receive_msg(): preparing to run routing scripts... DEBUG : sl_filter_ACK: to late to be a local ACK! ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=12 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=137 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=131 a=25 n=mf_process_maxfwd_header DEBUG: add_param: tag=as2da80cc9 DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 DEBUG: get_hdr_field: <To> [40]; uri=[sip:123@<sip.domain.tld>] DEBUG: to body [<sip:123@<sip.domain.tld>>] DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <102> <ACK> DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=144 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=137 a=26 n=sanity_check DEBUG: get_hdr_body : content_length=0 DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header DEBUG: add_param: tag=3f76daa87288aa1co0 DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=156 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=144 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=158 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=158 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=15 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=381 a=55 n=force_rport ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=391 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=382 a=25 n=nat_uac_test DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(10.141.0.5, 10.141.0.5, 0) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=391 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=29 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=18 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=29 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=210 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=168 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=207 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=171 a=24 n=loose_route DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=172 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=434 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=430 a=24 n=isdsturiset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=434 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=173 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=177 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=179 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=398 a=24 n=is_request ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=404 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=399 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=403 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=400 a=25 n=check_route_param ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=408 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=41 n=isflagset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=25 n=isbflagset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=406 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=94 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=91 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=97 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=94 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=101 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=97 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=104 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=101 a=24 n=t_relay DEBUG: t_newtran: msg id=2 , global msg id=1 , T on entrance=(nil) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=20645, isACK=1 DEBUG: t_lookup_request: e2e proxy ACK found DEBUG: totag for e2e ACK found: 0 DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fd048cb11c8, callback type 4, id 0 entered DEBUG: acc [acc_logic.c:571]: tmcb_func(): acc callback called for t(0x7fd048cb11c8) event type 4, reply code -4 DEBUG: pv [pv_core.c:977]: pv_get_pai(): no P-Asserted-Identity header DEBUG: tm [t_funcs.c:311]: t_relay_to(): SER: forwarding ACK statelessly DEBUG: <core> [resolve.c:1243]: srv_sip_resolvehost(): srv_sip_resolvehost: <IP_KAMAILIO_ASTERISK>:0 proto=0 DEBUG: <core> [resolve.c:1365]: srv_sip_resolvehost(): srv_sip_resolvehost: returning 0x899660 (<IP_KAMAILIO_ASTERISK>:5060 proto=1) DEBUG: MD5 calculated: a94f044fe5475bf0527047c599436de3 DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(10.141.0.5, 10.141.0.5, 0)
I guess that there are something useful here but if you can help to "decrypt".
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : mercredi 24 septembre 2014 10:21 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Hi!
- Please post SIP messages in a more readable format. Your dump seems
like Wireshark. Best way to get nice SIP messages is ngrep:
ngrep -t -q -P "" -Wbyline port 5060
Another good method is in Wireshark to activate "display RAW SIP message" in the SIP protocol dissector options. Then you can right-click and copy printable characters to the clipboard
- It seems that Kamailio does not change the port in the RURI. Instead
it copies the whole Route header into the RURI. This is usually only done when converting from loose-routing to strict routing, or when doing strict routing. Thus, for some reason it seems that Kamailio has problems with losse-routing this message.
You have to set the log level to "debug" and then watch the log message when routing the ACK. You should see some message be lr module how it routes the message. (there are a plenty of " == myself" messages when Kamailio tries to find out if a message is addressed to itself, eg if the URI in the Route header is itself - this may indicate errors in the alias= config).
regards Klaus
On 23.09.2014 17:34, Igor Potjevlesch wrote:
Hello Klaus,
Initial ACK sent by the UAC looks like this:
Request-Line: ACK sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060 SIP/2.0 Method: ACK Request-URI: sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060
Message Header Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-8b319388;rport Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-8b319388 RPort: rport From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=189f3d3bf3f9656o0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 189f3d3bf3f9656o0 To: sip:123@sip.fqdn.tld;tag=as091754f8 SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as091754f8 Call-ID: 39fe9b57-95f574a2@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 70 Route: <sip:<IP_ASTERISK/KAMAILIO>;lr=on> Route URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Route Host Part: <IP_ASTERISK/KAMAILIO> Route URI parameter: lr=on Proxy-Authorization: Digest
username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGIx1Qhh5sqtS7GwGWBKTLvJX 7H3Oqe",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="103a027b58eb628ea
003dd827ea1d669" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGIx1Qhh5sqtS7GwGWBKTLvJX7H3Oqe" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "103a027b58eb628ea003dd827ea1d669" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Next, the ACK on lo interface who loops: User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) <-- here the Dst Port has already been modified by Kamailio.
Session Initiation Protocol (ACK) Request-Line: ACK sip:<IP_ASTERISK/KAMAILIO>;lr=on SIP/2.0 Method: ACK Request-URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Request-URI Host Part: <IP_ASTERISK/KAMAILIO> Message Header Via: SIP/2.0/UDP
<IP_ASTERISK/KAMAILIO>;branch=z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0
Transport: UDP Sent-by Address: <IP_ASTERISK/KAMAILIO> Branch: z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-2182fea0;rport=5060 Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-2182fea0 RPort: 5060 From: 22 <sip:ABCDEFGHIJ@sip.fqdn.tld>;tag=8ab714d39e8cfdefo0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 8ab714d39e8cfdefo0 To: <sip:123@sip.fqdn.tld>;tag=as116ed4ed SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as116ed4ed Call-ID: 66c39a3-eb259f5f@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 69 Proxy-Authorization: Digest
username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGI/FQhh9AbPlF1XLMvEaetTC aGX9CM",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="55ca32ecf5ab7b328
95fd2e545d7033c" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGI/FQhh9AbPlF1XLMvEaetTCaGX9CM" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "55ca32ecf5ab7b32895fd2e545d7033c" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus
Darilion
Envoyé : mardi 23 septembre 2014 16:04 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
dump the whole ACK packet received by Kamailio, and the packet looped by Kamailio
regards Klaus
On 20.08.2014 18:38, Igor Potjevlesch wrote:
Hello,
I’m having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When I’m doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What does your "alias" line look like in your Kamalio config?
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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 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 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 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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello Andres,
He looks like this: alias=sip.domain.tld:5060
I also tried to add Alias=<IP_KAMAILIO/ASTERISK>:5060 and :4060
The only difference I seen in the debug is this line: > DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me. The line was not present if I set aliases with :4060. But the behaviour looks to be the same.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé : mercredi 24 septembre 2014 20:49 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/24/14, 12:41 PM, Igor Potjevlesch wrote:
Hi Klaus,
Sorry for the bad format. I took a debug:
DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request: DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <ACK> DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: <sip:7000ABCDEFGHI@<IP_KAMAILIO_ASTERISK>:4060> DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-9982f067>; state=6 DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via DEBUG: <core> [receive.c:152]: receive_msg(): After parse_msg... DEBUG: <core> [receive.c:193]: receive_msg(): preparing to run routing scripts... DEBUG : sl_filter_ACK: to late to be a local ACK! ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=12 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=137 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=131 a=25 n=mf_process_maxfwd_header DEBUG: add_param: tag=as2da80cc9 DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 DEBUG: get_hdr_field: <To> [40]; uri=[sip:123@<sip.domain.tld>] DEBUG: to body [<sip:123@<sip.domain.tld>>] DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <102> <ACK> DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=144 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=137 a=26 n=sanity_check DEBUG: get_hdr_body : content_length=0 DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header DEBUG: add_param: tag=3f76daa87288aa1co0 DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=156 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=144 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=158 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=158 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=159 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=160 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=161 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=162 a=26 n=replace ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=15 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=381 a=55 n=force_rport ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=391 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=382 a=25 n=nat_uac_test DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(10.141.0.5, 10.141.0.5, 0) ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=391 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=29 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=18 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=29 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=210 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=168 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=207 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=171 a=24 n=loose_route DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=172 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=434 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=430 a=24 n=isdsturiset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=434 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=173 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=177 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=179 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=398 a=24 n=is_request ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=404 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=399 a=24 n=has_totag DEBUG: siputils [checks.c:106]: has_totag(): totag found ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=403 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=400 a=25 n=check_route_param ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=408 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=41 n=isflagset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=405 a=25 n=isbflagset ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=406 a=2 n=return ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=185 a=5 n=route ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=94 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=91 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=97 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=94 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=101 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=97 a=25 n=is_method ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=104 a=16 n=if ERROR: *** cfgtrace: c=[/usr/local/etc/kamailio/kamailio.cfg] l=101 a=24 n=t_relay DEBUG: t_newtran: msg id=2 , global msg id=1 , T on entrance=(nil) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=20645, isACK=1 DEBUG: t_lookup_request: e2e proxy ACK found DEBUG: totag for e2e ACK found: 0 DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fd048cb11c8, callback type 4, id 0 entered DEBUG: acc [acc_logic.c:571]: tmcb_func(): acc callback called for t(0x7fd048cb11c8) event type 4, reply code -4 DEBUG: pv [pv_core.c:977]: pv_get_pai(): no P-Asserted-Identity header DEBUG: tm [t_funcs.c:311]: t_relay_to(): SER: forwarding ACK statelessly DEBUG: <core> [resolve.c:1243]: srv_sip_resolvehost():
srv_sip_resolvehost:
<IP_KAMAILIO_ASTERISK>:0 proto=0 DEBUG: <core> [resolve.c:1365]: srv_sip_resolvehost():
srv_sip_resolvehost:
returning 0x899660 (<IP_KAMAILIO_ASTERISK>:5060 proto=1) DEBUG: MD5 calculated: a94f044fe5475bf0527047c599436de3 DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(10.141.0.5, 10.141.0.5, 0)
I guess that there are something useful here but if you can help to "decrypt".
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : mercredi 24 septembre 2014 10:21 À : Kamailio (SER)
- Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Hi!
- Please post SIP messages in a more readable format. Your dump seems
like Wireshark. Best way to get nice SIP messages is ngrep:
ngrep -t -q -P "" -Wbyline port 5060
Another good method is in Wireshark to activate "display RAW SIP message" in the SIP protocol dissector options. Then you can right-click and copy printable characters to the clipboard
- It seems that Kamailio does not change the port in the RURI.
Instead it copies the whole Route header into the RURI. This is usually only done when converting from loose-routing to strict routing, or when doing strict routing. Thus, for some reason it seems that Kamailio has problems with losse-routing this message.
You have to set the log level to "debug" and then watch the log message when routing the ACK. You should see some message be lr module how it routes the message. (there are a plenty of " == myself" messages when Kamailio tries to find out if a message is addressed to itself, eg if the URI in the Route header is itself - this may indicate errors in the alias= config).
regards Klaus
On 23.09.2014 17:34, Igor Potjevlesch wrote:
Hello Klaus,
Initial ACK sent by the UAC looks like this:
Request-Line: ACK sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060 SIP/2.0 Method: ACK Request-URI: sip:700ABCDEFGHIJ@<IP_ASTERISK/KAMAILIO>:4060
Message Header Via: SIP/2.0/UDP <IP_UAC>:5060;branch=z9hG4bK-8b319388;rport Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-8b319388 RPort: rport From: 22 sip:ABCDEFGHIJ@sip.fqdn.tld;tag=189f3d3bf3f9656o0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 189f3d3bf3f9656o0 To: sip:123@sip.fqdn.tld;tag=as091754f8 SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as091754f8 Call-ID: 39fe9b57-95f574a2@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 70 Route: <sip:<IP_ASTERISK/KAMAILIO>;lr=on> Route URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Route Host Part: <IP_ASTERISK/KAMAILIO> Route URI parameter: lr=on Proxy-Authorization: Digest
username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGIx1Qhh5sqtS7GwGWB KTLvJX 7H3Oqe",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="103a027b58e b628ea
003dd827ea1d669" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGIx1Qhh5sqtS7GwGWBKTLvJX7H3Oqe" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "103a027b58eb628ea003dd827ea1d669" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Next, the ACK on lo interface who loops: User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) <-- here the Dst Port has already been modified by Kamailio.
Session Initiation Protocol (ACK) Request-Line: ACK sip:<IP_ASTERISK/KAMAILIO>;lr=on SIP/2.0 Method: ACK Request-URI: sip:<IP_ASTERISK/KAMAILIO>;lr=on Request-URI Host Part: <IP_ASTERISK/KAMAILIO> Message Header Via: SIP/2.0/UDP
<IP_ASTERISK/KAMAILIO>;branch=z9hG4bKe717.d7d6c57a10035735c483450629da 8b62.0
Transport: UDP Sent-by Address: <IP_ASTERISK/KAMAILIO> Branch: z9hG4bKe717.d7d6c57a10035735c483450629da8b62.0 Via: SIP/2.0/UDP
<IP_UAC>:5060;branch=z9hG4bK-2182fea0;rport=5060
Transport: UDP Sent-by Address: <IP_UAC> Sent-by port: 5060 Branch: z9hG4bK-2182fea0 RPort: 5060 From: 22 <sip:ABCDEFGHIJ@sip.fqdn.tld>;tag=8ab714d39e8cfdefo0 SIP Display info: 22 SIP from address: sip:ABCDEFGHIJ@sip.fqdn.tld SIP from address User Part: ABCDEFGHIJ SIP from address Host Part: sip.fqdn.tld SIP from tag: 8ab714d39e8cfdefo0 To: <sip:123@sip.fqdn.tld>;tag=as116ed4ed SIP to address: sip:123@sip.fqdn.tld SIP to address User Part: 123 SIP to address Host Part: sip.fqdn.tld SIP to tag: as116ed4ed Call-ID: 66c39a3-eb259f5f@<IP_UAC> CSeq: 102 ACK Sequence Number: 102 Method: ACK Max-Forwards: 69 Proxy-Authorization: Digest
username="ABCDEFGHIJ",realm="sip.fqdn.tld",nonce="VCGI/FQhh9AbPlF1XLMv EaetTC aGX9CM",uri="sip:123@sip.fqdn.tld",algorithm=MD5,response="55ca32ecf5a b7b328
95fd2e545d7033c" Authentication Scheme: Digest Username: "ABCDEFGHIJ" Realm: "sip.fqdn.tld" Nonce Value: "VCGI/FQhh9AbPlF1XLMvEaetTCaGX9CM" Authentication URI: "sip:123@sip.fqdn.tld" Algorithm: MD5 Digest Authentication Response: "55ca32ecf5ab7b32895fd2e545d7033c" Contact: 22 <sip:ABCDEFGHIJ@<IP_UAC>:5060> SIP Display info: 22 Contact URI: sip:ABCDEFGHIJ@<IP_UAC>:5060 Contact URI User Part: ABCDEFGHIJ Contact URI Host Part: <IP_UAC> Contact URI Host Port: 5060 User-Agent: Linksys/WRP400-2.00.32 Content-Length: 0
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus
Darilion
Envoyé : mardi 23 septembre 2014 16:04 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
dump the whole ACK packet received by Kamailio, and the packet looped by Kamailio
regards Klaus
On 20.08.2014 18:38, Igor Potjevlesch wrote:
Hello,
Im having trouble with this scenario (Kamailio and Asterisk are working on the same server, Asterisk listens on 4060 instead of 5060): the UAC sends an ACK request with the following R-URI: sip:955*95%23@<IP_ASTERISK/KAMAILIO>:4060 sip:955*95%23@%3cIP_ASTERISK/KAMAILIO%3e:4060.
When Im doing a capture on loopback interface, I just see an ACK request from IP <IP_ASTERISK/KAMAILIO>:5060 to IP <IP_ASTERISK/KAMAILIO>:5060.
So the ACK seems to loop inside Kamailio.
What does your "alias" line look like in your Kamalio config?
What could explain that the good port defined by the UAC is deleted?
Regards,
Igor.
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 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 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 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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Technical Support http://www.cellroute.net
_______________________________________________ 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
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
_______________________________________________ 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
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table, the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], Relay Forbidden\n"); sl_send_reply("403", "Relay Forbidden"); }; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
_______________________________________________ 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
On 9/25/14, 9:17 AM, Igor Potjevlesch wrote:
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table,
As I said before, what you need to use is IP_KAMAILIO/ASTERISK:5060. If you use it without the port, it will match also when directed to your Asterisk server residing on the same IP and loop inside Kamalio without being routed properly.
the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], Relay Forbidden\n"); sl_send_reply("403", "Relay Forbidden"); }; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Yes you're right. But many SIP requests come with R-URI sip:<IP_KAMAILIO/ASTERISK> without the port. So the test "is_from_local" fails.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé : jeudi 25 septembre 2014 15:54 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/25/14, 9:17 AM, Igor Potjevlesch wrote:
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table,
As I said before, what you need to use is IP_KAMAILIO/ASTERISK:5060. If you use it without the port, it will match also when directed to your Asterisk server residing on the same IP and loop inside Kamalio without being routed properly.
the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si]
flags=[$mf], Relay Forbidden\n");
sl_send_reply("403", "Relay Forbidden"); }; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Technical Support http://www.cellroute.net
_______________________________________________ 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
Hello,
Any idea on how can I manage this? I'm still stuck in this issue. If I remove the IP address from domain table, it works but many REGISTER fails because the R-URI only contains sip:<IP_KAMAILIO/ASTERISK> without the port.
Many thanks for your help.
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 17:45 À : andres@telesip.net; 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Yes you're right. But many SIP requests come with R-URI sip:<IP_KAMAILIO/ASTERISK> without the port. So the test "is_from_local" fails.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé : jeudi 25 septembre 2014 15:54 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/25/14, 9:17 AM, Igor Potjevlesch wrote:
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table,
As I said before, what you need to use is IP_KAMAILIO/ASTERISK:5060. If you use it without the port, it will match also when directed to your Asterisk server residing on the same IP and loop inside Kamalio without being routed properly.
the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si]
flags=[$mf], Relay Forbidden\n");
sl_send_reply("403", "Relay Forbidden"); }; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Technical Support http://www.cellroute.net
_______________________________________________ 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
Hello,
if you have a multi-domain environment, how you can decide which domain is the user in if the address is the IP of the server? Or do you have unique usernames across all domains and the location is not in multi-domain mode?
Cheers, Daniel
On 01/10/14 11:18, Igor Potjevlesch wrote:
Hello,
Any idea on how can I manage this? I'm still stuck in this issue. If I remove the IP address from domain table, it works but many REGISTER fails because the R-URI only contains sip:<IP_KAMAILIO/ASTERISK> without the port.
Many thanks for your help.
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 17:45 À : andres@telesip.net; 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Yes you're right. But many SIP requests come with R-URI sip:<IP_KAMAILIO/ASTERISK> without the port. So the test "is_from_local" fails.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé : jeudi 25 septembre 2014 15:54 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/25/14, 9:17 AM, Igor Potjevlesch wrote:
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table,
As I said before, what you need to use is IP_KAMAILIO/ASTERISK:5060. If you use it without the port, it will match also when directed to your Asterisk server residing on the same IP and loop inside Kamalio without being routed properly.
the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si]
flags=[$mf], Relay Forbidden\n");
sl_send_reply("403", "Relay Forbidden"); }; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Technical Support http://www.cellroute.net
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Multi-domain is used for backward compatibility with some customers. Also, some equipment don't support a domain name. So they must communicate directly with the IP address. That's why Kamailio must be reachable on these domains, but in the configuration, subscriber and location use the same domain.
Unfortunately, Asterisk listens on the same IP address, but not the same port.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Daniel-Constantin Mierla Envoyé : mercredi 1 octobre 2014 13:53 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Hello,
if you have a multi-domain environment, how you can decide which domain is the user in if the address is the IP of the server? Or do you have unique usernames across all domains and the location is not in multi-domain mode?
Cheers, Daniel
On 01/10/14 11:18, Igor Potjevlesch wrote:
Hello,
Any idea on how can I manage this? I'm still stuck in this issue. If I remove the IP address from domain table, it works but many REGISTER fails because the R-URI only contains sip:<IP_KAMAILIO/ASTERISK> without the port.
Many thanks for your help.
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 17:45 À : andres@telesip.net; 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Yes you're right. But many SIP requests come with R-URI sip:<IP_KAMAILIO/ASTERISK> without the port. So the test "is_from_local" fails.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé
:
jeudi 25 septembre 2014 15:54 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/25/14, 9:17 AM, Igor Potjevlesch wrote:
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table,
As I said before, what you need to use is IP_KAMAILIO/ASTERISK:5060. If you use it without the port, it will match also when directed to your Asterisk server residing on the same IP and loop inside Kamalio without being routed properly.
the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si]
flags=[$mf], Relay Forbidden\n");
sl_send_reply("403", "Relay
Forbidden");
}; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info
- checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] ==
[<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info
- checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info
- checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] ==
[192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info
- checking if port 5060 (advertise 0) matches port 4060
DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't
matched.
This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Technical Support http://www.cellroute.net
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
_______________________________________________ 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
One option is to map usernames to domains using mtree or hashtable, then when a request comes in with IP, rewrite domain ($rd) -- something like:
if(uri==myself && is_ip("$rd")) ) { $rd = ... }
Cheers, Daniel
On 01/10/14 14:12, Igor Potjevlesch wrote:
Hello,
Multi-domain is used for backward compatibility with some customers. Also, some equipment don't support a domain name. So they must communicate directly with the IP address. That's why Kamailio must be reachable on these domains, but in the configuration, subscriber and location use the same domain.
Unfortunately, Asterisk listens on the same IP address, but not the same port.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Daniel-Constantin Mierla Envoyé : mercredi 1 octobre 2014 13:53 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Hello,
if you have a multi-domain environment, how you can decide which domain is the user in if the address is the IP of the server? Or do you have unique usernames across all domains and the location is not in multi-domain mode?
Cheers, Daniel
On 01/10/14 11:18, Igor Potjevlesch wrote:
Hello,
Any idea on how can I manage this? I'm still stuck in this issue. If I remove the IP address from domain table, it works but many REGISTER fails because the R-URI only contains sip:<IP_KAMAILIO/ASTERISK> without the port.
Many thanks for your help.
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 17:45 À : andres@telesip.net; 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Yes you're right. But many SIP requests come with R-URI sip:<IP_KAMAILIO/ASTERISK> without the port. So the test "is_from_local" fails.
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Andres Envoyé
:
jeudi 25 septembre 2014 15:54 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
On 9/25/14, 9:17 AM, Igor Potjevlesch wrote:
I just identified that if "IP_KAMAILIO/ASTERISK" is set into domain table,
As I said before, what you need to use is IP_KAMAILIO/ASTERISK:5060. If you use it without the port, it will match also when directed to your Asterisk server residing on the same IP and loop inside Kamalio without being routed properly.
the issue occured. If I delete this entry, the ACK is properly relayed.
The thing is that I use domain table for this check in REQ_INIT: if (!has_totag()) { if (!is_uri_host_local()) { if (is_from_local() || allow_trusted()) { xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si] flags=[$mf], From the trusted source\n"); return; } else{ xlog("L_WARN","time=[$Tf] call id=[$ci] call seq=[$cs] contact header=[$ct] from uri=[$fu] from tag=[$ft] request's method=[$rm] request's uri=[$ru] to uri=[$tu] to tag=[$tt] sip message id=[$mi] process id=[$pp] ip source=[$si]
flags=[$mf], Relay Forbidden\n");
sl_send_reply("403", "Relay
Forbidden");
}; exit; }; };
Regards,
Igor.
-----Message d'origine----- De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com] Envoyé : jeudi 25 septembre 2014 14:45 À : 'Kamailio (SER) - Users Mailing List' Objet : RE: [SR-Users] Relaying ACK to Asterisk
Hello Klaus,
Thank you for the translation ;) Here is the config:
/* add local domain aliases */ alias=sip.domain.tld
/* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ listen=udp:IP_KAMAILIO/ASTERISK:5060 listen=udp:IP_KAMAILIO_LAN:5060
The 'domain' table is populated as follow: id | domain 1 <IP_KAMAILIO/ASTERISK> 2 sip.domain.tld 3 <hostname_server> 4 sip.domain.tld
Regards,
Igor.
-----Message d'origine----- De : sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] De la part de Klaus Darilion Envoyé : jeudi 25 septembre 2014 13:16 À : Kamailio (SER) - Users Mailing List Objet : Re: [SR-Users] Relaying ACK to Asterisk
Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info
- checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] ==
[<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info
- checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info
- checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] ==
[192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info
- checking if port 5060 (advertise 0) matches port 4060
DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't
matched.
This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Technical Support http://www.cellroute.net
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 list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
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