On Tue, Mar 29, 2011 at 9:45 PM, Matthew Kitchin (public/usenet)
wrote:
> The notes next to that setting indicate:
> "Set the From header to ITSP account information for outgoing INVITE
> messages. If you need to set this, ITSP is not following RFC and should be
> notified to this fact."
> I under
On 3/29/2011 8:30 PM, Douglas Hubler wrote:
> On Tue, Mar 29, 2011 at 9:05 PM, Matthew Kitchin (public/usenet)
> wrote:
>> Is it significant that it is showing different numbers? 4.2.1 is showing the
>> cell phone I'm calling in on. 4.4 is showing the DID alias for the extension
>> that is being
On Tue, Mar 29, 2011 at 9:05 PM, Matthew Kitchin (public/usenet)
wrote:
> Is it significant that it is showing different numbers? 4.2.1 is showing the
> cell phone I'm calling in on. 4.4 is showing the DID alias for the extension
> that is being forwarded.
> As for the ITSP setting, is that 4.4 on
Is it significant that it is showing different numbers? 4.2.1 is showing
the cell phone I'm calling in on. 4.4 is showing the DID alias for the
extension that is being forwarded.
As for the ITSP setting, is that 4.4 only? I don't see it in 4.2.1. I
will swap over and try it on the 4.4 machine if
Only difference I found was
WORKS (4.2.1)
=
From: "WIRELESS CALLER" ;tag=8452481748283643453
DOESN'T WORK (4.4)
From: "WIRELESS CALLER" ;tag=1035674599848618864
In ITSP Account advanced settings, do you have this set?
INVITE From ITSP Account: X
On Tue, Mar 29, 2011 at
On Tue, Mar 29, 2011 at 5:36 PM, Matthew Kitchin (public/usenet)
wrote:
> On 3/29/2011 4:11 PM, Michael Scheidell wrote:
>
> On 3/29/11 4:41 PM, Douglas Hubler wrote:
>
> Obvious answer is that there are no credentials, sipxecs is never
> challenged by verizon. In addition, sipxecs never challeng
On 3/29/2011 4:11 PM, Michael Scheidell wrote:
On 3/29/11 4:41 PM, Douglas Hubler wrote:
Obvious answer is that there are no credentials, sipxecs is never
challenged by verizon. In addition, sipxecs never challenges on the
original incoming INVITE either. The original SIP trace is suspect,
ca
On 3/29/11 4:41 PM, Douglas Hubler wrote:
Obvious answer is that there are no credentials, sipxecs is never
challenged by verizon. In addition, sipxecs never challenges on the
original incoming INVITE either. The original SIP trace is suspect,
can you (or anyone) think of any reason why "407 P
Putting this one back on list too.
I do not have a clue why something would be missing. If you are
referring to the merged logs, I can send the raw logs. They are small
and only contain data about the one call.
I will work on the capture for a 4.2.1 with working forward.
On 3/29/2011 3:41 PM, Do
On Tue, Mar 29, 2011 at 4:35 PM, Douglas Hubler wrote:
> On Tue, Mar 29, 2011 at 3:38 PM, Douglas Hubler wrote:
>> On Tue, Mar 29, 2011 at 3:16 PM, Matthew Kitchin (public/usenet)
>> wrote:
>>> Sure. Merged logs are attached. This is a call from 6159253938 (sipx 4.4
>>> test) to 6154670142 (sipx
On Tue, Mar 29, 2011 at 3:38 PM, Douglas Hubler wrote:
> On Tue, Mar 29, 2011 at 3:16 PM, Matthew Kitchin (public/usenet)
> wrote:
>> Sure. Merged logs are attached. This is a call from 6159253938 (sipx 4.4
>> test) to 6154670142 (sipx 4.2.1 production). The 2 systems are on seperate
>> Verizon s
On Tue, Mar 29, 2011 at 3:16 PM, Matthew Kitchin (public/usenet)
wrote:
> Sure. Merged logs are attached. This is a call from 6159253938 (sipx 4.4
> test) to 6154670142 (sipx 4.2.1 production). The 2 systems are on seperate
> Verizon sip trunks.
> Would you like to see a wireshark capture as well?
On Fri, Mar 25, 2011 at 11:30 AM, Matthew Kitchin (public/usenet) <
mkitchin.pub...@gmail.com> wrote:
> The wireshark shows it pretty clear to me, if I"m reading it correctly. It
> is attached, and I will attach it to the jira to.
> Call is from 6155008073 to 6159253938. It should forward to 61546
@list.sipfoundry.org>
>> *Cc: *Matthew Kitchin (public/usenet)
>> *Subject: *Re: [sipx-users] Sipx 4.4.0, failed external forward, Verizon
>> VoIP
>>
>> I am looking at this trace. I take it there is no "phone" involved on your
>> LAN. Can you explai
; *Date: *Sat, 26 Mar 2011 07:31:52 -0400
> *To: *Discussion list for users of sipXecs software<
> sipx-users@list.sipfoundry.org>
> *Cc: *Matthew Kitchin (public/usenet)
> *Subject: *Re: [sipx-users] Sipx 4.4.0, failed external forward, Verizon
> VoIP
>
> I am looking at this tr
: Sat, 26 Mar 2011 07:31:52
To: Discussion list for users of sipXecs
software
Cc: Matthew Kitchin (public/usenet)
Subject: Re: [sipx-users] Sipx 4.4.0, failed external forward, Verizon VoIP
I am looking at this trace. I take it there is no "phone" involved on your
LAN. Can you explain e
I am looking at this trace. I take it there is no "phone" involved on your
LAN. Can you explain exactly how the forwarding is configured in sipx? At
the same time or if no answer? and for how many seconds?
On Fri, Mar 25, 2011 at 12:27 PM, Matthew Kitchin (public/usenet) <
mkitchin.pub...@gmail.co
On 3/25/2011 11:23 AM, Michael Scheidell wrote:
On 3/25/11 12:19 PM, Matthew Kitchin (public/usenet) wrote:
The forward is immediate, because there isn't even a handset assigned
to that extension. It is set to forward for 30 seconds. 6154670142
never rings at all. The call drops after about 3 r
On 3/25/11 12:19 PM, Matthew Kitchin (public/usenet) wrote:
The forward is immediate, because there isn't even a handset assigned
to that extension. It is set to forward for 30 seconds. 6154670142
never rings at all. The call drops after about 3 rings heard on the
calling phone - 6155008073.
a
On 3/25/2011 10:42 AM, Michael Scheidell wrote:
On 3/25/11 11:30 AM, Matthew Kitchin (public/usenet) wrote:
On 3/25/2011 9:56 AM, Matthew Kitchin (public/usenet) wrote:
On 3/25/2011 8:17 AM, George Niculae wrote:
On Fri, Mar 25, 2011 at 2:44 AM, Matthew Kitchin (public/usenet)
mailto:mkitchi
On 3/25/11 11:30 AM, Matthew Kitchin (public/usenet) wrote:
On 3/25/2011 9:56 AM, Matthew Kitchin (public/usenet) wrote:
On 3/25/2011 8:17 AM, George Niculae wrote:
On Fri, Mar 25, 2011 at 2:44 AM, Matthew Kitchin (public/usenet)
mailto:mkitchin.pub...@gmail.com>> wrote:
I'm sending thi
On 3/25/2011 8:17 AM, George Niculae wrote:
On Fri, Mar 25, 2011 at 2:44 AM, Matthew Kitchin (public/usenet)
mailto:mkitchin.pub...@gmail.com>> wrote:
I'm sending this again with a zip'd logfile. I think it was too
big in my last email.
Could you please raise up a JIRA and attach th
pXecs software
Subject: Re: [sipx-users] Sipx 4.4.0, failed external forward, Verizon VoIP
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-
On 3/24/11 8:44 PM, Matthew Kitchin (public/usenet) wrote:
I'm sending this again with a zip'd logfile. I think it was too big in
my last email.
I did a merge-logs, and I assume that will contain all the correct
data since that is the only call in the logfile. The merged file is
attached. I can
On Fri, Mar 25, 2011 at 2:44 AM, Matthew Kitchin (public/usenet) <
mkitchin.pub...@gmail.com> wrote:
> I'm sending this again with a zip'd logfile. I think it was too big in my
> last email.
>
Could you please raise up a JIRA and attach this one and a snapshot?
Thanks,
George
__
look like it just dies here:
sipx does not like the reply/return code.
do you have wireshark on that box?
you should be able to do a 'yum install wireshark'
and then the cli version would be in /usr/sbin/tshark.
works similar to tcpdump, but wireshark actually decodes the sip sessions.
so,
sipx-users-boun...@list.sipfoundry.org
Date: Thu, 24 Mar 2011 15:54:54
To: Discussion list for users of sipXecs
software
Reply-To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Sipx 4.4.0, failed external forward, Verizon VoIP
___
On 3/24/11 2:43 PM, Matthew Kitchin (public/usenet) wrote:
I'm testing some functionality in 4.4 to see if I'm going to have any
issues in my environment.
I appear to have an issue when forwarding a call from an external
number to an external. This works in 4.2.1
The call just drops. I can forw
28 matches
Mail list logo
