[SIPForum-techwg] (Interop) SIPConnect Use cases for Basic Calls

[Peter Musgrave]

To focus my activity to specify use cases for basic voice interop in
SIPConnect I plan on listing some elementary use cases and seeing how
far down the path I can get before I hit cases where interop issues may
wreck. 

 

So far I'm thinking along the lines of:

 

1)     Basic call establishment

-        SP calls PBX, call is answered, voice path confirmed. 

-        PBX calls SP

2)     Call Hold

-        call on PBX places SP call on hold and recovers

3)     Call Failures

-        basic calls as above in which called party is busy, a invalid
number

-        call from SP to PBX where calls is not answered and goes to
voicemail

4)     Basic PBX Transfer

-        An established call is transferred from the initial PBX
endpoint to a new endpoint on the PBX - since REFER is not supported
this is a reINVITE to a new media port from the PBX to the SP ? With a
new private identity?

 

And trying to detail an "expected practice" (I'd use best practices but
I guess I'm not sure the simplest possible way to make calls will be
viewed as "best") which indicates the SP - PBX interactions which
result. 

 

I realize these seem pretty basic - but I can already see a number of
issues which will come up (some of which are probably answered in the
SIPconnect doc and which I hope this exercise will force me to ferret
out).  

 

-        TLS session establishment

-        Is a REGISTER required before a call attempt

-        Are INVITEs challenged?

-        Can a 302 be sent to a SP to redirect to voicemail (3261 says
SHOULD call Contact)

-        Etc. 

 

So if people think there is better way to approach this, please let me
know before I go too far down this road...

 

Cheers, 

 

Peter Musgrave

NewHeights Software

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20070424/2d79cda9/attachment.html