Re: [OpenSIPS-Users] Opensips forward calls to incorrect port

2018-04-25 Thread Denis via Users 
Hello, Pasan! Yes, i found where new port has been changed. Thank you. -- С уважением, Денис.Best regards, Denis 24.04.2018, 12:15, "Pasan Meemaduma via Users" :Hi Denis, Did you try to print the ruri port $rp before and after changes ?. is there any function call that could cause the destination port to be change?  On Tuesday, April 24, 2018, 2:26:13 PM GMT+5:30, Denis via Users  wrote:  Hello! version: opensips 2.2.6 (x86_64/linux)flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: 5d229f5main.c compiled on 13:56:51 Apr 20 2018 with gcc 5.4.0 In attachment you can find some log of the call, where 1.1.1.1 - caller SIP UA2.2.2.2 - Opensips3.3.3.3 - callee SIP UA There is some instruction in opensips.cfg "$rU="812111";$rd="3.3.3.3";" The question is why does Opensips, in such scheme, send request to the port 5105? Thank you -- С уважением, Денис.Best regards, Denis   ___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users,___Users mailing listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips forward calls to incorrect port

2018-04-24 Thread Pasan Meemaduma via Users 
Hi Denis,
Did you try to print the ruri port $rp before and after changes ?. is there any 
function call that could cause the destination port to be change?
 

On Tuesday, April 24, 2018, 2:26:13 PM GMT+5:30, Denis via Users 
 wrote:  
 
 Hello! version: opensips 2.2.6 (x86_64/linux)flags: STATS: On, DISABLE_NAGLE, 
USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, 
FAST_LOCK-ADAPTIVE_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, 
MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, 
epoll_lt, epoll_et, sigio_rt, select.git revision: 5d229f5main.c compiled on 
13:56:51 Apr 20 2018 with gcc 5.4.0 In attachment you can find some log of the 
call, where 1.1.1.1 - caller SIP UA2.2.2.2 - Opensips3.3.3.3 - callee SIP UA 
There is some instruction in opensips.cfg "$rU="812111";$rd="3.3.3.3";" The 
question is why does Opensips, in such scheme, send request to the port 5105? 
Thank you -- С уважением, Денис.Best regards, Denis   
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips forward calls to incorrect port

2018-04-24 Thread Denis via Users 
Hello! version: opensips 2.2.6 (x86_64/linux)flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, QM_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAITADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.git revision: 5d229f5main.c compiled on 13:56:51 Apr 20 2018 with gcc 5.4.0 In attachment you can find some log of the call, where 1.1.1.1 - caller SIP UA2.2.2.2 - Opensips3.3.3.3 - callee SIP UA There is some instruction in opensips.cfg "$rU="812111";$rd="3.3.3.3";" The question is why does Opensips, in such scheme, send request to the port 5105? Thank you -- С уважением, Денис.Best regards, Denis   2018/04/24 10:34:10.601677 1.1.1.1:5060 -> 2.2.2.2:5060
INVITE sip:12345678@2.2.2.2 SIP/2.0
Record-Route: 
Via: SIP/2.0/UDP 1.1.1.1;branch=z9hG4bK7e26.2a41d06dc46ff48d206962a93914c583.0
Via: SIP/2.0/UDP 213.170.99.51:5080;branch=z9hG4bKFSB9HH5yjDN9g
Max-Forwards: 67
From:  ;tag=FUy5FtX7D4raH
To: 
Ringme-user: 0*0205*099
P-Asserted-Identity: 
Contact: 
Diversion: ;reason=unconditional
Call-ID: e107b6fc-4791-11e8-bf7d-f9235a29ebf6
CSeq: 121941561 INVITE
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REFER, NOTIFY
Supported: precondition, timer, path, replaces
Content-Type: application/sdp
Content-Length: 265

v=0
o=RINGME 1524528718 1524528719 IN IP4 213.170.99.51
s=RINGME
c=IN IP4 213.170.99.51
t=0 0
m=audio 26532 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


2018/04/24 10:34:10.604374 2.2.2.2:5060 -> 1.1.1.1:5060
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 1.1.1.1;branch=z9hG4bK7e26.2a41d06dc46ff48d206962a93914c583.0
Via: SIP/2.0/UDP 213.170.99.51:5080;branch=z9hG4bKFSB9HH5yjDN9g
From:  ;tag=FUy5FtX7D4raH
To: 
Call-ID: e107b6fc-4791-11e8-bf7d-f9235a29ebf6
CSeq: 121941561 INVITE
Content-Length: 0



2018/04/24 10:34:11.636056 2.2.2.2:5060 -> 3.3.3.3:5105
INVITE sip:812111@3.3.3.3:5105 SIP/2.0
Record-Route: 
Record-Route: 
Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK7e26.eb1b8cf4.0
Via: SIP/2.0/UDP 1.1.1.1;branch=z9hG4bK7e26.2a41d06dc46ff48d206962a93914c583.0
Via: SIP/2.0/UDP 213.170.99.51:5080;branch=z9hG4bKFSB9HH5yjDN9g
Max-Forwards: 67
From:  ;tag=FUy5FtX7D4raH
To: 
Contact: 
Diversion: ;reason=unconditional
P-Asserted-Identity: 
Remote-Party-ID: ;party=calling;screen=yes
Call-ID: e107b6fc-4791-11e8-bf7d-f9235a29ebf6
CSeq: 121941561 INVITE
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REFER, NOTIFY
Supported: precondition, timer, path, replaces
Content-Type: application/sdp
Content-Length: 287

v=0
o=RINGME 1524528718 1524528719 IN IP4 2.2.2.2
s=RINGME
c=IN IP4 2.2.2.2
t=0 0
m=audio 41308 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=nortpproxy:yes


2018/04/24 10:34:12.644198 2.2.2.2:5060 -> 3.3.3.3:5105
INVITE sip:812111@3.3.3.3:5105 SIP/2.0
Record-Route: 
Record-Route: 
Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK7e26.eb1b8cf4.0
Via: SIP/2.0/UDP 1.1.1.1;branch=z9hG4bK7e26.2a41d06dc46ff48d206962a93914c583.0
Via: SIP/2.0/UDP 213.170.99.51:5080;branch=z9hG4bKFSB9HH5yjDN9g
Max-Forwards: 67
From:  ;tag=FUy5FtX7D4raH
To: 
Contact: 
Diversion: ;reason=unconditional
P-Asserted-Identity: 
Remote-Party-ID: ;party=calling;screen=yes
Call-ID: e107b6fc-4791-11e8-bf7d-f9235a29ebf6
CSeq: 121941561 INVITE
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REFER, NOTIFY
Supported: precondition, timer, path, replaces
Content-Type: application/sdp
Content-Length: 287

v=0
o=RINGME 1524528718 1524528719 IN IP4 2.2.2.2
s=RINGME
c=IN IP4 2.2.2.2
t=0 0
m=audio 41308 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=nortpproxy:yes


2018/04/24 10:34:14.650464 2.2.2.2:5060 -> 3.3.3.3:5105
INVITE sip:812111@3.3.3.3:5105 SIP/2.0
Record-Route: 
Record-Route: 
Via: SIP/2.0/UDP 2.2.2.2:5060;branch=z9hG4bK7e26.eb1b8cf4.0
Via: SIP/2.0/UDP