On Tue, Dec 1, 2009 at 1:19 PM, mkitchin.pub...@gmail.com
wrote:
> Woohoo! I'm making calls! I toggled one option 'Use public address for
> call setup' and things are working now. I still need to work on figuring
> out how to change the codec, but it is progress.
sipxbridge ( and indeed all of si
Woohoo! I'm making calls! I toggled one option 'Use public address for
call setup' and things are working now. I still need to work on figuring
out how to change the codec, but it is progress.
mkitchin.pub...@gmail.com wrote:
> Sorry for the multiple emails. The Verizon tech just added this info
Scott Lawrence wrote:
> On Mon, 2009-11-23 at 09:25 -0600, mkitchin.pub...@gmail.com wrote:
>
>> I cleared my sipxbridge.log and tried some test calls. I'm still at home
>> on X -Lite (taking care of sick kids, but I will be in the office with
>> Cisco and Polycom phones on a few hours).
>> I
needed to include that info
on either of the hostname fields.
--Original Message--
From: Scott Lawrence
To: mkitchin.pub...@gmail.com
Cc: sipx-users@list.sipfoundry.org
Cc: Melting Pot Technologies GMail
Subject: Re: [sipx-users] Connecting to Verizon DS3
Sent: Nov 23, 2009 10:38 AM
On Mon,
On Mon, 2009-11-23 at 09:25 -0600, mkitchin.pub...@gmail.com wrote:
> I cleared my sipxbridge.log and tried some test calls. I'm still at home
> on X -Lite (taking care of sick kids, but I will be in the office with
> Cisco and Polycom phones on a few hours).
> I believe I have set sipx to pass 1
I cleared my sipxbridge.log and tried some test calls. I'm still at home
on X -Lite (taking care of sick kids, but I will be in the office with
Cisco and Polycom phones on a few hours).
I believe I have set sipx to pass 10 numbers to Verizon.
I tried local and long distance. In the attached log,
I read your guide, and I don't see anything that sticks out at me that
I'm doing wrong. Verizon says they are sending 10 and expecting 10
digits. I have enabled and tweaked the default dialing plans. I'm using
Cisco 7940s, because I had a few laying around. I am home now, so I just
tried Xlite
I did enable the dial plan, but I definitely need to go through his
document and see if I did something wrong.
Melting Pot Technologies GMail wrote:
> I would check your dial plans here like Tony said. It looks like the
> server is telling itself the call is denied. Did you enable the dial
>
But there is a simpler way to do the dial plan first. Ask Verizon what
format your numbers should be. I would assume they would accept the full
"+12025551212" (all +1 dialing). If so, the guide I have for
bandwidth.comhas all the rules laid out. It should work the same, only
the gateway name
would
Yes. 10.87.20.5 is me. I assumed that is what that meant. I will discuss
with them on Monday.
Tony Graziano wrote:
> I see two things that make me go hmmm
>
> "2009-11-20T23:11:36.845000Z":
> 19:OUTGOING:INFO:nshpbx1.sipx.voip:Thread-17::sipXbridge:"Sent
> SIP Message :\nRemote Ho
I see two things that make me go hmmm
"2009-11-20T23:11:36.845000Z":
19:OUTGOING:INFO:nshpbx1.sipx.voip:Thread-17::sipXbridge:"Sent
SIP Message :\nRemote Host:10.87.20.5 Port: 38526\nSIP/2.0
403 Forbidden\r\nVia: SIP/2.0/TCP
10.87.20.5;branch=z9hG4bK-sipXecs-0016a7a00a17b94
I would check your dial plans here like Tony said. It looks like the
server is telling itself the call is denied. Did you enable the dial
plan? You can see the different local components communicating in the
logs.
On Nov 20, 2009, at 6:17 PM, "mkitchin.pub...@gmail.com"
wrote:
> Not su
Not sure if there was a delay of some sort, but I got lots of activity
now. It is below. I will dig through them and see what I can find. They
announced the routing update (I'm not the network guy) and the equipment
did learn it. I can definitely ping their .1 address.
"2009-11-20T23:11:36.831
How are you/they learning the route to your/their network? Can you
ping their .1 address they gave you from the IPPBX?
On Nov 20, 2009, at 6:03 PM, "mkitchin.pub...@gmail.com"
wrote:
> It didn't put anything in a new log file. I've obviously got some
> work to do on my end.
> In a document
It didn't put anything in a new log file. I've obviously got some work
to do on my end.
In a document I gave them several weeks ago, I did provide them, the IP
of my server.
Melting Pot Technologies GMail wrote:
> Can you run:
>
> cd /var/log/sipxpbx
>
> rm -f ./sipxbridge.log
>
> Make a test ca
Can you run:
cd /var/log/sipxpbx
rm -f ./sipxbridge.log
Make a test call, and post the results from sipxbridge.log
If your a static configuration they are more than likely pointing to a
specific address on your end. Did they say anything about that?
On Nov 20, 2009, at 5:25 PM, "mkitchin.pu
---
From: sipx-users-boun...@list.sipfoundry.org
To: Melting Pot Technologies GMail ;
sipx-users@list.sipfoundry.org
Sent: Fri Nov 20 17:25:20 2009
Subject: Re: [sipx-users] Connecting to Verizon DS3
Yes. I just found that under advanced settings. that seems to have
gotten rid of that error. Than
Yes. I just found that under advanced settings. that seems to have
gotten rid of that error. Thank you! I still can't make any outbound
calls, but hopefully I will be able to find some more logs showing why.
The last entries in my sipxbridge log are below. My inbound calls from
Verizon are stil
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: sipx-users-boun...@list.sipfoundry.org
To: sipx-users@list.sipfoundry.org
Sent: Fri Nov 20 16:24:16 2009
Subject: Re: [sipx-users] Connecting to Verizon DS3
In case you didn't have enough e
Did you uncheck register on initialization?
On Nov 20, 2009, at 4:24 PM, "mkitchin.pub...@gmail.com"
wrote:
> In case you didn't have enough emails from me, here is a little more
> info. I put in 123 for the username, so that is obviously where the
> 'sip:1...@pcelbcn0001' entry is coming from.
In case you didn't have enough emails from me, here is a little more
info. I put in 123 for the username, so that is obviously where the
'sip:1...@pcelbcn0001' entry is coming from. The service errors out if I
don't put in a username and password, but Verizon isn't requesting we
use one.
mkitc
On Fri, 2009-11-20 at 16:06 -0500, Tony Graziano wrote:
> Two things: if you plan on having remote workers you ought to try to keep
> 5060 for them. Verizon should be able to send to you on 5080.
>
> I think you need to consider how you route from your 10.x network to your
> 172.x provider. Do you
al Message -
> From: mkitchin.pub...@gmail.com
> To: Robert Joly ; sipx-users@list.sipfoundry.org
>
> Cc: Tony Graziano
> Sent: Fri Nov 20 15:54:29 2009
> Subject: Re: [sipx-users] Connecting to Verizon DS3
>
> Oh yeah, I'm running 4.0.4
>
> mkitchin.pub...@gmail.co
Subject: Re: [sipx-users] Connecting to Verizon DS3
Oh yeah, I'm running 4.0.4
mkitchin.pub...@gmail.com wrote:
> Robert Joly wrote:
>>> That's weird. The ip they gave you to use is on the same subnet sipx
>>> is on?
>>>
>>> If so, sipxbridge is not n
Oh yeah, I'm running 4.0.4
mkitchin.pub...@gmail.com wrote:
> Robert Joly wrote:
>>> That's weird. The ip they gave you to use is on the same subnet sipx
>>> is on?
>>>
>>> If so, sipxbridge is not needed. Creating an unmanaged gateway would
>>> be simpler.
>>>
>>
>> That is true only if Ve
Robert Joly wrote:
>> That's weird. The ip they gave you to use is on the same
>> subnet sipx is on?
>>
>> If so, sipxbridge is not needed. Creating an unmanaged
>> gateway would be simpler.
>>
>
> That is true only if Verizon is capable of handling things like REFERs.
> If that is not the c
t; To: sipx-users@list.sipfoundry.org
> Sent: Fri Nov 20 15:16:00 2009
> Subject: Re: [sipx-users] Connecting to Verizon DS3
>
> Here are some log file entries that appear relevant to me:
>
> "2009-11-20T20:08:02.577000Z":5:OUTGOING:INFO:nshpbx1.sipx.voip:main:
gt; Telephone: 434.984.8426
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> - Original Message -
> From: sipx-users-boun...@list.sipfoundry.org
>
> To: sipx-users@list.sipfoundry.org
> Sent: Fri Nov 20 15:1
2009
Subject: Re: [sipx-users] Connecting to Verizon DS3
Here are some log file entries that appear relevant to me:
"2009-11-20T20:08:02.577000Z":5:OUTGOING:INFO:nshpbx1.sipx.voip:main::sipXbridge:"Sent
SIP Message :\nRemote Host:172.30.209.62 Port:
5070\nREGI
Here are some log file entries that appear relevant to me:
"2009-11-20T20:08:02.577000Z":5:OUTGOING:INFO:nshpbx1.sipx.voip:main::sipXbridge:"Sent
SIP Message :\nRemote Host:172.30.209.62 Port:
5070\nREGISTER sip:pcelbcn0001.munged.munged.com:5070
SIP/2.0\r\nCall-ID: 8d16619
This was an inevitable question from me. I need some help connecting to
Verizon SIP over a private DS3. There is no firewall or NAT involved.
The information they gave me is below.
From Verizon:
Inbound calls will route from the 172.30.9.0/24 port 5060 network and
you should be able to ping 17
31 matches
Mail list logo
