[Spce-user] Directly Fowarding Calls in sipwise

Martin Stix ms at pluteus.at
Tue Oct 28 16:24:12 EDT 2014

Hi Andrew!

Last question: Is there a way to disable Comedia in that case because of no NAT in place? Disable it for peerings?


mit freundlichen Grüßen
best regards
Martin Stix
pluteus communication solutions
ms at pluteus.at
Dampfsägestraße 17
3300 Amstetten
tel.: +43 7472 28165 20
fax.: +43 7472 28165 22

-----Ursprüngliche Nachricht-----
Von: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com] 
Gesendet: Dienstag, 28. Oktober 2014 13:57
An: Martin Stix; spce-user at lists.sipwise.com
Betreff: Re: AW: [Spce-user] Directly Fowarding Calls in sipwise

Hi Martin,

OK, I see. The Sipwise platform does not generate any SDP on calls or call forwarding, it does that only if you make a call to a conference or voicebox service which is answered by sipwise spce.

The SDP comes from the callee - the Sonus_UAC with first IP octet 185.
Actually it sends the SDP in the 183 which I overlooked before but does not send any in 200 OK. Weird. Anyway, that's callee (Sonus) that sends the a=direction:passive attribute. I think you should check with them..

Hope this helps.

On 10/28/2014 01:45 PM, Martin Stix wrote:
> Hi Andrew!
> The question is, why there's no sdp in it.
> Only sipwise is acting here, no client subscriber etc.
> The direction attribute says that in this particularly case sipwise is going to establish the stream.
> So again: Is there a way to disable Comedia, or do a re-invite?
> In normal call forwarding situation (peering to sipwise to customer to sipwise to another peering) there is no direction attribute coming vom ngcp and you see an SDP immediately.
> Thanks

More information about the Spce-user mailing list