[Spce-user] Rings once, then disconnects!

[William Hilsum]

Hi

This is now solved... The moment I unticked "allow video" on the softphone, it worked as expected. 

These additional lines in the "invite (SDP) packet" from Sipwise to the carrier platform break the connection:

m=video 32562 RTP/AVP 34
c=IN IP4 <PBX-IP>
a=rtpmap:34 H263/90000
a=fmtp:34 QCIF=1;CIF=1;SQCIF=1;CIF4=1
a=sendrecv
a=rtcp:32563
a=direction:both

so...

1. Is there anyway to disable voice/these headers being sent on a per carrier basis? 
2. Is this a case of the carrier not following spec? (should it be ignored if they don't support video?)
3. is it just a broken softphone? (if it is, this is the first problem I've had with it)
 Or something else?!

I still don't get how one single ring goes out! I can't say I am an expert at all on this, but, this is certainly a new one for me!

Thanks for your help Andreas and Alex.

William

-----Original Message-----
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andreas Granig
Sent: 01 February 2016 16:33
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Rings once, then disconnects!

Hi William,

Maybe your peering partner doesn't like the SDP body (specifically the list of codecs) or something.

Try to limit the list of codecs on your 3CX to G711 as a start. Maybe also the SIP message (the 500 from your carrier) contains a header providing more details. From a SIP signaling perspective, there is a B2BUA in the SPCE, so the outbound message should be *somewhat* equal all the time no matter what client you're using, but then again the SDP is passed through more or less as-is, which could be a starting point for trouble-shooting.

Anyways, your carrier should be able to explain the reason why they're sending a 500 reply.

Andreas

On 02/01/2016 12:37 PM, William Hilsum wrote:
> Hi,
> 
> I've been working on this overnight and made a bit more progress... and, it is a weird one!
> 
> I saw the Sipwise Ios App and I thought I would give it a go...
> 
> I made calls fine without issue!
> 
> It looks like the issue is then related to the softphone (I was using 3CX) doing something dodgy and/or Sipwise not removing/changing the headers.
> 
> I'm really unsure how to proceed here, but, I am guessing I just have a lot of trial and error ahead of me.
> 
> William
> 
> -----Original Message-----
> From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf 
> Of Alex Lutay
> Sent: 01 February 2016 10:28
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Rings once, then disconnects!
> 
> Dear William,
> 
> As I can see on picture SPCE received "500 - Server Internal Error"
> from your Carrier, so there is nothing we can tell you here.
> 
> Please ask your Carrier about the reason of internal server error here.
> 
> On 02/01/2016 03:08 AM, William Hilsum wrote:
> [...skipped...]
>> I've tried to do diagnostics - I selected both legs of the call and 
>> made a quick picture: http://i.imgur.com/PzJF0Y5.jpg
> [...skipped...]
>> Feb  1 02:55:45 masterpbx1 (local7.notice) proxy[3350]: NOTICE:
>> <script>: NAT-Reply - S=500 - Server Internal Error M=INVITE
>> IP=**MY-HOME-IP**:56805 (127.0.0.1:5080) 
>> ID=ZTdlYmYwY2I2MmExZThkYmY1MTIxZGJmOGQyOWQ4ZmM. UA='<null>'
> [...skipped...]
> 
> --
> Alex Lutay
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user