Development

Development.B2bua History

Hide minor edits - Show changes to markup

April 19, 2013, at 09:47 AM by liviu -
Deleted line 1:

(:noleft:)

April 18, 2013, at 06:08 PM by 109.99.235.212 -
Changed line 2 from:
to:

(:noleft:)

April 18, 2013, at 06:05 PM by 109.99.235.212 -
Changed line 1 from:

(:noleft:)

to:

(:noright:)

April 18, 2013, at 06:05 PM by 109.99.235.212 -
Changed line 1 from:

(:nosidebars:)

to:

(:noleft:)

April 18, 2013, at 06:04 PM by 109.99.235.212 -
Changed lines 1-2 from:

(:title B2B U:)

to:

(:nosidebars:)

April 18, 2013, at 05:51 PM by 109.99.235.212 -
Added line 1:

(:title B2B U:)

April 18, 2013, at 05:48 PM by 109.99.235.212 -
Deleted line 0:

SetTmplDisplay('PageLeftFmt', 0);

April 18, 2013, at 05:48 PM by 109.99.235.212 -
Changed line 1 from:

(:notitle:)

to:

SetTmplDisplay('PageLeftFmt', 0);

April 18, 2013, at 05:47 PM by 109.99.235.212 -
Added line 1:

(:notitle:)

October 04, 2008, at 12:33 AM by Emmanuel BUU -
Changed line 5 from:
to:

Changed line 14 from:
to:

Changed line 31 from:
to:

Changed line 49 from:
to:

October 04, 2008, at 12:32 AM by Emmanuel BUU -
Changed lines 24-31 from:

on_call_hold[route_number] on_call_transfer[route_number] on_outcall_failure[route_number] on_outcall_redirect[route_number] on_call_termination[route_number] on_timer[route_number]

to:
  • on_call_hold[route_number]
  • on_call_transfer[route_number]
  • on_outcall_failure[route_number]
  • on_outcall_redirect[route_number]
  • on_call_termination[route_number]
  • on_timer[route_number]
Changed lines 40-47 from:

- limit the number of calls per user - limit the duration of call (e.g. prepaid calls) - handle redirect and call transfer locally - implement simple ACD logic - provide a server side busy / in use / free / unavailable status per user - possibily facilitate the devlopment of protocol translators (e.g. SIP <-> H.323 ). - ideally a mechanism such as memcached should be used to enable an active / active cluster of b2bua to sit on two different hosts.

to:
  • limit the number of calls per user
  • limit the duration of call (e.g. prepaid calls)
  • handle redirect and call transfer locally
  • implement simple ACD logic
  • provide a server side busy / in use / free / unavailable status per user
  • possibily facilitate the devlopment of protocol translators (e.g. SIP <-> H.323 ).
  • ideally a mechanism such as memcached should be used to enable an active / active cluster of b2bua to sit on two different hosts.
October 04, 2008, at 12:14 AM by Emmanuel BUU -
Changed lines 13-14 from:
to:

The function would pass on the message to the b2bua and stop further processing of the message.

Changed lines 54-56 from:

that would process messages issued by b2bua

to:

that would process messages issued by b2bua

a b2bua_reply() function would be available in case the proxy logic chose to direcly reply to the b2bua logic

October 04, 2008, at 12:11 AM by Emmanuel BUU -
October 04, 2008, at 12:11 AM by Emmanuel BUU -
Changed line 19 from:
    b2b_arm_timer( max call )
to:
    b2b_arm_timer( tick );
Changed lines 30-31 from:

3. New proxy routes should be define

to:

3. Inside b2bua routes,

modules functions dedicated to b2bua could be called and a way to delegate also: a call context should be defined and it should be possible to define variables that lives during the whole call duration.

for multi party calls, provision should be made to enable one context to influence another context for instance by sending events .

B2BUA should be able to enable the implementation of the following - limit the number of calls per user - limit the duration of call (e.g. prepaid calls) - handle redirect and call transfer locally - implement simple ACD logic - provide a server side busy / in use / free / unavailable status per user - possibily facilitate the devlopment of protocol translators (e.g. SIP <-> H.323 ). - ideally a mechanism such as memcached should be used to enable an active / active cluster of b2bua to sit on two different hosts.

Just dreaming.

4. New proxy routes should be define

October 04, 2008, at 12:00 AM by Emmanuel BUU -
Added lines 6-7:

Emmanuel BUU's proposal

October 03, 2008, at 11:59 PM by Emmanuel BUU -
Changed lines 4-32 from:

How it should be used?

to:

How it should be used?

1. In the proxy part, we should have a new 'core?) function that would engage the B2BUA but message could be modified / twicked before getting into b2bua. It would be the configuration's responsibility to properly call this new function.

ex:

if (is_method("INVITE") && ...) b2bua_process(route_number)

2. New routes or instruction blocks should be defined possibily in a separate conf file.

on_incoming_call[route_number] {

  1. do B2BUA actions
    b2b_arm_timer( max call )
    b2b_initiate_outcall( uri );

}

on_call_hold[route_number] on_call_transfer[route_number] on_outcall_failure[route_number] on_outcall_redirect[route_number] on_call_termination[route_number] on_timer[route_number]

3. New proxy routes should be define

outgoing_route[route_number]

that would process messages issued by b2bua

October 03, 2008, at 01:31 PM by 81.180.102.217 -
Added lines 1-4:

Development -> Sand Box -> B2BUA


How it should be used?


Page last modified on April 19, 2013, at 09:47 AM