DID again, it was working but not now, urgent help is needed

jaldulaimi · Last edited by jaldulaimi on Tue Apr 27, 2010 4:25 pm; edited 2 times in total

1. Brekeke Product Name and version:2.4.3.9

2. Java version: 4.1.31

3. OS type and the version: Fedora 8

4. UA (phone), gateway or other hardware/software involved: PAP2

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html : Pattern 4

6. Your problem: My DIDs were working but not now: Make call from a pstn--------->CiscoGW--------->SIP server-------->my sip phone. Cisco GW, been configured to use DID,. If I dial a DID, I get a message in my mobile or the carrier message saying the number not in use. According to my Cisco debug and my trace file on my sip server, I get this: SIP/2.0 404 Not Found

Here are my Cisco DP and BSS Dial Plan, can someone suggest what it could be wrong please, your help greatly appreciated.

They are both having public IP on the same LAN, my PAP2 is behind NAT, but the FW is not an issue, as I’m allowing everything between my LAN and where the Cisco and BSS are located.

Let's assume

Cisco IP is 215.8.164.44 and the BSS is 215.8.164.17

BSS

Matching Patterns

$request = ^INVITE
$addr = 215\.8\.164\.44
To = sip:82558100@

Deploy Patterns

$auth = off
To = sip:1777400018@

Cisco:

dial-peer voice 14010 pots
incoming called-number 82558100
direct-inward-dial
!
dial-peer voice 24010 voip
destination-pattern 88234010
session protocol sipv2
session target ipv4:215.8.165.17
dtmf-relay h245-signal h245-alphanumeric
!

hope · Brekeke Master Guru Joined: 15 Jan 2008 Posts: 862

if using wireshark capture packets at pc running brekeke sip server, can you see the INVITE to sip:82558100@... sent from Cisco gateway to bss?

jaldulaimi · Posted: Mon Apr 26, 2010 4:09 pm Post subject:

As you can see the answer is yes. Please not ths sip user ID is registered and I have no issue making sip to pstn calls.
1 0.000000 215.8.164.44 215.8.164.17 SIP/SDP Request: INVITE sip:82558100@215.8.164.17 :5060, with session description
2 0.000013 215.8.164.17 215.8.164.44 SIP Status: 100 Trying
3 0.006204 215.8.164.17 215.8.164.44 SIP Status: 404 Not Found

hope · Brekeke Master Guru Joined: 15 Jan 2008 Posts: 862

jaldulaimi · Posted: Tue Apr 27, 2010 4:07 pm Post subject:

Hi,

That's exactly how I've got my dial plan configured from the beginning and as I said it was working, the only thing I did I've upgraded to the latest BSS and changed the order of my dail plans, but the server is up and running and verything looks normal and again I have no problem making sip 2 pstn, only my DIDs no longer working.

hope · Brekeke Master Guru Joined: 15 Jan 2008 Posts: 862

jaldulaimi · Posted: Wed Apr 28, 2010 8:50 pm Post subject:

Hi Putting the dial plan at top does not make a difference.

According to this:

2 0.000013 215.8.164.17 215.8.164.44 SIP Status: 100 Trying
3 0.006204 215.8.164.17 215.8.164.44 SIP Status: 404 Not Found

The sip server saying, it does not find the correct sip user ID, correct? If correct why it does not find it? If you update BSS, does Tomcat and Java need an update as well, it's weird problem?

hope · Brekeke Master Guru Joined: 15 Jan 2008 Posts: 862

jaldulaimi · Posted: Thu Apr 29, 2010 3:19 pm Post subject:

Yes I did, many times and even restarted the BSS. It's all ok, remember it WAS WORKING, so all the setup is correct, all I'm asking does the update do funny things?

hope · Brekeke Master Guru Joined: 15 Jan 2008 Posts: 862

i donot think it is related to update but what you did after updating. if you donot tell us more about problem but only it was working before, How can we help you?
Maybe you'd better ask help directly from Brekeke support.

jaldulaimi · Posted: Sun May 02, 2010 9:12 pm Post subject:

Man, I'm not sure what you're talking about? I explained to you what I did, you either know the answer to the problem or you do not. Just to let you know put a complete new sip server Fedora 11 with latest BBS plus os update, still get the same thing, the usaull 404 not found. It could be the GW itself not sure though. It's killing me.