More SIP issues, audio OK, but no incoming ring

[rpavlinich]

Ok so this is the same customer I've been having issues with for a while. They had SIP trunks on a IPO 500 with R4.something, then I upgraded them to R9 to try to solve the issue, still nothing. So I swapped their system out with a demo kit V2 with R8.1 and everything seemed fine for an hour.

Now incoming calls are not being handled correctly. The IPO sees the calls INVITE but never responds. This is the second system that's done this here. I thought it may have been the firewall/router, but I don't think the IPO would even see an INVITE if that was the case. Here's a short trace:

4215119mS SIP Rx: UDP 66.23.129.253:5060 -> 192.168.1.125:5060
INVITE sip:17603222653@71.189.196.59 SIP/2.0
Record-Route: <sip:+17603222653@66.23.129.253:5060;nat=yes;ftag=gK023fb4ad;lr=on>
Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bKb9c1.851990f3.0
Via: SIP/2.0/UDP 66.23.190.10:5060;branch=z9hG4bKb9c1.740b3193.0
Via: SIP/2.0/UDP 4.55.42.35:5060;branch=z9hG4bK02B0d9e24d04d3a39af
From: "WIRELESS CALLER" <sip:+19095833531@4.55.42.35:5060>;tag=gK023fb4ad
To: <sip:+17603222653@66.23.190.10:5060>
Call-ID: 335735007_119586035@4.55.42.35
CSeq: 26341 INVITE
Max-Forwards: 15
Allow: INVITE,ACK,CANCEL,BYE,REFER,SUBSCRIBE,PRACK,UPDATE
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "WIRELESS CALLER" <sip:+19095833531@4.55.42.35:5060>
P-Asserted-Identity: "WIRELESS CALLER" <sip:+19095833531@4.55.42.35:5060>
Supported: 100rel
Content-Length: 301
Content-Disposition: session; handling=required
Content-Type: application/sdp

v=0
o=Sonus_UAC 4917 26707 IN IP4 4.55.42.35
s=SIP Media Capabilities
c=IN IP4 4.55.42.6
t=0 0
m=audio 22662 RTP/AVP 0 8 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=maxptime:20
4215699mS SIP Rx: UDP 66.23.129.253:5060 -> 192.168.1.125:5060
INVITE sip:17603222653@71.189.196.59 SIP/2.0
Record-Route: <sip:+17603222653@66.23.129.253:5060;nat=yes;ftag=gK023fb4ad;lr=on>
Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bKb9c1.851990f3.0
Via: SIP/2.0/UDP 66.23.190.10:5060;branch=z9hG4bKb9c1.740b3193.0
Via: SIP/2.0/UDP 4.55.42.35:5060;branch=z9hG4bK02B0d9e24d04d3a39af
From: "WIRELESS CALLER" <sip:+19095833531@4.55.42.35:5060>;tag=gK023fb4ad
To: <sip:+17603222653@66.23.190.10:5060>
Call-ID: 335735007_119586035@4.55.42.35
CSeq: 26341 INVITE
Max-Forwards: 15
Allow: INVITE,ACK,CANCEL,BYE,REFER,SUBSCRIBE,PRACK,UPDATE
Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed
Contact: "WIRELESS CALLER" <sip:+19095833531@4.55.42.35:5060>
P-Asserted-Identity: "WIRELESS CALLER" <sip:+19095833531@4.55.42.35:5060>
Supported: 100rel
Content-Length: 301
Content-Disposition: session; handling=required
Content-Type: application/sdp

v=0
o=Sonus_UAC 4917 26707 IN IP4 4.55.42.35
s=SIP Media Capabilities
c=IN IP4 4.55.42.6
t=0 0
m=audio 22662 RTP/AVP 0 8 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=maxptime:20
4236638mS RES: Thu 17/4/2014 11:08:49 FreeMem=60679700(1) CMMsg=5 (5) Buff=5200 958 1000 7479 5 Links=6746 CPU=1/2/13588/29557/142933/0

 

[amriddle01]

It's unlikely that 2 systems on 3 different releases all just so happen to develop the same issue at the same location when 1 of them works fine elsewhere, and this location has given other issue in the past, the issue has to be linked to the location or provider in some way, so the network/network equipment or the provider is having issues/is rubbish...finding which is the hard part but it isn't the system hardware/software I'd wager