> Make sure you turn on debug logging on the sipXproxy and the sipXregistrar
> before reproducing the failing scenarios and taking the snapshot. Also,
> clearly take note of each steps involved in each scenario, i.e. who calls
> who and what the results are at each end.
Ok, so first, the remote u
Got the tests done. Where do I send this so that I'm not posting all sorts of
information I prefer not having on the net? :)
On Thu, 25 Mar 2010 17:51:52 -0400, JOLY, ROBERT (ROBERT) wrote:
>> The remote can call out. We tested by making a call to a cell phone.
>>
>> Using an internal to call t
.org
To: sipx-users
Sent: Thu Mar 25 17:33:01 2010
Subject: Re: [sipx-users] anonymous errors
The remote can call out. We tested by making a call to a cell phone.
Using an internal to call the remote leads to ringing, nothing else, not
even vm.
Using an external phone, cell phone, calling the rem
Sounds like a plan, will get on that later on then.
On Thu, 25 Mar 2010 17:51:52 -0400, JOLY, ROBERT (ROBERT) wrote:
>> The remote can call out. We tested by making a call to a cell phone.
>>
>> Using an internal to call the remote leads to ringing,
>> nothing else, not even vm.
>> Using an exter
> The remote can call out. We tested by making a call to a cell phone.
> Using an internal to call the remote leads to ringing,
> nothing else, not even vm.
> Using an external phone, cell phone, calling the remote,
> leads to a fast busy.
I think the next logical step is gathering a snapshot fo
The remote can call out. We tested by making a call to a cell phone.
Using an internal to call the remote leads to ringing, nothing else, not even
vm.
Using an external phone, cell phone, calling the remote, leads to a fast busy.
___
sipx-users mailing
> >?This is a 'normal error'. ?The sipXproxy will periodically
> (every 20
> >secs.)
>
> That's what we gathered but wanted to confirm, thanks.
>
> >?Stay away from Internet calling if you can avoid it. ?Please visit
>
> Ok, will do that.
> ?
> >?Check out "Problem #2" in link above and check
> This is a 'normal error'. The sipXproxy will periodically (every 20 secs.)
That's what we gathered but wanted to confirm, thanks.
> Stay away from Internet calling if you can avoid it. Please visit
Ok, will do that.
> Check out "Problem #2" in link above and check that the IP addresses tha
> When I take a phone and plug it into a wireless remote
> network connection, the following keeps showing up in sipXproxy.log.
>
> "2010-03-25T19:48:50.052314Z":3099:INCOMING:INFO:uc.domain.com
> :SipClientUdp-8:B78FCB90:SipXProxy:"Read SIP
> message:\nRemote Host:xxx.xxx.xxx.215 Port:
When I take a phone and plug it into a wireless remote network connection, the
following keeps showing up in sipXproxy.log.
"2010-03-25T19:48:50.052314Z":3099:INCOMING:INFO:uc.domain.com:SipClientUdp-8:B78FCB90:SipXProxy:"Read
SIP message:\nRemote Host:xxx.xxx.xxx.215 Port: 5060\nSIP
10 matches
Mail list logo
