subject:"\[OpenSIPS\-Users\] 408 timeout"

Re: [OpenSIPS-Users] 408 timeout

2017-05-02 Thread volga629


Hello Everyone,
Thank you for help.

On Mon, 1 May, 2017 at 5:49 AM, Bogdan-Andrei Iancu 
 wrote:

Hi,

The failure route is correct and you have to arm it before sending 
out the request via the request route (before the t_relay()) with 
t_on_failure("MANAGE_FAILURE")


Regards,
 Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html
On 05/01/2017 04:22 AM, volga...@networklab.ca wrote:

Hello Bogdan,
I created fail route

failure_route[MANAGE_FAILURE] {
if (t_check_status("408")) {
append_branch();
route(DISPATCH);
}

if (t_was_cancelled()) {
exit;
}
}

How I can detect that timer expire ? On which stage in reply need 
apply fail route.


volga629

On Sun, 30 Apr, 2017 at 8:44 AM, Bogdan-Andrei Iancu 
 wrote:

Hi,

OpenSIPS is generating the CANCEL due to the timeout (no answer to 
the call) - see:

http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout


If you want to get a redirect to a VM, you need to use the failure 
route in order to catch the 408 reply and create a new branch to 
the VM server.


Regards,
 Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html
On 04/29/2017 06:28 AM, volga...@networklab.ca wrote:

Hello Alex,
So what it is

2017/04/28 22:12:45.455111 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
Record-Route: 

Record-Route: 


From: "volga629" ;tag=f30d187f
To: ;tag=ZH2mc6gFgS9Fg
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Contact: 
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Content-Length: 0

OPENSIPS send to PBX

2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
CANCEL sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: 
CSeq: 2 CANCEL
Max-Forwards: 70
Reason: SIP;cause=480;text="NO_ANSWER"
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:13:14.639605 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
To: 
;tag=c88f800b416e86b8a763b24c260500d8-3c4f

From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0


On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov 
 wrote:

OpenSIPS didn't hang up anything.

On April 28, 2017 10:30:08 PM EDT, volga...@networklab.ca wrote:

Hello Everyone,
Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail.
What way possible fix it.

Please see attached trace.

volga629



-- Alex

--
Principal, Evariste Systems LLC (www.evaristesys.com)

Sent from my Google Nexus.

___
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




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

Re: [OpenSIPS-Users] 408 timeout

2017-05-01 Thread Bogdan-Andrei Iancu


Hi,

The failure route is correct and you have to arm it before sending out 
the request via the request route (before the t_relay()) with 
t_on_failure("MANAGE_FAILURE")


Regards,

Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html

On 05/01/2017 04:22 AM, volga...@networklab.ca wrote:

Hello Bogdan,
I created fail route

failure_route[MANAGE_FAILURE] {
if (t_check_status("408")) {
append_branch();
route(DISPATCH);
}

if (t_was_cancelled()) {
exit;
}
}

How I can detect that timer expire ? On which stage in reply need 
apply fail route.


volga629

On Sun, 30 Apr, 2017 at 8:44 AM, Bogdan-Andrei Iancu 
 wrote:

Hi,

OpenSIPS is generating the CANCEL due to the timeout (no answer to 
the call) - see:

http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout

If you want to get a redirect to a VM, you need to use the failure 
route in order to catch the 408 reply and create a new branch to the 
VM server.


Regards,
Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
   http://www.opensips.org/events/Summit-2017Amsterdam.html
On 04/29/2017 06:28 AM, volga...@networklab.ca wrote:

Hello Alex,
So what it is

2017/04/28 22:12:45.455111 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293

Record-Route: 
Record-Route: 


From: "volga629" ;tag=f30d187f
To: ;tag=ZH2mc6gFgS9Fg
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Contact: 
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Content-Length: 0

*OPENSIPS send to PBX*
2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
CANCEL sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: 
CSeq: 2 CANCEL
Max-Forwards: 70
Reason: SIP;cause=480;text="NO_ANSWER"
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:13:14.639605 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293

To: ;tag=c88f800b416e86b8a763b24c260500d8-3c4f
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0


On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov 
 wrote:
OpenSIPS didn't hang up anything. On April 28, 2017 10:30:08 PM 
EDT, volga...@networklab.ca  wrote:


Hello Everyone, Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail. What way possible fix it. Please see attached trace.
volga629 

-- Alex -- Principal, Evariste Systems LLC (www.evaristesys.com 
) Sent from my Google Nexus. 
___ 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




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

Re: [OpenSIPS-Users] 408 timeout

2017-04-30 Thread volga629


Hello Everyone,
Is timer reset will not help in this case ?

if (t_check_status("180") || t_check_status("183")) {
$T_fr_inv_timeout = 70;
}

volga629

On Sun, 30 Apr, 2017 at 8:44 AM, Bogdan-Andrei Iancu 
 wrote:

Hi,

OpenSIPS is generating the CANCEL due to the timeout (no answer to 
the call) - see:

http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout


If you want to get a redirect to a VM, you need to use the failure 
route in order to catch the 408 reply and create a new branch to the 
VM server.


Regards,
 Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html
On 04/29/2017 06:28 AM, volga...@networklab.ca wrote:

Hello Alex,
So what it is

2017/04/28 22:12:45.455111 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
Record-Route: 

Record-Route: 


From: "volga629" ;tag=f30d187f
To: ;tag=ZH2mc6gFgS9Fg
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Contact: 
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Content-Length: 0

OPENSIPS send to PBX

2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
CANCEL sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: 
CSeq: 2 CANCEL
Max-Forwards: 70
Reason: SIP;cause=480;text="NO_ANSWER"
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:13:14.639605 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
To: 
;tag=c88f800b416e86b8a763b24c260500d8-3c4f

From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0


On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov 
 wrote:

OpenSIPS didn't hang up anything.

On April 28, 2017 10:30:08 PM EDT, volga...@networklab.ca wrote:

Hello Everyone,
Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail.
What way possible fix it.

Please see attached trace.

volga629



-- Alex

--
Principal, Evariste Systems LLC (www.evaristesys.com)

Sent from my Google Nexus.

___
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


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

Re: [OpenSIPS-Users] 408 timeout

2017-04-30 Thread volga629


Hello Bogdan,
I created fail route

failure_route[MANAGE_FAILURE] {
   if (t_check_status("408")) {
   append_branch();
   route(DISPATCH);
   }

   if (t_was_cancelled()) {
   exit;
   }
}

How I can detect that timer expire ? On which stage in reply need apply 
fail route.


volga629

On Sun, 30 Apr, 2017 at 8:44 AM, Bogdan-Andrei Iancu 
 wrote:

Hi,

OpenSIPS is generating the CANCEL due to the timeout (no answer to 
the call) - see:

http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout


If you want to get a redirect to a VM, you need to use the failure 
route in order to catch the 408 reply and create a new branch to the 
VM server.


Regards,
 Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html
On 04/29/2017 06:28 AM, volga...@networklab.ca wrote:

Hello Alex,
So what it is

2017/04/28 22:12:45.455111 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
Record-Route: 

Record-Route: 


From: "volga629" ;tag=f30d187f
To: ;tag=ZH2mc6gFgS9Fg
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Contact: 
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Content-Length: 0

OPENSIPS send to PBX

2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
CANCEL sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: 
CSeq: 2 CANCEL
Max-Forwards: 70
Reason: SIP;cause=480;text="NO_ANSWER"
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:13:14.639605 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293
To: 
;tag=c88f800b416e86b8a763b24c260500d8-3c4f

From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0


On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov 
 wrote:

OpenSIPS didn't hang up anything.

On April 28, 2017 10:30:08 PM EDT, volga...@networklab.ca wrote:

Hello Everyone,
Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail.
What way possible fix it.

Please see attached trace.

volga629



-- Alex

--
Principal, Evariste Systems LLC (www.evaristesys.com)

Sent from my Google Nexus.

___
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


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

Re: [OpenSIPS-Users] 408 timeout

2017-04-30 Thread Bogdan-Andrei Iancu


Hi,

OpenSIPS is generating the CANCEL due to the timeout (no answer to the 
call) - see:

http://www.opensips.org/html/docs/modules/2.2.x/tm.html#fr_inv_timeout

If you want to get a redirect to a VM, you need to use the failure route 
in order to catch the 408 reply and create a new branch to the VM server.


Regards,

Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html

On 04/29/2017 06:28 AM, volga...@networklab.ca wrote:

Hello Alex,
So what it is

2017/04/28 22:12:45.455111 server_public_ip:5082 -> client_public_ip:47293
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293

Record-Route: 
Record-Route: 


From: "volga629" ;tag=f30d187f
To: ;tag=ZH2mc6gFgS9Fg
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Contact: 
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Content-Length: 0

*OPENSIPS send to PBX*
2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
CANCEL sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: 
CSeq: 2 CANCEL
Max-Forwards: 70
Reason: SIP;cause=480;text="NO_ANSWER"
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:13:14.639605 server_public_ip:5082 -> client_public_ip:47293
SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293

To: ;tag=c88f800b416e86b8a763b24c260500d8-3c4f
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0


On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov 
 wrote:
OpenSIPS didn't hang up anything. On April 28, 2017 10:30:08 PM EDT, 
volga...@networklab.ca  wrote:


Hello Everyone, Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail. What way possible fix it. Please see attached trace.
volga629 

-- Alex -- Principal, Evariste Systems LLC (www.evaristesys.com 
) Sent from my Google Nexus. 
___ 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


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

Re: [OpenSIPS-Users] 408 timeout

2017-04-28 Thread volga629


Hello Alex,
So what it is

2017/04/28 22:12:45.455111 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293

Record-Route: 
Record-Route: 


From: "volga629" ;tag=f30d187f
To: ;tag=ZH2mc6gFgS9Fg
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Contact: 
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Content-Length: 0

OPENSIPS send to PBX

2017/04/28 22:13:14.639461 10.18.130.27:5060 -> 10.18.130.26:5160
CANCEL sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bKeffd.f2504821.0
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: 
CSeq: 2 CANCEL
Max-Forwards: 70
Reason: SIP;cause=480;text="NO_ANSWER"
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:13:14.639605 server_public_ip:5082 -> 
client_public_ip:47293

SIP/2.0 408 Request Timeout
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---d06c254812b2384a;rport=47293

To: ;tag=c88f800b416e86b8a763b24c260500d8-3c4f
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 2 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0


On Fri, 28 Apr, 2017 at 11:33 PM, Alex Balashov 
 wrote:

OpenSIPS didn't hang up anything.

On April 28, 2017 10:30:08 PM EDT, volga...@networklab.ca wrote:

Hello Everyone,
Why opensips hang up session with 408 on
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
voicemail.
What way possible fix it.

Please see attached trace.

volga629



-- Alex

--
Principal, Evariste Systems LLC (www.evaristesys.com)

Sent from my Google Nexus.

___
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] 408 timeout

2017-04-28 Thread Alex Balashov

OpenSIPS didn't hang up anything. 

On April 28, 2017 10:30:08 PM EDT, volga...@networklab.ca wrote:
>Hello Everyone,
>Why opensips hang up session with 408 on 
>SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to
>voicemail.
>What way possible fix it.
>
>Please see attached trace.
>
>volga629


-- Alex

--
Principal, Evariste Systems LLC (www.evaristesys.com)

Sent from my Google Nexus.

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

[OpenSIPS-Users] 408 timeout

2017-04-28 Thread volga629


Hello Everyone,
Why opensips hang up session with 408 on 
SIP;cause=480;text="NO_ANSWER". I expected b2bua will send to voicemail.

What way possible fix it.

Please see attached trace.

volga629
2017/04/28 22:12:44.877291 client_public_ip:47293 -> server_public_ip:5082
INVITE sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/TCP 
192.168.88.164:45248;branch=z9hG4bK-524287-1---0ff878105c54f80a;rport
Max-Forwards: 70
Contact: 

To: 
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, NOTIFY, OPTIONS, UPDATE, PRACK, 
SUBSCRIBE, MESSAGE
Content-Type: application/sdp
Supported: replaces, 100rel
User-Agent: Bria Android 3.9.2 build 96033
Content-Length: 187

v=0
o=- 209131404580 1 IN IP4 192.168.88.164
s=Cpc session
c=IN IP4 client_public_ip
t=0 0
m=audio 52044 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv


2017/04/28 22:12:44.878139 server_public_ip:5082 -> client_public_ip:47293
SIP/2.0 100 Giving a try
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---0ff878105c54f80a;rport=47293
To: 
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 1 INVITE
Server: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:12:44.878360 10.18.130.27:5060 -> 10.18.130.26:5160
INVITE sip:4...@sip.company.tld SIP/2.0
Record-Route: 
Record-Route: 

Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bK100e.2220d935.0;i=61f22547
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---0ff878105c54f80a;rport=47293
Max-Forwards: 69
Contact: 

To: 
From: "volga629";tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, NOTIFY, OPTIONS, UPDATE, PRACK, 
SUBSCRIBE, MESSAGE
Content-Type: application/sdp
Supported: replaces, 100rel
User-Agent: Bria Android 3.9.2 build 96033
Content-Length: 197

v=0
o=- 209131404580 1 IN IP4 10.18.130.27
s=Cpc session
c=IN IP4 10.18.130.27
t=0 0
m=audio 11074 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=rtcp:11075


2017/04/28 22:12:44.878951 10.18.130.26:5160 -> 10.18.130.27:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bK100e.2220d935.0;i=61f22547
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---0ff878105c54f80a;rport=47293
Record-Route: 
Record-Route: 

From: "volga629" ;tag=f30d187f
To: 
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 1 INVITE
User-Agent: B2BUA01
Content-Length: 0



2017/04/28 22:12:44.884190 10.18.130.26:5160 -> 10.18.130.27:5060
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bK100e.2220d935.0;i=61f22547
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---0ff878105c54f80a;rport=47293
From: "volga629" ;tag=f30d187f
To: ;tag=y88UaB0BKgKXm
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
CSeq: 1 INVITE
User-Agent: B2BUA01
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, 
NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, 
line-seize, call-info, sla, include-session-description, presence.winfo, 
message-summary, refer
Proxy-Authenticate: Digest realm="sip.company.tld", 
nonce="ab74c0b2-a496-4d19-a66d-512678604809", algorithm=MD5, qop="auth"
Content-Length: 0



2017/04/28 22:12:44.884351 10.18.130.27:5060 -> 10.18.130.26:5160
ACK sip:4...@sip.company.tld SIP/2.0
Via: SIP/2.0/UDP 10.18.130.27:5060;branch=z9hG4bK100e.2220d935.0
From: "volga629" ;tag=f30d187f
Call-ID: 141351_rel51ZmI1MWU2ZTFkN2Y5NDUzN2M0YTYyMThiYTY0NmZjYzI
To: ;tag=y88UaB0BKgKXm
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: OpenSIPS (2.4.0-dev (x86_64/linux))
Content-Length: 0



2017/04/28 22:12:44.884728 server_public_ip:5082 -> client_public_ip:47293
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/TCP 
192.168.88.164:45248;received=client_public_ip;branch=z9hG4bK-524287-1---0ff878105c54f80a;rport=47293
From:

[OpenSIPS-Users] 408 Timeout with X-Lite

2009-07-02 Thread Gordon Ross

Starting with an empty DB, I created a domain and I created a subscriber in
OpenSIPS.

# opensipsctl domain add blah
# opensipsctl add 2...@blah 1234

Looking at the database, the user  domain are in the tables.

Firing up X-Lite, I put the following in as the SIP account details:

Display Name: Gordon
User name: 2345
Password: 1234
Authorisation user name:
Domain: blah

X-Lite comes back with a 408 - Request Timeout message.

Doing a tcpdump shows a batch of REGISTER packets. After a while, the server
responds with 408 Request Timeout packets.

Messages then starts getting:

/usr/local/sbin/opensips[14893]: ERROR:registrar:update_contacts: invalid
cseq for aor 2345

Doing a google, it seems that this problem appears when there is already an
entry in the locations table. But when I first start up OpenSIPS  XLite,
the locations table is empty !

After XLite it started, I do get entries in the locations table. One strange
thing is that the domain column is blank. (But there are entries in most of
the other columns)

Can someone enlighten me as to the stupid mistake I'm making ?

Thanks,

GTG


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

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

2009-07-02 Thread Uwe Kastens

Gordon,

Which version of opensips you are testing with? Have you enabled multi
domain support for register, urloc etc.pp.? Maybe you can post the head
of your config.

BR

Uwe



Gordon Ross schrieb:
 Starting with an empty DB, I created a domain and I created a subscriber in
 OpenSIPS.
 
 # opensipsctl domain add blah
 # opensipsctl add 2...@blah 1234
 
 Looking at the database, the user  domain are in the tables.
 
 Firing up X-Lite, I put the following in as the SIP account details:
 
 Display Name: Gordon
 User name: 2345
 Password: 1234
 Authorisation user name:
 Domain: blah
 
 X-Lite comes back with a 408 - Request Timeout message.
 
 Doing a tcpdump shows a batch of REGISTER packets. After a while, the server
 responds with 408 Request Timeout packets.
 
 Messages then starts getting:
 
 /usr/local/sbin/opensips[14893]: ERROR:registrar:update_contacts: invalid
 cseq for aor 2345
 
 Doing a google, it seems that this problem appears when there is already an
 entry in the locations table. But when I first start up OpenSIPS  XLite,
 the locations table is empty !
 
 After XLite it started, I do get entries in the locations table. One strange
 thing is that the domain column is blank. (But there are entries in most of
 the other columns)
 
 Can someone enlighten me as to the stupid mistake I'm making ?
 
 Thanks,
 
 GTG
 
 
 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users
 


-- 

kiste lat: 54.322684, lon: 10.13586

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

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

2009-07-02 Thread Gordon Ross

On 02/07/2009 09:13, Uwe Kastens ki...@kiste.org wrote:
 Which version of opensips you are testing with?

1.5.1

 Have you enabled multi
 domain support for register, urloc etc.pp.?

Yes. However, in the process of posting the config (below) I noticed that I
hadn't un-commented the line:

modparam(alias_db|auth_db|usrloc|uri_db, use_domain, 1)

I've uncommented this, cleaned out the locations table and re-started
OpenSIPS then X-Lite. The locations table now has the domain column
completed, but I'm still getting a 408 :-(

 Maybe you can post the head
 of your config.

I hope this is enough. Let me know if you want any more.

Ta.

GTG

### Modules Section 

#set module path
mpath=/usr/local/lib64/opensips/modules/

/* uncomment next line for MySQL DB support */
#loadmodule db_mysql.so
loadmodule db_postgres.so
loadmodule signaling.so
loadmodule sl.so
loadmodule tm.so
loadmodule rr.so
loadmodule maxfwd.so
loadmodule usrloc.so
loadmodule registrar.so
loadmodule textops.so
loadmodule mi_fifo.so
loadmodule uri_db.so
loadmodule uri.so
loadmodule xlog.so
loadmodule acc.so
/* uncomment next lines for MySQL based authentication support
   NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule auth.so
loadmodule auth_db.so
/* uncomment next line for aliases support
   NOTE: a DB (like db_mysql) module must be also loaded */
loadmodule alias_db.so
/* uncomment next line for multi-domain support
   NOTE: a DB (like db_mysql) module must be also loaded
   NOTE: be sure and enable multi-domain support in all used modules
 (see multi-module params section ) */
loadmodule domain.so
/* uncomment the next two lines for presence server support
   NOTE: a DB (like db_mysql) module must be also loaded */
#loadmodule presence.so
#loadmodule presence_xml.so


# - setting module-specific parameters ---


# - mi_fifo params -
modparam(mi_fifo, fifo_name, /tmp/opensips_fifo)


# - rr params -
# add value to ;lr param to cope with most of the UAs
modparam(rr, enable_full_lr, 1)
# do not append from tag to the RR (no need for this script)
modparam(rr, append_fromtag, 0)


# - registrar params -
modparam(registrar, method_filtering, 1)
/* uncomment the next line to disable parallel forking via location */
# modparam(registrar, append_branches, 0)
/* uncomment the next line not to allow more than 10 contacts per AOR */
#modparam(registrar, max_contacts, 10)


# - usrloc params -
#modparam(usrloc, db_mode,   0)
/* uncomment the following lines if you want to enable DB persistency
   for location entries */
modparam(usrloc, db_mode,   1)
modparam(usrloc, db_url,
postgres://opensips:opensip...@localhost/opensips)


# - uri_db params -
/* by default we disable the DB support in the module as we do not need it
   in this configuration */
modparam(uri_db, use_uri_table, 0)
modparam(uri_db, db_url, )


# - acc params -
/* what sepcial events should be accounted ? */
modparam(acc, early_media, 1)
modparam(acc, report_ack, 1)
modparam(acc, report_cancels, 1)
/* by default ww do not adjust the direct of the sequential requests.
   in rr module */
modparam(acc, detect_direction, 0)
/* account triggers (flags) */
modparam(acc, failed_transaction_flag, 3)
modparam(acc, log_flag, 1)
modparam(acc, log_missed_flag, 2)
/* uncomment the following lines to enable DB accounting also */
modparam(acc, db_flag, 1)
modparam(acc, db_missed_flag, 2)


# - auth_db params -
/* uncomment the following lines if you want to enable the DB based
   authentication */
modparam(auth_db, calculate_ha1, yes)
modparam(auth_db, password_column, password)
modparam(auth_db, db_url,
#   mysql://opensips:opensip...@localhost/opensips)
postgres://opensips:opensip...@localhost/opensips)
modparam(auth_db, load_credentials, )


# - alias_db params -
/* uncomment the following lines if you want to enable the DB based
   aliases */
modparam(alias_db, db_url,
#   mysql://opensips:opensip...@localhost/opensips)
postgres://opensips:opensip...@localhost/opensips)


# - domain params -
/* uncomment the following lines to enable multi-domain detection
   support */
modparam(domain, db_url,
#   mysql://opensips:opensip...@localhost/opensips)
postgres://opensips:opensip...@localhost/opensips)
modparam(domain, db_mode, 1)   # Use caching


# - multi-module params -
/* uncomment the following line if you want to enable multi-domain support
   in the modules (dafault off) */
modparam(alias_db|auth_db|usrloc|uri_db, use_domain, 1)


# - presence params -
/* uncomment the following lines if you want to enable presence */
#modparam(presence|presence_xml, db_url,
#   mysql://opensips:opensip...@localhost/opensips)
#modparam(presence_xml, force_active, 1)
#modparam(presence, server_address, sip:192.168.1.2:5060)


___
Users mailing list
Users@lists.opensips.org

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

2009-07-02 Thread Uwe Kastens

Gordon,

Strange so far. I cannot see any wrong configuration on a 1st view.
Could you see if auth is working and only writing to the USRLOC is
failing? (Maybe put some xlog statements around the register part).

The error ocurs by saving the contact into the DB. Have you tried with
another client?

BR

Uwe


Gordon Ross schrieb:
 On 02/07/2009 09:13, Uwe Kastens ki...@kiste.org wrote:
 Which version of opensips you are testing with?
 
 1.5.1
 
 Have you enabled multi
 domain support for register, urloc etc.pp.?
 
 Yes. However, in the process of posting the config (below) I noticed that I
 hadn't un-commented the line:
 
 modparam(alias_db|auth_db|usrloc|uri_db, use_domain, 1)
 
 I've uncommented this, cleaned out the locations table and re-started
 OpenSIPS then X-Lite. The locations table now has the domain column
 completed, but I'm still getting a 408 :-(
 
 Maybe you can post the head
 of your config.
 
 I hope this is enough. Let me know if you want any more.
 
 Ta.
 
 GTG
 
 ### Modules Section 
 
 #set module path
 mpath=/usr/local/lib64/opensips/modules/
 
 /* uncomment next line for MySQL DB support */
 #loadmodule db_mysql.so
 loadmodule db_postgres.so
 loadmodule signaling.so
 loadmodule sl.so
 loadmodule tm.so
 loadmodule rr.so
 loadmodule maxfwd.so
 loadmodule usrloc.so
 loadmodule registrar.so
 loadmodule textops.so
 loadmodule mi_fifo.so
 loadmodule uri_db.so
 loadmodule uri.so
 loadmodule xlog.so
 loadmodule acc.so
 /* uncomment next lines for MySQL based authentication support
NOTE: a DB (like db_mysql) module must be also loaded */
 loadmodule auth.so
 loadmodule auth_db.so
 /* uncomment next line for aliases support
NOTE: a DB (like db_mysql) module must be also loaded */
 loadmodule alias_db.so
 /* uncomment next line for multi-domain support
NOTE: a DB (like db_mysql) module must be also loaded
NOTE: be sure and enable multi-domain support in all used modules
  (see multi-module params section ) */
 loadmodule domain.so
 /* uncomment the next two lines for presence server support
NOTE: a DB (like db_mysql) module must be also loaded */
 #loadmodule presence.so
 #loadmodule presence_xml.so
 
 
 # - setting module-specific parameters ---
 
 
 # - mi_fifo params -
 modparam(mi_fifo, fifo_name, /tmp/opensips_fifo)
 
 
 # - rr params -
 # add value to ;lr param to cope with most of the UAs
 modparam(rr, enable_full_lr, 1)
 # do not append from tag to the RR (no need for this script)
 modparam(rr, append_fromtag, 0)
 
 
 # - registrar params -
 modparam(registrar, method_filtering, 1)
 /* uncomment the next line to disable parallel forking via location */
 # modparam(registrar, append_branches, 0)
 /* uncomment the next line not to allow more than 10 contacts per AOR */
 #modparam(registrar, max_contacts, 10)
 
 
 # - usrloc params -
 #modparam(usrloc, db_mode,   0)
 /* uncomment the following lines if you want to enable DB persistency
for location entries */
 modparam(usrloc, db_mode,   1)
 modparam(usrloc, db_url,
 postgres://opensips:opensip...@localhost/opensips)
 
 
 # - uri_db params -
 /* by default we disable the DB support in the module as we do not need it
in this configuration */
 modparam(uri_db, use_uri_table, 0)
 modparam(uri_db, db_url, )
 
 
 # - acc params -
 /* what sepcial events should be accounted ? */
 modparam(acc, early_media, 1)
 modparam(acc, report_ack, 1)
 modparam(acc, report_cancels, 1)
 /* by default ww do not adjust the direct of the sequential requests.
in rr module */
 modparam(acc, detect_direction, 0)
 /* account triggers (flags) */
 modparam(acc, failed_transaction_flag, 3)
 modparam(acc, log_flag, 1)
 modparam(acc, log_missed_flag, 2)
 /* uncomment the following lines to enable DB accounting also */
 modparam(acc, db_flag, 1)
 modparam(acc, db_missed_flag, 2)
 
 
 # - auth_db params -
 /* uncomment the following lines if you want to enable the DB based
authentication */
 modparam(auth_db, calculate_ha1, yes)
 modparam(auth_db, password_column, password)
 modparam(auth_db, db_url,
 #   mysql://opensips:opensip...@localhost/opensips)
 postgres://opensips:opensip...@localhost/opensips)
 modparam(auth_db, load_credentials, )
 
 
 # - alias_db params -
 /* uncomment the following lines if you want to enable the DB based
aliases */
 modparam(alias_db, db_url,
 #   mysql://opensips:opensip...@localhost/opensips)
 postgres://opensips:opensip...@localhost/opensips)
 
 
 # - domain params -
 /* uncomment the following lines to enable multi-domain detection
support */
 modparam(domain, db_url,
 #   mysql://opensips:opensip...@localhost/opensips)
 postgres://opensips:opensip...@localhost/opensips)
 modparam(domain, db_mode, 1)   # Use caching
 
 
 # - multi-module params -
 /* uncomment the following line if you want to enable multi-domain support

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

2009-07-02 Thread Gordon Ross

On 02/07/2009 09:49, Uwe Kastens ki...@kiste.org wrote:
 Strange so far. I cannot see any wrong configuration on a 1st view.
 Could you see if auth is working and only writing to the USRLOC is
 failing? (Maybe put some xlog statements around the register part).

Small progress. I discovered another missed un-comment. Now I'm getting 401
rejected messages.

A few xlogs show it's going into the www_challenge function and not coming
back:

if (is_method(REGISTER))
{
# authenticate the REGISTER requests (uncomment to enable
auth)
if (!www_authorize(, subscriber))
{
www_challenge(, 1);
exit;
}
(blah)
}

GTG


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

Re: [OpenSIPS-Users] 408 timeout

Re: [OpenSIPS-Users] 408 timeout

Re: [OpenSIPS-Users] 408 timeout

Re: [OpenSIPS-Users] 408 timeout

Re: [OpenSIPS-Users] 408 timeout

Re: [OpenSIPS-Users] 408 timeout

Re: [OpenSIPS-Users] 408 timeout

[OpenSIPS-Users] 408 timeout

[OpenSIPS-Users] 408 Timeout with X-Lite

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

Re: [OpenSIPS-Users] 408 Timeout with X-Lite

13 matches

Site Navigation

Mail list logo

Footer information