[Spce-user] SEMS teardown request

John Murray john.murray at skyracktelecom.com
Mon Nov 19 15:01:02 EST 2012


The INVITE has a 'Diversion:' header in it and that seems to make a
difference. Ie. Without the Diversion header the call is not dropped.

 

From: spce-user-bounces at lists.sipwise.com
[mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of John Murray
Sent: 19 November 2012 19:56
To: spce-user at lists.sipwise.com
Subject: [Spce-user] SEMS teardown request

 

Hello,

 

I have SPCE setup as a transit SBC and during a specific call type SEMS
seems to drop the call after a fixed time.

I have a fairly vanilla install of SPCE v2.6 with some minor rewrites to
peers but no extra SEMS config.

 

>From the debug it looks like some sort of timer:

 

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86ef8d5700] [execute,
XMLRPC2DI.cpp:542] DEBUG: XMLRPC2DI: factory 'sbc' function 'postControlCmd'

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [run,
AmSessionProcessor.cpp:97] DEBUG: running processing loop

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [run,
AmSessionProcessor.cpp:133] DEBUG: processing events for  up to 1 sessions

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [processingCycle,
AmSession.cpp:450] DEBUG: vv S
[BW191408016191112-1188464574 at 192.168.30.10|5CC1B345-50AA8500000082

1B-EE3C0700] Connected, running, 0 UACTransPending vv

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [onControlCmd,
SBC.cpp:781] DEBUG: teardown requested from control cmd

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [stopCallTimer,
SBC.cpp:957] DEBUG: SBC: removing call timer

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [removeTimer,
AmSession.cpp:1327] DEBUG: removing timer 1

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [relayEvent,
AmB2BSession.cpp:474] DEBUG: AmB2BSession::relayEvent: to
other_id='406B6EB4-50AA85000000833A-EECC9700'

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eebc8700] [run,
AmSessionProcessor.cpp:97] DEBUG: running processing loop

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eebc8700] [run,
AmSessionProcessor.cpp:133] DEBUG: processing events for  up to 1 sessions

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [parse_sip_uri,
parse_uri.cpp:332] DEBUG: Converted URI port (5062) to int (5062)

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [set_next_hop,
trans_layer.cpp:672] DEBUG: next_hop:next_port is <127.0.0.1:5062>

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [set_destination_ip,
trans_layer.cpp:683] DEBUG: checking whether '127.0.0.1' is IP address...

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [set_destination_ip,
trans_layer.cpp:725] DEBUG: set destination to 127.0.0.1:5062

Nov 19 19:15:18 skt-salem02 sems[2200]: [#7f86eecc9700] [send_request,
trans_layer.cpp:851] DEBUG: send_request to R-URI
<sip:+441234567890 at 122.123.10.238:5060;transport=udp

> 

 

Can I change this timer somewhere ?

 

 

Regards

 

John

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121119/014b0475/attachment-0001.html>


More information about the Spce-user mailing list