[cc: changed to serusers, which is publicly archived]
There is no B2BUA support in SER. You can try to use some
existing B2BUA implementation. You can use SER along with
B2BUA too -- they interact using SIP. You just need to set
SIP routing accordingly to your scenario.
You should be perhaps warned of some side-effect of use
of the B2BUA technology. The root reason is B2BUAs break
the end-to-end model, in which intelligence lives in
end-devices. With B2BUA, you put a fair amount of work
on a network entity. That breaks e2e security, degrades
scalability and robustness -- B2BUA's failure affect
all existing calls.
-Jiri
At 01:18 PM 12/4/2002, Igor Vasiliev wrote:
>Hello,
>
> I've tryed to read B2BUA's doc that I could find.
>But I did't properly understand how it should works with SER.
>Should SER redirect any INVITE(e.t.c) request to B2BUA,
>and after B2BUA'll try to establish connection with a calee
>on behalf of B2BUA?
> Or B2BUA should be stand alone programm working without
>any SIP proxy server?
> Then how could it find out callee location.
>
>Could anybody describe me shortly a interaction model
>between caller B2BUA SER and callee.
>Just general example.
>
>Thanks
>Igor Vasiliev
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>_______________________________________________
>Serhelp mailing list
>serhelp(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serhelp
--
Jiri Kuthan http://iptel.org/~jiri/
1st draft and just a bit rough. I'm also stuck with MS-Word
for my editer at the moment, so there's some extra garbage in
the file.
Let me know if I'm on the right track, if there are sections
that need more detail, less detail or elimination.
I'm considering an addition section on client configuration,
but I'm not sure how valuable that will be. (Cisco 79XX, MSN,
any other clients I can get my hands on...)
Dan
At 08:07 AM 12/3/2002, Dan Austin wrote:
[...]
>I've got a question I thought to send to the SERUsers list, but I'm not
>sure if enough people have signed up yet.
Don't worry -- all our developers are on the serusers list too.
We just plan to shift the help from our developers to the SER
community to have more cycles for development.
>I have a Cisco 7940 that I've converted to SIP and can place calls from,
>both to PSTN numbers and to uri's registered with my server. The odd
>part is that the phone does not seem to request the presence feature, so
>I can not route calls to it.
Hmmm -- we only have 7960s in our labs but they should be similar and they
work. You need to set up registrar, user name and credentials to be able
to register.
>If I call test(a)199.254.167.202 the phone rings and the call can be completed.
>If I call test(a)fitawi.com, I get an immediate call rejected. Since the
>phone does not show up as online in MSN messanger, I suspect that the lack
>of presence is the problem. Any thoughts?
These are two different things: ability to register and ability to
share current presence status. With 7960, you are able to register
so that people can reach you at your current address. 7960 has no
"presence disclosure" support -- if you want to see that the phone
is on-line in your messenger, you will have to use a presence agent
inbetween. We're working on it, but it is not currently part of SER.
The UsrLoc dump bellow shows a valid Test entry -- so the registration
must have proceeded well. If you are not able to call the user
test@yourdomain, the error will be probably somewhere else. Please
send me your configuration file and network dumps (gained using
e.g. ngrep utility) -- I'll be glad to review it.
-Jiri
> I will try the users list, and
>Cisco as a last resort.
>
>Thanks,
>Dan
>
>Here is my serctl ul show results:
>~~~Contact(0x402f0788)~~~
>domain : 'location'
>aor : 'Test'
>Contact: 'sip:Test@199.254.167.202:5060'
>Expires: 1983
>q : 0.00
>Call-ID: '000a8a93-d466000b-389ca1b7-74778f1a(a)199.254.167.202'
>CSeq : 101
>State : CS_SYNC
>next : (nil)
>prev : (nil)
