Re: [OpenSIPS-Users] OpenSips and WebRTC ERRORS

[bharathdk]

 Hi, 

I have the similar problem and got same log message as you. When I try to
call from the chrome to local softphone(X-lite), I can get the ring but once
I answer the call gets disconnected with the message 484 not acceptable here

Next, Softphone to chrome, there is no call established and have received
the following errors
 
 ERROR:core:tcp_connect_blocking: timeout 99281 ms elapsed from 10 s
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_sync_connect: tcp_blocking_connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_connect: connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:proto_wss_send: connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]: ERROR:tm:msg_send:
send() to x.x.x.x:62235 for proto wss/6 failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:tm:t_forward_nonack: sending request failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
INFO:core:probe_max_sock_buff: using snd buffer of 244 kb
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 17
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:core:tcp_connect_blocking: timeout 99346 ms elapsed from 10 s
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_sync_connect: tcp_blocking_connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_connect: connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:proto_wss_send: connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]: ERROR:tm:msg_send:
send() to x.x.x.x:62317 for proto wss/6 failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:tm:t_forward_nonack: sending request failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
INFO:core:probe_max_sock_buff: using snd buffer of 244 kb
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 17
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:core:tcp_connect_blocking: timeout 99241 ms elapsed from 10 s
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_sync_connect: tcp_blocking_connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_connect: connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:proto_wss_send: connect failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]: ERROR:tm:msg_send:
send() to x.x.x.x:62601 for proto wss/6 failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:tm:t_forward_nonack: sending request failed
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
INFO:core:probe_max_sock_buff: using snd buffer of 244 kb
Feb  1 11:41:19 opensips-sbc-01 /usr/sbin/opensips[2811]:
INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 17
Feb  1 11:41:20 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:core:tcp_connect_blocking: timeout 99364 ms elapsed from 10 s
Feb  1 11:41:20 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_sync_connect: tcp_blocking_connect failed
Feb  1 11:41:20 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:ws_connect: connect failed
Feb  1 11:41:20 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:proto_wss:proto_wss_send: connect failed
Feb  1 11:41:20 opensips-sbc-01 /usr/sbin/opensips[2811]: ERROR:tm:msg_send:
send() to x.x.x.x:62775 for proto wss/6 failed
Feb  1 11:41:20 opensips-sbc-01 /usr/sbin/opensips[2811]:
ERROR:tm:t_forward_nonack: sending request failed


I used "opensipsctl fifo list_tcp_conns" to see whether the wss connection
between my local and server is alive. It looks fine.





--
Sent from: 
http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Registration Loss on opensips SBC

[Royee Tichauer via Users]

Hi,

We are using opensips 2.1 as an SBC component and we see that we have loss
of registrations happening once in a while. When we captured SIP we saw
that some messages are being delayed by a couple of seconds. We enabled
'exec_execute_message=5' and saw in the logs that opensips core methods
like 't_realy' and 'save' . I looked at SAR during this time and there are
no indications of CPU running high during this time.

Can you help me figure out this issue?

Thanks,
Royee

Logs:

Feb  4 17:07:23 sbc.company.com 
 /usr/sbin/opensips[29827]: WARNING:core:log_expiry: threshold exceeded :
msg processing took too long - 8912776 us.Source : SIP/2.0 200
OK#015#012Via: SIP/2.0/UDP
5060;received=;rport=5060;branch=z9hG4bK7eec.23d21053.0#015#012Via:
SIP/2.0/UDP
:5060;rport=5060;received=;branch=z9hG4bK2715962793#015#012From: ""
@.company.com:5060
>;tag=646749010#015#012To:
"###" http://sip:vh2677...@sip-190913.accounts.vocalocity.com:5060/>
>;tag=8b4547f60a700f827fe775c80b65be1b.efed#015#012Call-ID:
0_2258842442@#015#012CSeq
: 3575
REGISTER#015#012Contact: :5060
>;expires=45;received="sip:
:5060 "#015#012Server:
Vonage#015#012Content-Length: 0#015#012#015#012

Feb  4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry:
#1 is a module action : save - 8912725us - line 914

Feb  4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry:
#2 is a core action : 80 - 17us - line 1103

Feb  4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry:
#3 is a core action : 72 - 5us - line 887

Feb  4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29820]:
WARNING:core:log_expiry:
threshold exceeded : msg processing took too long - 5355695 us.Source :
REGISTER sip:.accounts.company.com:5060
 SIP/2.0#015#012Via:
SIP/2.0/UDP :5060;branch=z9hG4bK2715962793#015#012From: "###" <
sip:#@sip-.accounts.company.com:5060
>;tag=646749010#015#012To:
"" http://sip:vh2677...@sip-190913.accounts.vocalocity.com:5060/>
>#015#012Call-ID: 0_2258842442@##015#012CSeq
: 3575
REGISTER#015#012Contact: <@:5060
>#015#012Authorization: Digest
username="", realm=".accounts.company.com
",
nonce="5a773de00b19dc7d21205f1edfda504fac90296b04fb", uri="sip:
sip-###.accounts.company.com:5060
",
response="df8d6cbfd178a36913a1464920da3f06", algorithm=MD5#015#012Allow:
INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER,
SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE#015#012Max-Forwards:
69#015#012User-Agent: #015#012Expires: 3600#015#012Allow-Events:
talk,hold,conference,refer,check-sync#015#012Content-Length:
0#015#012#015#012


Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29827]:
WARNING:core:log_expiry:
#4 is a core action : 72 - 5us - line 1086

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29820]:
WARNING:core:log_expiry:
#1 is a module action : t_relay - 5355333us - line 465

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29827]:
WARNING:core:log_expiry:
#5 is a module action : ds_is_in_list - 4us - line 943

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29817]:
WARNING:core:log_expiry:
#1 is a module action : t_relay - 7375370us - line 465

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29820]:
WARNING:core:log_expiry:
#2 is a core action : 78 - 105us - line 604

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29817]:
WARNING:core:log_expiry:
#2 is a core action : 78 - 100us - line 604

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29820]:
WARNING:core:log_expiry:
#3 is a core action : 78 - 99us - line 635

Feb  4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29817]:
WARNING:core:log_expiry:
#3 is a core action : 78 - 98us - line 635
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] False Answer Supervision

[Abdoul Osséni]

Hello guys,

Is there a method to detect FAS (False Answer Supervision) in OpenSips ?

Regards

Abdoul OSSENI
Ingénieur DevOps chez Néo-Soft
Co-Fondateur de ON SERVICES
Tél : +33 601 135 167
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Dectect FAS: False Answer Supervision

[Abdoul Osséni]

Hello guys,

Is there a method to detect FAS (False Answer Supervision) in OpenSips ?

Regards

Abdoul OSSENI
Ingénieur DevOps chez Néo-Soft
Co-Fondateur de ON SERVICES
Tél : +33 601 135 167
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

[Bogdan-Andrei Iancu]

Hi Brian,

Keep in mind that you cannot make opensips act in the same time as proxy 
(as required by the load balancer) and as a end-point (as required by 
the B2BUA). Ideally is to run the two services (LB and B2B) on two 
opensips instancesin a chain.


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/02/2018 07:03 PM, Brian Southworth wrote:


Sorry my apologies.

So from the beginning opensips acts as an authorization proxy which 
passes the call on to an asterisk box based on load (using load balancer).


I am trying to get the opensips proxy to handle call transfers and I 
thought the b2bua would be the best way. Initially the refer was sent 
to the asterisk box.


On inbound calls

The call comes in from the carrier goes to asterisk, asterisk then 
passes the sip invite to the proxy which then rings the sip phone.


What I wish to achieve is a way to transfer an inbound call to an 
internal extension or external number.


Example:

Caller A receives call àcaller A places call on hold and dials caller 
B àcaller B picks up àcaller A presses cisco xfer and call is passed 
to caller B


I was hoping to achieve this using the proxy or asterisk box if possible.

I hope this helps.

Regards,

Brian Southworth

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* 02 February 2018 16:50
*To:* Brian Southworth ; OpenSIPS users 
mailling list 
*Subject:* Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no 
socket found to match RR [1][XXX.XXX.XXX.XXX:5060]


I'm a bit confused. The original report was on a record_route() / 
loose_route() matter. But you say you have opensips as B2B, so the RR 
mechanism must not be used in such a case - you act either as a 
end-point, either as a proxy - you cannot be both for the same call.


Now you have this b2b error, during a call transfer scenario. and you 
mentioned LB also :)...so I'm a bit confused - could please try to put 
all these pieces together, so I can understand what you are doing ?


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/02/2018 04:27 PM, Brian Southworth wrote:

Maybe I am doing this wrong but I wanted the B2BUA module to
handle the refer and bridge the calls.

I have the B2bUA working now. However my issue is that its not
able to send the replies.

incoming reply

b2b_reply (B2B.222.7591351.1517580641)

Feb  2 14:10:47 [22664] ERROR:tm:_reply_light: failed to generate
408 reply when a final 200 was sent out

Feb  2 14:10:47 [22664] ERROR:b2b_entities:b2b_send_reply: failed
to send reply with tm

Feb  2 14:10:47 [22664] ERROR:b2b_logic:b2b_logic_notify_reply:
Sending reply failed - 408, [B2B.452.342.1517580641]

Do you need anything else to help me debug this ? I am not sure
why its failing to pass the reply with tm, I have enabled the param:

modparam("tm", "pass_provisional_replies", 1)

I should also note that I am using the load balancer module also.
This normally deals with all call distribution. In and out.

Regards,

Brian Southworth

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* 02 February 2018 14:20
*To:* Brian Southworth 
; OpenSIPS users mailling list
 
*Subject:* Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict:
no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

Hi Brian,

Maybe that warning points to a routing error that prevents the
REFER to be route to carrier - make a sip capture to be sure the
REFER from A is properly routed and accepted by the carrier.

Regards,


Bogdan-Andrei Iancu

  


OpenSIPS Founder and Developer

   http://www.opensips-solutions.com

OpenSIPS Summit 2018

   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/02/2018 01:38 PM, Brian Southworth wrote:

Hi Bogdan,

Thank you very much, so this doesn’t have any impact on why
the call being transferred are dropped ?

I am trying to transfer a call using the refer method as that
is what the cisco phones use.

The network is setup like so opensips proxy àasterisk gateway
àcarrier

Scenario:

Inbound call comes into the phone like so: carrier àast àproxy
àphone A

Phone A needs to transfer call to phone B: Phone A dials phone
B àphone B picks up àphone A presses xfer button and call is
dropped.

Any help would be appreciated.

Regards,

Brian Southworth

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* 02 February 2018 11:29
*To:* OpenSIPS users mailling list 
   

Re: [OpenSIPS-Users] Registration Loss on opensips SBC

[Bogdan-Andrei Iancu]

Hi Royee,

what are the time values reported for 't_relay' and 'save' ? the 50ms 
threashold may not be so relevant for explaining delays of seconds.


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 02:09 PM, Royee Tichauer via Users wrote:

Hi,

We are using opensips 2.1 as an SBC component and we see that we have 
loss of registrations happening once in a while. When we captured SIP 
we saw that some messages are being delayed by a couple of seconds. We 
enabled 'exec_execute_message=5' and saw in the logs that opensips 
core methods like 't_realy' and 'save' . I looked at SAR during this 
time and there are no indications of CPU running high during this time.


Can you help me figure out this issue?

Thanks,
Royee

Logs:

Feb4 17:07:23 sbc.company.com 
 /usr/sbin/opensips[29827]: 
WARNING:core:log_expiry: threshold exceeded : msg processing took too 
long - 8912776 us.Source : SIP/2.0 200 OK#015#012Via: SIP/2.0/UDP 
5060;received=;rport=5060;branch=z9hG4bK7eec.23d21053.0#015#012Via: 
SIP/2.0/UDP 
:5060;rport=5060;received=;branch=z9hG4bK2715962793#015#012From: 
"" @.company.com:5060 
>;tag=646749010#015#012To: 
"###" >;tag=8b4547f60a700f827fe775c80b65be1b.efed#015#012Call-ID: 
0_2258842442@#015#012CSeq 
: 3575 
REGISTER#015#012Contact: :5060 
>;expires=45;received="sip::5060 
"#015#012Server: 
Vonage#015#012Content-Length: 0#015#012#015#012


Feb4 17:07:23 sbc.amz1.company.com 
 /usr/sbin/opensips[29827]: 
WARNING:core:log_expiry: #1 is a module action : save - 8912725us - 
line 914


Feb4 17:07:23 sbc.amz1.company.com 
 /usr/sbin/opensips[29827]: 
WARNING:core:log_expiry: #2 is a core action : 80 - 17us - line 1103


Feb4 17:07:23 sbc.amz1.company.com 
 /usr/sbin/opensips[29827]: 
WARNING:core:log_expiry: #3 is a core action : 72 - 5us - line 887


Feb4 17:07:23 sbc.amz1.company.com 
 /usr/sbin/opensips[29820]: 
WARNING:core:log_expiry: threshold exceeded : msg processing took too 
long - 5355695 us.Source : REGISTER sip:.accounts.company.com:5060 
 SIP/2.0#015#012Via: 
SIP/2.0/UDP :5060;branch=z9hG4bK2715962793#015#012From: "###" 
>;tag=646749010#015#012To: 
"" >#015#012Call-ID: 
0_2258842442@##015#012CSeq 
: 3575 
REGISTER#015#012Contact: <@:5060 
>#015#012Authorization: 
Digest username="", realm=".accounts.company.com 
", 
nonce="5a773de00b19dc7d21205f1edfda504fac90296b04fb", 
uri="sip:sip-###.accounts.company.com:5060 
", 
response="df8d6cbfd178a36913a1464920da3f06", 
algorithm=MD5#015#012Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, 
OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, 
MESSAGE#015#012Max-Forwards: 69#015#012User-Agent: 
#015#012Expires: 3600#015#012Allow-Events: 
talk,hold,conference,refer,check-sync#015#012Content-Length: 
0#015#012#015#012



Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29827]: 
WARNING:core:log_expiry: #4 is a core action : 72 - 5us - line 1086


Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29820]: 
WARNING:core:log_expiry: #1 is a module action : t_relay - 5355333us - 
line 465


Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29827]: 
WARNING:core:log_expiry: #5 is a module action : ds_is_in_list - 4us - 
line 943


Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29817]: 
WARNING:core:log_expiry: #1 is a module action : t_relay - 7375370us - 
line 465


Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29820]: 
WARNING:core:log_expiry: #2 is a core action : 78 - 105us - line 604


Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29817]: 
WARNING:core:log_expiry: #2 is a core action : 78 - 100us - line 604


Feb4 17:07:23 sbc.amz1.company.com 
  /usr/sbin/opensips[29820]: 
WARNING:core:log_expiry: #3 is a core action : 78 - 99us - line 635


Feb4 17

Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found to match RR [1][XXX.XXX.XXX.XXX:5060]

[Brian Southworth]

I think I get it now thank you Bogdan.

So I would forward the traffic using the opensips proxy, using the if 
(is_method(“refer”)) to the opensips box that would be the B2BUA? To bridge the 
call ?.

 
Also look forward to Opensips summit in may 😊 ill see you all there got it 
booked Saturday 😊

 
Regards,

 
Brian Southworth

 
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: 05 February 2018 15:47
To: Brian Southworth ; OpenSIPS users mailling list 

Subject: Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found 
to match RR [1][XXX.XXX.XXX.XXX:5060]

 
Hi Brian,

Keep in mind that you cannot make opensips act in the same time as proxy (as 
required by the load balancer) and as a end-point (as required by the B2BUA). 
Ideally is to run the two services (LB and B2B) on two opensips instances in a 
chain.

Best regards,



Bogdan-Andrei Iancu


 

OpenSIPS Founder and Developer


  http://www.opensips-solutions.com  


OpenSIPS Summit 2018


  http://www.opensips.org/events/Summit-2018Amsterdam 
 

On 02/02/2018 07:03 PM, Brian Southworth wrote:

Sorry my apologies.

 
So from the beginning opensips acts as an authorization proxy which passes the 
call on to an asterisk box based on load (using load balancer).

I am trying to get the opensips proxy to handle call transfers and I thought 
the b2bua would be the best way. Initially the refer was sent to the asterisk 
box.

 
On inbound calls 

The call comes in from the carrier goes to asterisk, asterisk then passes the 
sip invite to the proxy which then rings the sip phone.

 
What I wish to achieve is a way to transfer an inbound call to an internal 
extension or external number.

 
Example: 

Caller A receives call à caller A places call on hold and dials caller B à 
caller B picks up à caller A presses cisco xfer and call is passed to caller B

 
I was hoping to achieve this using the proxy or asterisk box if possible.

 
I hope this helps.

 
Regards,

 
Brian Southworth

 
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org 
 ] 
Sent: 02 February 2018 16:50
To: Brian Southworth  
 ; OpenSIPS users mailling list 
  
Subject: Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found 
to match RR [1][XXX.XXX.XXX.XXX:5060]

 
I'm a bit confused. The original report was on a record_route() / loose_route() 
matter. But you say you have opensips as B2B, so the RR mechanism must not be 
used in such a case - you act either as a end-point, either as a proxy - you 
cannot be both for the same call.

Now you have this b2b error, during a call transfer scenario. and you mentioned 
LB also :)...so I'm a bit confused - could please try to put all these pieces 
together, so I can understand what you are doing ?

Regards,




Bogdan-Andrei Iancu


 

OpenSIPS Founder and Developer


  http://www.opensips-solutions.com  


OpenSIPS Summit 2018


  http://www.opensips.org/events/Summit-2018Amsterdam 
 

On 02/02/2018 04:27 PM, Brian Southworth wrote:

Maybe I am doing this wrong but I wanted the B2BUA module to handle the refer 
and bridge the calls. 

I have the B2bUA working now. However my issue is that its not able to send the 
replies.

 
incoming reply

b2b_reply (B2B.222.7591351.1517580641)

Feb  2 14:10:47 [22664] ERROR:tm:_reply_light: failed to generate 408 reply 
when a final 200 was sent out

Feb  2 14:10:47 [22664] ERROR:b2b_entities:b2b_send_reply: failed to send reply 
with tm

Feb  2 14:10:47 [22664] ERROR:b2b_logic:b2b_logic_notify_reply: Sending reply 
failed - 408, [B2B.452.342.1517580641]

 
Do you need anything else to help me debug this ? I am not sure why its failing 
to pass the reply with tm, I have enabled the param:

modparam("tm", "pass_provisional_replies", 1)

 
I should also note that I am using the load balancer module also. This normally 
deals with all call distribution. In and out.

 
Regards,

 
Brian Southworth

 
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org 
 ] 
Sent: 02 February 2018 14:20
To: Brian Southworth  
 ; OpenSIPS users mailling list 
  
Subject: Re: [OpenSIPS-Users] [15066] WARNING:rr:after_strict: no socket found 
to match RR [1][XXX.XXX.XXX.XXX:5060]

 
Hi Brian,

Maybe that warning points to a routing error that prevents the REFER to be 
route to carrier - make a sip capture to be sure the REFER from A is properly 
routed and accepted by the carrier.

Regards,





Bogdan-Andrei Iancu


 

OpenSIPS Founder and Developer


  http://www.opensips-solutions.com  


OpenSIPS Summit 2018


  http://www.opensips.org/events/Summit-2018Amsterdam 

Re: [OpenSIPS-Users] Dectect FAS: False Answer Supervision

[Bogdan-Andrei Iancu]

Hi Abdoul,

AFAIK, you cannot detect FAS from signaling level. Even by looking at 
the RTP level it will be difficult.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 05:02 PM, Abdoul Osséni wrote:

Hello guys,

Is there a method to detect FAS (False Answer Supervision) in OpenSips ?

Regards

Abdoul OSSENI
Ingénieur DevOps chez Néo-Soft
Co-Fondateur de ON SERVICES
Tél : +33 601 135 167


___
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

Re: [OpenSIPS-Users] Registration Loss on opensips SBC

[Royee Tichauer via Users]

Hi Bogdan, as the logs show:

save - 8912725us
t_relay - 5355333us

Let me know if you have any ideas,
Thanks,
Royee




On Mon, Feb 5, 2018 at 5:50 PM Bogdan-Andrei Iancu 
wrote:

> Hi Royee,
>
> what are the time values reported for 't_relay' and 'save' ? the 50ms
> threashold may not be so relevant for explaining delays of seconds.
>
> Best regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Summit 2018
>   http://www.opensips.org/events/Summit-2018Amsterdam
>
> On 02/05/2018 02:09 PM, Royee Tichauer via Users wrote:
>
> Hi,
>
> We are using opensips 2.1 as an SBC component and we see that we have loss
> of registrations happening once in a while. When we captured SIP we saw
> that some messages are being delayed by a couple of seconds. We enabled
> 'exec_execute_message=5' and saw in the logs that opensips core methods
> like 't_realy' and 'save' . I looked at SAR during this time and there are
> no indications of CPU running high during this time.
>
> Can you help me figure out this issue?
>
> Thanks,
> Royee
>
> Logs:
>
> Feb  4 17:07:23 sbc.company.com 
>  /usr/sbin/opensips[29827]: WARNING:core:log_expiry: threshold exceeded :
> msg processing took too long - 8912776 us.Source : SIP/2.0 200
> OK#015#012Via: SIP/2.0/UDP
> 5060;received=;rport=5060;branch=z9hG4bK7eec.23d21053.0#015#012Via:
> SIP/2.0/UDP
> :5060;rport=5060;received=;branch=z9hG4bK2715962793#015#012From: ""
> @.company.com:5060
> >;tag=646749010#015#012To:
> "###"  
> >;tag=8b4547f60a700f827fe775c80b65be1b.efed#015#012Call-ID:
> 0_2258842442@#015#012CSeq
> : 3575
> REGISTER#015#012Contact: :5060
> >;expires=45;received="sip:
> :5060 "#015#012Server:
> Vonage#015#012Content-Length: 0#015#012#015#012
>
> Feb  4 17:07:23 sbc.amz1.company.com
>  /usr/sbin/opensips[29827]:
> WARNING:core:log_expiry: #1 is a module action : save - 8912725us - line
> 914
>
> Feb  4 17:07:23 sbc.amz1.company.com
>  /usr/sbin/opensips[29827]:
> WARNING:core:log_expiry: #2 is a core action : 80 - 17us - line 1103
>
> Feb  4 17:07:23 sbc.amz1.company.com
>  /usr/sbin/opensips[29827]:
> WARNING:core:log_expiry: #3 is a core action : 72 - 5us - line 887
>
> Feb  4 17:07:23 sbc.amz1.company.com
>  /usr/sbin/opensips[29820]:
> WARNING:core:log_expiry: threshold exceeded : msg processing took too
> long - 5355695 us.Source : REGISTER sip:.accounts.company.com:5060
>  SIP/2.0#015#012Via:
> SIP/2.0/UDP :5060;branch=z9hG4bK2715962793#015#012From: "###" <
> sip:#@sip-.accounts.company.com:5060
> >;tag=646749010#015#012To:
> ""  
> >#015#012Call-ID: 0_2258842442@##015#012CSeq
> : 3575
> REGISTER#015#012Contact: <@:5060
> >#015#012Authorization: Digest
> username="", realm=".accounts.company.com
> ",
> nonce="5a773de00b19dc7d21205f1edfda504fac90296b04fb", uri="sip:
> sip-###.accounts.company.com:5060
> ",
> response="df8d6cbfd178a36913a1464920da3f06", algorithm=MD5#015#012Allow:
> INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER,
> SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE#015#012Max-Forwards:
> 69#015#012User-Agent: #015#012Expires: 3600#015#012Allow-Events:
> talk,hold,conference,refer,check-sync#015#012Content-Length:
> 0#015#012#015#012
>
>
> Feb  4 17:07:23 sbc.amz1.company.com
>   /usr/sbin/opensips[29827]:
> WARNING:core:log_expiry: #4 is a core action : 72 - 5us - line 1086
>
> Feb  4 17:07:23 sbc.amz1.company.com
>   /usr/sbin/opensips[29820]:
> WARNING:core:log_expiry: #1 is a module action : t_relay - 5355333us -
> line 465
>
> Feb  4 17:07:23 sbc.amz1.company.com
>   /usr/sbin/opensips[29827]:
> WARNING:core:log_expiry: #5 is a module action : ds_is_in_list - 4us -
> line 943
>
> Feb  4 17:07:23 sbc.amz1.company.com
>   /usr/sbin/opensips[29817]:
> WARNING:core:log_expiry: #1 is a module action : t_relay - 7375370us -
> line 465
>
> Feb  4 17:07:23 sbc.amz1.company.com
>   /usr/sbin/opensips[29820]:
> WARNING:core:log_expiry: #2 is a core action : 78 -

Re: [OpenSIPS-Users] Registration Loss on opensips SBC

[Bogdan-Andrei Iancu]

Hi Royee,

Well, you need to break for each function the possible types of actions. 
Like for save():

- actual internal save()
- DB insert  if realtime mode used
- potential events triggering - do you use any usrloc related events ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 06:20 PM, Royee Tichauer wrote:

Hi Bogdan, as the logs show:

save - 8912725us
t_relay - 5355333us

Let me know if you have any ideas,
Thanks,
Royee




On Mon, Feb 5, 2018 at 5:50 PM Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Royee,

what are the time values reported for 't_relay' and 'save' ? the
50ms threashold may not be so relevant for explaining delays of
seconds.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 02:09 PM, Royee Tichauer via Users wrote:

Hi,

We are using opensips 2.1 as an SBC component and we see that we
have loss of registrations happening once in a while. When we
captured SIP we saw that some messages are being delayed by a
couple of seconds. We enabled 'exec_execute_message=5' and
saw in the logs that opensips core methods like 't_realy' and
'save' . I looked at SAR during this time and there are no
indications of CPU running high during this time.

Can you help me figure out this issue?

Thanks,
Royee

Logs:

Feb4 17:07:23 sbc.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: threshold exceeded : msg processing took
too long - 8912776 us.Source : SIP/2.0 200 OK#015#012Via:
SIP/2.0/UDP
5060;received=;rport=5060;branch=z9hG4bK7eec.23d21053.0#015#012Via:
SIP/2.0/UDP
:5060;rport=5060;received=;branch=z9hG4bK2715962793#015#012From:
"" @.company.com:5060

>;tag=646749010#015#012To:
"###" http://sip:vh2677...@sip-190913.accounts.vocalocity.com:5060/>>;tag=8b4547f60a700f827fe775c80b65be1b.efed#015#012Call-ID:
0_2258842442@#015#012CSeq
: 3575
REGISTER#015#012Contact: :5060

>;expires=45;received="sip::5060
"#015#012Server:
Vonage#015#012Content-Length: 0#015#012#015#012

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: #1 is a module action : save -
8912725us - line 914

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: #2 is a core action : 80 - 17us - line 1103

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: #3 is a core action : 72 - 5us - line 887

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29820]:
WARNING:core:log_expiry: threshold exceeded : msg processing took
too long - 5355695 us.Source : REGISTER
sip:.accounts.company.com:5060
 SIP/2.0#015#012Via:
SIP/2.0/UDP :5060;branch=z9hG4bK2715962793#015#012From: "###"
http://sip:vh2677...@sip-190913.accounts.vocalocity.com:5060/>>;tag=646749010#015#012To:
"" http://sip:vh2677...@sip-190913.accounts.vocalocity.com:5060/>>#015#012Call-ID:
0_2258842442@##015#012CSeq
: 3575
REGISTER#015#012Contact: <@:5060
>#015#012Authorization:
Digest username="", realm=".accounts.company.com
",
nonce="5a773de00b19dc7d21205f1edfda504fac90296b04fb",
uri="sip:sip-###.accounts.company.com:5060
",
response="df8d6cbfd178a36913a1464920da3f06",
algorithm=MD5#015#012Allow: INVITE, INFO, PRACK, ACK, BYE,
CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH,
UPDATE, MESSAGE#015#012Max-Forwards: 69#015#012User-Agent:
#015#012Expires: 3600#015#012Allow-Events:
talk,hold,conference,refer,check-sync#015#012Content-Length:
0#015#012#015#012


Feb4 17:07:23 sbc.amz1.company.com

 /usr/sbin/opensips[29827]: WARNING:core:log_expiry: #4 is a core
action : 72 - 5us - line 1086

Feb4 17:07:23 sbc.amz1.company.com
  /usr/sbin/opensips[29820]:
WARNING:core:log_expiry: #1 is a module action : t_re

Re: [OpenSIPS-Users] Registration Loss on opensips SBC

[Royee Tichauer via Users]

Bogdan,

Not sure I follow about breaking each function. What do you mean by 'actual
internal save()'?

DB insert is not used.

We use:

event_route[E_UL_CONTACT_UPDATE]

event_route[E_UL_CONTACT_DELETE]

event_route[E_UL_CONTACT_INSERT]

btw, we also use the mi_xmlrpc_ng constantly for monitoring if that might
have something to do with it (I saw a comment on opensips 1.6 that there
was an opensips blocking issue in some cases).

Royee



On Mon, Feb 5, 2018 at 6:34 PM Bogdan-Andrei Iancu 
wrote:

> Hi Royee,
>
> Well, you need to break for each function the possible types of actions.
> Like for save():
> - actual internal save()
> - DB insert  if realtime mode used
> - potential events triggering - do you use any usrloc related events ?
>
> Regards,
>
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Summit 2018
>   http://www.opensips.org/events/Summit-2018Amsterdam
>
> On 02/05/2018 06:20 PM, Royee Tichauer wrote:
>
> Hi Bogdan, as the logs show:
>
> save - 8912725us
> t_relay - 5355333us
>
> Let me know if you have any ideas,
> Thanks,
> Royee
>
>
>
>
> On Mon, Feb 5, 2018 at 5:50 PM Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Royee,
>>
>> what are the time values reported for 't_relay' and 'save' ? the 50ms
>> threashold may not be so relevant for explaining delays of seconds.
>>
>> Best regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   http://www.opensips-solutions.com
>> OpenSIPS Summit 2018
>>   http://www.opensips.org/events/Summit-2018Amsterdam
>>
>> On 02/05/2018 02:09 PM, Royee Tichauer via Users wrote:
>>
>> Hi,
>>
>> We are using opensips 2.1 as an SBC component and we see that we have
>> loss of registrations happening once in a while. When we captured SIP we
>> saw that some messages are being delayed by a couple of seconds. We enabled
>> 'exec_execute_message=5' and saw in the logs that opensips core methods
>> like 't_realy' and 'save' . I looked at SAR during this time and there are
>> no indications of CPU running high during this time.
>>
>> Can you help me figure out this issue?
>>
>> Thanks,
>> Royee
>>
>> Logs:
>>
>> Feb  4 17:07:23 sbc.company.com 
>>  /usr/sbin/opensips[29827]: WARNING:core:log_expiry: threshold exceeded
>> : msg processing took too long - 8912776 us.Source : SIP/2.0 200
>> OK#015#012Via: SIP/2.0/UDP
>> 5060;received=;rport=5060;branch=z9hG4bK7eec.23d21053.0#015#012Via:
>> SIP/2.0/UDP
>> :5060;rport=5060;received=;branch=z9hG4bK2715962793#015#012From: ""
>> @.company.com:5060
>> >;tag=646749010#015#012To:
>> "###" > 
>> >;tag=8b4547f60a700f827fe775c80b65be1b.efed#015#012Call-ID:
>> 0_2258842442@#015#012CSeq
>> : 3575
>> REGISTER#015#012Contact: :5060
>> >;expires=45;received="sip:
>> :5060 "#015#012Server:
>> Vonage#015#012Content-Length: 0#015#012#015#012
>>
>> Feb  4 17:07:23 sbc.amz1.company.com
>>  /usr/sbin/opensips[29827]:
>> WARNING:core:log_expiry: #1 is a module action : save - 8912725us - line
>> 914
>>
>> Feb  4 17:07:23 sbc.amz1.company.com
>>  /usr/sbin/opensips[29827]:
>> WARNING:core:log_expiry: #2 is a core action : 80 - 17us - line 1103
>>
>> Feb  4 17:07:23 sbc.amz1.company.com
>>  /usr/sbin/opensips[29827]:
>> WARNING:core:log_expiry: #3 is a core action : 72 - 5us - line 887
>>
>> Feb  4 17:07:23 sbc.amz1.company.com
>>  /usr/sbin/opensips[29820]:
>> WARNING:core:log_expiry: threshold exceeded : msg processing took too
>> long - 5355695 us.Source : REGISTER sip:.accounts.company.com:5060
>>  SIP/2.0#015#012Via:
>> SIP/2.0/UDP :5060;branch=z9hG4bK2715962793#015#012From: "###" <
>> sip:#@sip-.accounts.company.com:5060
>> >;tag=646749010#015#012To:
>> "" > 
>> >#015#012Call-ID: 0_2258842442@##015#012CSeq
>> : 3575
>> REGISTER#015#012Contact: <@:5060
>> >#015#012Authorization: Digest
>> username="", realm=".accounts.company.com
>> ",
>> nonce="5a773de00b19dc7d21205f1edfda504fac90296b04fb", uri="sip:
>> sip-###.accounts.company.com:5060
>> ",
>> response="df8d6cbfd178a36913a1464920da3f06", algorithm=MD5#015#012Allow:
>> INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER,
>> SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE#015#

Re: [OpenSIPS-Users] Registration Loss on opensips SBC

[Bogdan-Andrei Iancu]

Hi Royee,

I don't think it is related to xmlrpc - there are separate connection, 
separate processes for this.


I would rather suspect the event routes - the event is in-line handled 
in usrloc, so the save() will cover the delivery/handling of the contact 
related events. And if you do something time consuming in 
event_route[E_UL_CONTACT_INSERT] lets say, this will reflect as 
processing time for the save() function.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Summit 2018
  http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 06:44 PM, Royee Tichauer wrote:


Bogdan,

Not sure I follow about breaking each function. What do you mean by 
'actual internal save()'?


DB insert is not used.

We use:

event_route[E_UL_CONTACT_UPDATE]

event_route[E_UL_CONTACT_DELETE]

event_route[E_UL_CONTACT_INSERT]

btw, we also use the mi_xmlrpc_ng constantly for monitoring if that 
might have something to do with it (I saw a comment on opensips 1.6 
that there was an opensips blocking issue in some cases).


Royee



On Mon, Feb 5, 2018 at 6:34 PM Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Royee,

Well, you need to break for each function the possible types of
actions. Like for save():
- actual internal save()
- DB insert  if realtime mode used
- potential events triggering - do you use any usrloc related
events ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 06:20 PM, Royee Tichauer wrote:

Hi Bogdan, as the logs show:

save - 8912725us
t_relay - 5355333us

Let me know if you have any ideas,
Thanks,
Royee




On Mon, Feb 5, 2018 at 5:50 PM Bogdan-Andrei Iancu
mailto:bog...@opensips.org>> wrote:

Hi Royee,

what are the time values reported for 't_relay' and 'save' ?
the 50ms threashold may not be so relevant for explaining
delays of seconds.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Summit 2018
   http://www.opensips.org/events/Summit-2018Amsterdam

On 02/05/2018 02:09 PM, Royee Tichauer via Users wrote:

Hi,

We are using opensips 2.1 as an SBC component and we see
that we have loss of registrations happening once in a
while. When we captured SIP we saw that some messages are
being delayed by a couple of seconds. We enabled
'exec_execute_message=5' and saw in the logs that
opensips core methods like 't_realy' and 'save' . I looked
at SAR during this time and there are no indications of CPU
running high during this time.

Can you help me figure out this issue?

Thanks,
Royee

Logs:

Feb4 17:07:23 sbc.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: threshold exceeded : msg processing
took too long - 8912776 us.Source : SIP/2.0 200
OK#015#012Via: SIP/2.0/UDP

5060;received=;rport=5060;branch=z9hG4bK7eec.23d21053.0#015#012Via:
SIP/2.0/UDP
:5060;rport=5060;received=;branch=z9hG4bK2715962793#015#012From:
"" @.company.com:5060

>;tag=646749010#015#012To:
"###" http://sip:vh2677...@sip-190913.accounts.vocalocity.com:5060/>>;tag=8b4547f60a700f827fe775c80b65be1b.efed#015#012Call-ID:
0_2258842442@#015#012CSeq
: 3575
REGISTER#015#012Contact: :5060

>;expires=45;received="sip::5060
"#015#012Server:
Vonage#015#012Content-Length: 0#015#012#015#012

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: #1 is a module action : save -
8912725us - line 914

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: #2 is a core action : 80 - 17us -
line 1103

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29827]:
WARNING:core:log_expiry: #3 is a core action : 72 - 5us -
line 887

Feb4 17:07:23 sbc.amz1.company.com
 /usr/sbin/opensips[29820]:
WARNING:core:log_expiry: threshold exceeded : msg processing
took too long - 5355695 us.Source : REGISTER
sip:.accounts.company.com:5060

[OpenSIPS-Users] fix documentation link

[Pasan Meemaduma via Users]

Hi
could you please fix the hyperlink for PROTO_BIN ? its refer to same link as 
PROTO_HEP

http://www.opensips.org/Documentation/Modules-2-3
  
|  
|   
|   
|   ||

   |

  |
|  
|   |  
openSIPS | Documentation / Modules - 2.3
   |   |

  |

  |

 

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Username in DB URL

[Olle Frimanson]

Hi, we are experiencing an issue with a roleout in Microsoft Azure, where
the DB  username contains a "@" sign. This seems to be the default in MySQL
in Azure.  Is there anyway to escape this the URL for the clusterer module?

 

If you use mysql client it's typical something like

 

Mysql -h host.mysql.azure.com -u opensips@host -popensips opensips, which
works fine

 

In clustererar where we use this this translates to:

 

modparam("clusterer",
"db_url","mysql://opensips@host:opens...@host.mysql.azure.com/opensips")

 

which fails

 

Any ideas on a workaround on this?

 

BR / Olle

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Username in DB URL

[Alex Balashov]

Hah! Yeah, it's a well-known proble, same if '@' appears in the
password. I'd love to know if there's a solution too, as there appears
to be no means of escaping these.

On Mon, Feb 05, 2018 at 07:08:58PM +0100, Olle Frimanson wrote:

> Hi, we are experiencing an issue with a roleout in Microsoft Azure, where
> the DB  username contains a "@" sign. This seems to be the default in MySQL
> in Azure.  Is there anyway to escape this the URL for the clusterer module?
> 
>  
> 
> If you use mysql client it's typical something like
> 
>  
> 
> Mysql -h host.mysql.azure.com -u opensips@host -popensips opensips, which
> works fine
> 
>  
> 
> In clustererar where we use this this translates to:
> 
>  
> 
> modparam("clusterer",
> "db_url","mysql://opensips@host:opens...@host.mysql.azure.com/opensips")
> 
>  
> 
> which fails
> 
>  
> 
> Any ideas on a workaround on this?
> 
>  
> 
> BR / Olle
> 

> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-- 
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) 
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Problem with topology hiding when hairpinning a call

[Andreas Sikkema]

Hi,

I'm playing with the topology hiding module and I am running into a problem
when a call is sent from the inside of OpenSIPS to the outside, which is
then received back on the outside of OpenSIPS to sent to the inside of
OpenSIP. Calls being answered on the inside or outside work fine, it's just
with hairpinning I have this problem.

The call setup works fine, but as soon as the call is answered, I am seeing
a lot of lines like this:

Feb  5 18:52:38 [31118] WARNING:dialog:dlg_onroute: tight matching failed
for BYE with callid='ee75e7e72504b88f57959fe48d3fa...@192.168.xxx.xxx'/46,
ftag='1640688292'/10, ttag='1456089971'/10 and direction=0
Feb  5 18:52:38 [31118] WARNING:dialog:dlg_onroute: dialog identification
elements are
callid='BB_KhVSWzZ+NWR9RVVaMXFoNXpHXFtqLzVndxRWCDIoMzAPQVxcfXhma2FBV1p9fA--'/71,
caller tag='1640688292'/10, callee tag='1456089971'/10

Is there something obvious I am doing wrong? The config is basically the
generic topology hiding module example. I was hoping to not have a seperate
instance for both directions ;-)

Thanks!

-- 
Andreas
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Dectect FAS: False Answer Supervision

[Abdoul Osséni]

Thank you for your feedback.

Abdoul OSSENI
Ingénieur DevOps chez Néo-Soft
Co-Fondateur de ON SERVICES
Tél : +33 601 135 167

2018-02-05 16:57 GMT+01:00 Bogdan-Andrei Iancu :

> Hi Abdoul,
>
> AFAIK, you cannot detect FAS from signaling level. Even by looking at the
> RTP level it will be difficult.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Summit 2018
>   http://www.opensips.org/events/Summit-2018Amsterdam
>
> On 02/05/2018 05:02 PM, Abdoul Osséni wrote:
>
> Hello guys,
>
> Is there a method to detect FAS (False Answer Supervision) in OpenSips ?
>
> Regards
>
> Abdoul OSSENI
> Ingénieur DevOps chez Néo-Soft
> Co-Fondateur de ON SERVICES
> Tél : +33 601 135 167
>
>
> ___
> 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