[Freeswitch-users] Aastra SCA Woes, Any Updates?

[Brian West]

The issue is the absence of the extra bits in the call-info header on every packet involved in the call transaction... but its worse than that if you want SCA you can only have ONE account on the phone and HOPE and pray it behaves.  I have tried to get Aastra to fix it but as far as I'm concerned your best bet is to call Polycom and trade all those Aastra's for Polycom's they have a trade up program and all you have to do is take a baseball bat and make the Aastra's inoperable or not they seems to have the inoperable part covered already right out of the box.  

/b

On Jun 17, 2010, at 12:32 PM, Wes Pearce wrote:

> 
> Hello Users,
> 
> I've got a dozen or so Aastra 6757i phones hooked up to FreeSWITCH in the
> office here. I've been trying to get SCA working unsuccessfully. While I was
> digging around, I found this thread:
> 
> http://freeswitch-users.2379917.n2.nabble.com/Aastra-and-SCA-td4995252.html
> 
> Which describes my exact problem. SCA works neatly on outbound calls, and
> SCA works on incoming calls until the phone is answered... at which point
> the call dissapears from the other lines.
> 
> Brian West mentioned this has something to do with Aastras inconsistent
> call-info headers.
> 
> I've been speaking with a support representative from Aastra named Brian
> Epps, who says their engineers are unaware of any SCA problems.
> 
> Here are the appropriate SIP traces:
> 
> incoming call: http://pastebin.com/QK9K3KL9
> outgoing call: http://pastebin.com/zzxbm9mq
> 
> There are call info headers in both traces. It's just the call-info headers
> in the incoming trace look incorrect.
> 
> I'm wondering if there has been any movement on this, or if I've just
> screwed something up somewhere.
> -- 
> View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Aastra-SCA-Woes-Any-Updates-tp5191927p5191927.html
> Sent from the freeswitch-users mailing list archive at Nabble.com.