then the 192.168.175.x network should NOT be in your intranet subnets
and you need to ensure DNS and firewall NAT is setup properly.

if it is not registering, I suggest you get a pcap at your firewall to
see what it is/is not doing.

2012/4/4 Simon Brûlé <[email protected]>:
> It should be Nat since the router between the LAN of the company and my
> SipXecs server have his WAN link plug into the company LAN.
>
> 2012/4/4 Tony Graziano <[email protected]>
>>
>> I am having a hard time explaining the difference between NAT/firewall
>> and ROUTING to you.
>>
>> sipx is in 192.168.0.x network. "OTHER" user is in 192.168.175.x network.
>>
>> Does the link between the 192.168.175.x network provide NAT or is it
>> just another network segment plugged in and routed? There is a huge
>> difference here.
>>
>> If it is routed this means the remote user comes from their IP address
>> 192.168.175.20 instead of the interface address of the nat as
>> 192.168.0.(whatever the router is).
>>
>> Which is it?
>>
>>
>>
>> 2012/4/4 Simon Brûlé <[email protected]>:
>> > Yes the nat traversal and remote users is enabled but like I said in my
>> > last
>> > post i dont think it's a remote user since it's in the same network but
>> > different subnet. He is in the 192.168.175.XXX /24 subnet and my SipXecs
>> > server is in the 192.168.0.XXX/24 subnet behind a router that we put
>> > there
>> > for testing purpose.
>> >
>> > There is the WAN that come in the router of the company then this router
>> > give the adresse 192.168.175.XXX to the LAN. I pluged a router in the
>> > lan to
>> > get one of those adresse so i have the 192.168.175.22 and this router
>> > don't
>> > give DHCp, I just use it to plug my SipXEcs server, my computer and 2
>> > hardphone on it for a testing environment.
>> >
>> > So the user that want to communicate with the others is in the LAN of
>> > the
>> > company and not in my Private LAN.
>> >
>> > 2012/4/4 Tony Graziano <[email protected]>
>> >>
>> >> Sorry, still having trouble following you. The picture below does not
>> >> show
>> >> where the remote user is.
>> >>
>> >> If sipx is on 192.168.0.1 then the only intranet subnet that should be
>> >> listed is 192.168.0.0/24 (assuming the subnet mask is /24 or
>> >> 255.255.255.0).
>> >>
>> >> If the remote user is on a public Ip other then their subnet should not
>> >> be
>> >> listed.  You need to ensure your firewall is set to forward at least
>> >> port
>> >> 5060 (tcp/udp) and 30000-31000 (udp) to sipx for the wan address the
>> >> remote
>> >> user is using and ensure the dns records the remote user is accessing
>> >> also
>> >> indicate the wan ip address of your firewall. the nat type for the sipx
>> >> ip
>> >> should also be symettrical (either 1:1 NAT). It's important that the
>> >> firewall not randomize port requests to sipx if you are using the built
>> >> in
>> >> media relay function.
>> >>
>> >> One assumes you have nat traversal and remote users enabled on the
>> >> server
>> >> profile too.
>> >>
>> >>
>> >>
>> >> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>
>> >>> I am sorry if my question are not specific enough or I am not giving
>> >>> enough detail I am doing my best since English is my second language.
>> >>>
>> >>> My first post give what the network look like at the moment. It will
>> >>> not
>> >>> be like that on the real installation its only for testing purpose of
>> >>> SipXecs that it's looking that.
>> >>>
>> >>> WAN ---------------> Router -------------------->  LAN ------------->
>> >>> Router --------------------> SipXecs
>> >>> xxx.xxx.xxx.xxx   and    192.168.175.1    192.168.175.22   and
>> >>> 192.168.0.2       192.168.0.1
>> >>>
>> >>> The user that can only receive call and not make them is in the LAN
>> >>> with
>> >>> an IP 192.168.175.XXX.
>> >>>
>> >>> My server is in the DMZ so anything that come from any IP adresse to
>> >>> the
>> >>> 192.168.175.22 of the router is redirect to 192.168.0.1.
>> >>>
>> >>> I disabled the firewall of the router.
>> >>>
>> >>> Since it's in the same network but different subnet I guess it's not
>> >>> remote.
>> >>>
>> >>> When the user is using Ekiga for Windows on his Vm he can call in the
>> >>> network but cannot receive call, but when he's using X-Lite on his
>> >>> windows
>> >>> he can receive but he cannot call.
>> >>>
>> >>> 2012/4/4 Tony Graziano <[email protected]>
>> >>>>
>> >>>> You need to be better articulate, because people will have a hard
>> >>>> time
>> >>>> following you. I am now after this last post.
>> >>>>
>> >>>> IF the remote user passes through a firewall (NAT) then that user is
>> >>>> remote.
>> >>>> IF that user is directly routed over a private network or vpn and
>> >>>> doesn't pass through NAT (bridged OR routed) then that user is LOCAL
>> >>>> and
>> >>>> their subnet should be added to the intranet subnet list.
>> >>>>
>> >>>> From what you have provided, I have no idea if the user is remote or
>> >>>> not.
>> >>>>
>> >>>> For goodness sakes, there's a wiki for and you should consult that
>> >>>> first.
>> >>>>
>> >>>> http://wiki.sipfoundry.org/display/sipXecs/Remote+User+NAT+Traversal
>> >>>>
>> >>>> You next post should indicate whether the user is TRULY remote. If
>> >>>> not,
>> >>>> that you have added the subnet and ensured the user can get the
>> >>>> appropriate
>> >>>> DNS records with the proper results.
>> >>>>
>> >>>>
>> >>>> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>>>
>> >>>>> When im saying external user he is still in the company network he
>> >>>>> is
>> >>>>> just outside my subnet he is outside of my router that's what i
>> >>>>> meant.
>> >>>>>
>> >>>>>
>> >>>>> 2012/4/4 Tony Graziano <[email protected]>
>> >>>>>>
>> >>>>>> Ask your trunk provider what they don't like about the forwarded
>> >>>>>> call.
>> >>>>>> It;'s either they don't support hairpinned calls or the
>> >>>>>> configuration of
>> >>>>>> your trunk with them. Note the forward call has zero to do with the
>> >>>>>> subject
>> >>>>>> (remote register).
>> >>>>>>
>> >>>>>>
>> >>>>>> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>>>>>
>> >>>>>>> Ok thanks. For the problem of my external user why can I call him
>> >>>>>>> from one of the phone but he cant call anything, it always says
>> >>>>>>> call failed.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> 2012/4/4 Michael Picher <[email protected]>
>> >>>>>>>>
>> >>>>>>>> I think there's a pay-for version of Bria for Ubuntu...
>> >>>>>>>>
>> >>>>>>>> I'm not running one on my Ubuntu at the moment...  Just Windows
>> >>>>>>>> (Bria), Mac (Bria), iPad (Bria for iPad), Android (Bria &
>> >>>>>>>> CSipSimple).
>> >>>>>>>>
>> >>>>>>>> Mike
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On Wed, Apr 4, 2012 at 9:36 AM, Simon Brûlé
>> >>>>>>>> <[email protected]> wrote:
>> >>>>>>>>>
>> >>>>>>>>> THe computer outside of the subnet got a Windows VM too so he
>> >>>>>>>>> installed X-lite to test it and it's working too i can call him
>> >>>>>>>>> without any
>> >>>>>>>>> trouble but he cant call me.
>> >>>>>>>>>
>> >>>>>>>>> So as i can see it's a software problem but we have to use a
>> >>>>>>>>> linux
>> >>>>>>>>> softphone so any suggestion on something that could work??
>> >>>>>>>>>
>> >>>>>>>>> So far i tested Ekiga and SFLPhone and they didn't work where
>> >>>>>>>>> X-lite worked perfecly.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>>>>>>>>
>> >>>>>>>>>> I have a Windows VM on my Ubuntu install so i installed X-lite
>> >>>>>>>>>> on
>> >>>>>>>>>> it to try the domain name and its working with X-lite.
>> >>>>>>>>>>
>> >>>>>>>>>> The windows Client is able to connect to the SipXecs server and
>> >>>>>>>>>> he
>> >>>>>>>>>> is in the same subnet as my computer.
>> >>>>>>>>>>
>> >>>>>>>>>> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>
>> >>>>>>>>>>> That test is from the computer
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> In the resolv.conf of my computer i put the SipXecs server,
>> >>>>>>>>>>>> my
>> >>>>>>>>>>>> router and i put the line Search netappsid.local because he
>> >>>>>>>>>>>> wouldn't resolv
>> >>>>>>>>>>>> any dns with netappsid.local if i didn't gave him that line.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Without those line i only had the adresse of my router and
>> >>>>>>>>>>>> when
>> >>>>>>>>>>>> i tryed to do a nslookup of my sipXecs server
>> >>>>>>>>>>>> (voiptest.netappsid.local) it
>> >>>>>>>>>>>> gave me the external adresse of my router because the server
>> >>>>>>>>>>>> is in the DMZ.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 2012/4/4 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> I can't try X-lite because i am on a Ubuntu based system and
>> >>>>>>>>>>>>> on
>> >>>>>>>>>>>>> the main site i only see a Windows and Mac version.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> I used dig -t SRV _sip._udp.netappsid.local because my SIP
>> >>>>>>>>>>>>> domain is netappsid.local. Voiptest is the name i gave to
>> >>>>>>>>>>>>> the server.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Here is the output of dig -t SRV _sip._udp.netappsid.loca :
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ; <<>> DiG 9.7.3 <<>> -t SRV _sip._udp.netappsid.local
>> >>>>>>>>>>>>> ;; global options: +cmd
>> >>>>>>>>>>>>> ;; Got answer:
>> >>>>>>>>>>>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51491
>> >>>>>>>>>>>>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
>> >>>>>>>>>>>>> ADDITIONAL: 1
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ;; QUESTION SECTION:
>> >>>>>>>>>>>>> ;_sip._udp.netappsid.local. IN SRV
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ;; ANSWER SECTION:
>> >>>>>>>>>>>>> _sip._udp.netappsid.local. 1800 IN SRV 1 0 5060
>> >>>>>>>>>>>>> voiptest.netappsid.local.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ;; AUTHORITY SECTION:
>> >>>>>>>>>>>>> netappsid.local. 1800 IN NS voiptest.netappsid.local.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ;; ADDITIONAL SECTION:
>> >>>>>>>>>>>>> voiptest.netappsid.local. 1800 IN A 192.168.0.1
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ;; Query time: 2 msec
>> >>>>>>>>>>>>> ;; SERVER: 192.168.0.1#53(192.168.0.1)
>> >>>>>>>>>>>>> ;; WHEN: Wed Apr  4 08:49:09 2012
>> >>>>>>>>>>>>> ;; MSG SIZE  rcvd: 117
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> 2012/4/4 <[email protected]>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Hi Simon,
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Please try to test with X-Lite.
>> >>>>>>>>>>>>>> This one is known to work OK with SRV records.
>> >>>>>>>>>>>>>> I never got Ekiga working properly.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Anyhow your DNS does not seem to be OK.
>> >>>>>>>>>>>>>> Is your SIP domain voiptest.netappsid.local or
>> >>>>>>>>>>>>>> netappsid.local?
>> >>>>>>>>>>>>>> Please show the output of dig -t SRV
>> >>>>>>>>>>>>>> _sip._udp.{voiptest.netappsid.}local
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Paul
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Simon Brûlé <[email protected]> wrote on
>> >>>>>>>>>>>>>> 03-04-2012
>> >>>>>>>>>>>>>> 21:47:40:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > When I run Ekiga on the computer in the same subnet as
>> >>>>>>>>>>>>>> > the
>> >>>>>>>>>>>>>> > sipXecs
>> >>>>>>>>>>>>>> > server those are the error I got
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.899 10:11.423 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Starting REGISTER for offline retry
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.899 10:11.423 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Changing REGISTER handler from Unavailable to Restoring,
>> >>>>>>>>>>>>>> > target=sip:
>> >>>>>>>>>>>>>> > [email protected], id=be420c86-307c-
>> >>>>>>>>>>>>>> > e111-80f4-0024e8991e4c@simon-Vostro-1720
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.899 10:11.424 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > DNS
>> >>>>>>>>>>>>>> > SRV
>> >>>>>>>>>>>>>> > Lookup voiptest.netappsid.local service _sip._udp
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.426 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > No SRV
>> >>>>>>>>>>>>>> > record found.
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.426 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > OpalUDP
>> >>>>>>>>>>>>>> > Binding to interface: 0.0.0.0:5060
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > Socket Name
>> >>>>>>>>>>>>>> > lookup of "voiptest.netappsid.local" failed: errno=4
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > Opal Could
>> >>>>>>>>>>>>>> > not find host "voiptest.netappsid.local"
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Could
>> >>>>>>>>>>>>>> > not find udp$voiptest.netappsid.local:5060
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > Opal
>> >>>>>>>>>>>>>> > Transport clean up on termination
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > Opal Transport Close
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.902 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > Opal
>> >>>>>>>>>>>>>> > Deleted transport udp$*:5060<if=udp$*:5060>
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.903 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Changing REGISTER handler from Restoring to Unavailable,
>> >>>>>>>>>>>>>> > target=sip:
>> >>>>>>>>>>>>>> > [email protected], id=be420c86-307c-
>> >>>>>>>>>>>>>> > e111-80f4-0024e8991e4c@simon-Vostro-1720
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.903 10:11.427 Housekeeper:0xb3f02b70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Retrying REGISTER after 30 seconds.
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.917 10:11.442  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Start REGISTER
>> >>>>>>>>>>>>>> >           [email protected]
>> >>>>>>>>>>>>>> >        remote=voiptest.netappsid.local
>> >>>>>>>>>>>>>> >         local=
>> >>>>>>>>>>>>>> >       contact=
>> >>>>>>>>>>>>>> >        authID=3014
>> >>>>>>>>>>>>>> >         realm=
>> >>>>>>>>>>>>>> >        expire=3600
>> >>>>>>>>>>>>>> >       restore=30
>> >>>>>>>>>>>>>> >      minRetry=0.000
>> >>>>>>>>>>>>>> >      maxRetry=0.000
>> >>>>>>>>>>>>>> > compatibility=CannotRegisterMultipleContacts
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.918 10:11.443  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Expiry
>> >>>>>>>>>>>>>> > time for REGISTER set to 3600 seconds.
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.918 10:11.443  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Executing state change to Subscribing for REGISTER
>> >>>>>>>>>>>>>> > handler,
>> >>>>>>>>>>>>>> > target=sip:[email protected],
>> >>>>>>>>>>>>>> > id=be420c86-307c-
>> >>>>>>>>>>>>>> > e111-80f4-0024e8991e4c@simon-Vostro-1720
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.918 10:11.443  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Changing REGISTER handler from Unavailable to
>> >>>>>>>>>>>>>> > Subscribing,
>> >>>>>>>>>>>>>> > target=sip:[email protected],
>> >>>>>>>>>>>>>> > id=be420c86-307c-
>> >>>>>>>>>>>>>> > e111-80f4-0024e8991e4c@simon-Vostro-1720
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.443  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > DNS
>> >>>>>>>>>>>>>> > SRV
>> >>>>>>>>>>>>>> > Lookup voiptest.netappsid.local service _sip._udp
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.443  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > No SRV
>> >>>>>>>>>>>>>> > record found.
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.443  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > OpalUDP
>> >>>>>>>>>>>>>> > Binding to interface: 0.0.0.0:5060
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > Socket Name
>> >>>>>>>>>>>>>> > lookup of "voiptest.netappsid.local" failed: errno=4
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > Opal Could
>> >>>>>>>>>>>>>> > not find host "voiptest.netappsid.local"
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Could
>> >>>>>>>>>>>>>> > not find udp$voiptest.netappsid.local:5060
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > Opal
>> >>>>>>>>>>>>>> > Transport clean up on termination
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.919 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > Opal Transport Close
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.920 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > Opal
>> >>>>>>>>>>>>>> > Deleted transport udp$*:5060<if=udp$*:5060>
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.920 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Changing REGISTER handler from Subscribing to
>> >>>>>>>>>>>>>> > Unavailable,
>> >>>>>>>>>>>>>> > target=sip:[email protected],
>> >>>>>>>>>>>>>> > id=be420c86-307c-
>> >>>>>>>>>>>>>> > e111-80f4-0024e8991e4c@simon-Vostro-1720
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.920 10:11.444  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > SIP
>> >>>>>>>>>>>>>> > Retrying REGISTER after 30 seconds.
>> >>>>>>>>>>>>>> > 2012/04/03 15:27:39.920 10:11.445  subscriber:0xb10feb70
>> >>>>>>>>>>>>>> > PTLib
>> >>>>>>>>>>>>>> > Thread ended: name="subscriber:0xb10feb70", real=0.002,
>> >>>>>>>>>>>>>> > kernel=0.000
>> >>>>>>>>>>>>>> > (0%), user=0.000 (0%), both=0.000 (0%)
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > and those come over and over as Ekiga try to register
>> >>>>>>>>>>>>>> > again
>> >>>>>>>>>>>>>> > every 30secondes.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > The Domain name is netappsid.local
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > the alias the server have is :
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > voiptest.netappsid.local
>> >>>>>>>>>>>>>> > 192.168.0.1
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > with the IP no problem
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 2012/4/3 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>>> > Im at the same place with Ekiga that i was with SFLPhone,
>> >>>>>>>>>>>>>> > I
>> >>>>>>>>>>>>>> > can
>> >>>>>>>>>>>>>> > register with the IP adresse alias i created on the
>> >>>>>>>>>>>>>> > server
>> >>>>>>>>>>>>>> > but not
>> >>>>>>>>>>>>>> > with the domain name and the hostname.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > 2012/4/3 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>>> > At the moment I am trying with Ekiga and he is giving me
>> >>>>>>>>>>>>>> > an
>> >>>>>>>>>>>>>> > error
>> >>>>>>>>>>>>>> > even with the IP adresse alias that i tested with SFL and
>> >>>>>>>>>>>>>> > is
>> >>>>>>>>>>>>>> > working fine.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > 2012/4/3 Tony Graziano <[email protected]>
>> >>>>>>>>>>>>>> > then i think its a lack of support on the part of
>> >>>>>>>>>>>>>> > sflphone.
>> >>>>>>>>>>>>>> > have you
>> >>>>>>>>>>>>>> > talked to them as to whether they plan to support
>> >>>>>>>>>>>>>> > hostname
>> >>>>>>>>>>>>>> > or srv? I
>> >>>>>>>>>>>>>> > am not sure this is a sipx question or problem. sflphone
>> >>>>>>>>>>>>>> > is
>> >>>>>>>>>>>>>> > really
>> >>>>>>>>>>>>>> > geared towards * and likely hasn't matured to handle dns
>> >>>>>>>>>>>>>> > properly yet.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > 2012/4/3 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>>> > Right now the softphone (SFLPhone) that is in the same
>> >>>>>>>>>>>>>> > subnet can be
>> >>>>>>>>>>>>>> > registered by the IP alias that SipXecs have but cant
>> >>>>>>>>>>>>>> > register by
>> >>>>>>>>>>>>>> > hostname or domain name.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >  I can ping the hostname of the SipXecs server and i can
>> >>>>>>>>>>>>>> > resolve the
>> >>>>>>>>>>>>>> > SRV record i tried with this command dig -t SRV
>> >>>>>>>>>>>>>> > _sip._udp.example.com
>> >>>>>>>>>>>>>> > that i found on the Wiki and its working.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 2012/4/3 Tony Graziano <[email protected]>
>> >>>>>>>>>>>>>> > can you ping by hostname? how are the phones tryong to
>> >>>>>>>>>>>>>> > register? by
>> >>>>>>>>>>>>>> > ip, hostname or domain name?
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > if the user agent is sflphone, can it register by domain?
>> >>>>>>>>>>>>>> > do
>> >>>>>>>>>>>>>> > you
>> >>>>>>>>>>>>>> > have srv records populated that the host pc can resolve?
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > realize if you are trying to register by IP, you need to
>> >>>>>>>>>>>>>> > add
>> >>>>>>>>>>>>>> > the IP
>> >>>>>>>>>>>>>> > as a domain alias to sipxconifg. You stand to lose
>> >>>>>>>>>>>>>> > functionality by
>> >>>>>>>>>>>>>> > registering to a hostname or IP address.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > good luck.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > 2012/4/3 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>>> > RIght now i can ping my sipXecs server by its domain name
>> >>>>>>>>>>>>>> > from a
>> >>>>>>>>>>>>>> > computer on the same subnet and from one on a different
>> >>>>>>>>>>>>>> > subnet but
>> >>>>>>>>>>>>>> > they cant register with their softphone.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > With the one on the same subnet i get the error 502 Bad
>> >>>>>>>>>>>>>> > Gateway and
>> >>>>>>>>>>>>>> > from the one outside the subnet i get a Transfer Error
>> >>>>>>>>>>>>>> > and
>> >>>>>>>>>>>>>> > in the
>> >>>>>>>>>>>>>> > debug mode the error are No SRV Record and couldn't fin
>> >>>>>>>>>>>>>> > host.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 2012/4/3 Simon Brûlé <[email protected]>
>> >>>>>>>>>>>>>> > Thanks for the suggestion I am working on it at the
>> >>>>>>>>>>>>>> > moment.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > 2012/4/1 Michael Picher <[email protected]>
>> >>>>>>>>>>>>>> > sipXecs likes domain names...  if you want to play with
>> >>>>>>>>>>>>>> > IP
>> >>>>>>>>>>>>>> > addresses, I'd suggest not.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > see wiki for DNS suggestions, and start with a simple
>> >>>>>>>>>>>>>> > network first
>> >>>>>>>>>>>>>> > to learn the ropes.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > mike
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > On Fri, Mar 30, 2012 at 3:13 PM, Simon Brûlé
>> >>>>>>>>>>>>>> > <[email protected]
>> >>>>>>>>>>>>>> > > wrote:
>> >>>>>>>>>>>>>> > Hi
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > My network (for testing purpose) looks like this at the
>> >>>>>>>>>>>>>> > moment.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > WAN ---------------> Router -------------------->  LAN
>> >>>>>>>>>>>>>> > -------------> Router --------------------> SipXecs
>> >>>>>>>>>>>>>> > xxx.xxx.xxx.xxx   and    192.168.175.1    192.168.175.22
>> >>>>>>>>>>>>>> > and
>> >>>>>>>>>>>>>> > 192.168.0.2       192.168.0.1
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > Keep in mind this is only for testing purpose.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > I have 2 computer in the 192.168.175.xxx network with
>> >>>>>>>>>>>>>> > softphone and
>> >>>>>>>>>>>>>> > I am not able to register them to SipXecs.The Ip Adresse
>> >>>>>>>>>>>>>> > of
>> >>>>>>>>>>>>>> > the
>> >>>>>>>>>>>>>> > computer use for the test is 192.168.175.136.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > I did everything as they say in the wiki
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > http://wiki.sipfoundry.org/display/sipXecs/Remote+User+NAT+Traversal
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > I did the troubleshooting test for problem #1.The Number
>> >>>>>>>>>>>>>> > is
>> >>>>>>>>>>>>>> > different from 0 each time so my sipXecs receive
>> >>>>>>>>>>>>>> > everything
>> >>>>>>>>>>>>>> > but my
>> >>>>>>>>>>>>>> > SFLPhone and the ekiga of the other computer have the
>> >>>>>>>>>>>>>> > Error
>> >>>>>>>>>>>>>> > 483 "Too
>> >>>>>>>>>>>>>> > Many Hops".
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > The text file I created to put the result of the Tail of
>> >>>>>>>>>>>>>> > the
>> >>>>>>>>>>>>>> > sipXproxy file got 170 line in about 2-3sec when I try to
>> >>>>>>>>>>>>>> > log one of
>> >>>>>>>>>>>>>> > my softphone.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > The line are all the same. Here is an exemple of the
>> >>>>>>>>>>>>>> > incoming lines,
>> >>>>>>>>>>>>>> > the outgoing lines and the NAT lines I have in the file:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > "2012-03-30T17:30:14.399076Z":
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 104805:INCOMING:INFO:voiptest.netappsid.local:SipClientUdp-12:
>> >>>>>>>>>>>>>> > 4237A940:SipXProxy:"Read SIP message:\n----Local
>> >>>>>>>>>>>>>> > Host:192.168.0.
>> >>>>>>>>>>>>>> > 1---- Port: 5060----\n----Remote Host:192.168.175.22----
>> >>>>>>>>>>>>>> > Port:
>> >>>>>>>>>>>>>> > 5060----\nSIP/2.0 483 Too many hops\r\nFrom:
>> >>>>>>>>>>>>>> > <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo:
>> >>>>>>>>>>>>>> > > <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=N39HZK\r\nCall-Id:
>> >>>>>>>>>>>>>> > > bc3d355a-5161-4c83-b5f0-a59c471be90d\r
>> >>>>>>>>>>>>>> > \nCseq: 25984 REGISTER\r\nVia: SIP/2.0/UDP 192.168.0.1:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;branch=z9hG4bK-XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.
>> >>>>>>>>>>>>>> > 0.2;rport=5060\r\nVia: SIP/2.0/UDP
>> >>>>>>>>>>>>>> > 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.175.136:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c
>> >>>>>>>>>>>>>> > \r\nWarning: 399 192.168.0.1 \"Too many
>> >>>>>>>>>>>>>> > hops\"\r\nContent-Type:
>> >>>>>>>>>>>>>> > message/sipfrag\r\nServer: sipXecs/4.4.0
>> >>>>>>>>>>>>>> > sipXecs/sipXproxy
>> >>>>>>>>>>>>>> > (Linux)\r
>> >>>>>>>>>>>>>> > \nContent-Length: 3167\r\nDate: Fri, 30 Mar 2012 17:30:12
>> >>>>>>>>>>>>>> > GMT\r\n\r
>> >>>>>>>>>>>>>> > \nREGISTER sip:192.168.175.22 SIP/2.0\r\nRecord-Route:
>> >>>>>>>>>>>>>> > <sip:192.168.
>> >>>>>>>>>>>>>> > 0.1:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 7EMTlmNzZjMmMtOWEwYy00ZjI0LTlmMmMtYWZkODZkMDNlZjM1.900_ntap%2ACrT%
>> >>>>>>>>>>>>>> > 7EMTkyLjE2OC4wLjI6NDY5OTM7dHJhbnNwb3J0PXVkcA%60%60%
>> >>>>>>>>>>>>>> > 214a544449ed5ce5e50a94e999a899bdc5>\r\nVia: SIP/2.0/TCP
>> >>>>>>>>>>>>>> > 192.168.0.1:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;branch=z9hG4bK-XX-0832i5x33`VKc22zP3mkGNjmfQ;received=192.168.
>> >>>>>>>>>>>>>> > 0.2;rport=46993\r\nVia: SIP/2.0/TCP
>> >>>>>>>>>>>>>> > 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-082fq1WJ8M5x6b4tDeiljIBDTA;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-082csuOFUit3bmLpyKgObSVCXA;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0829VHLuUQt1lIHkHqgVbjqDKQ;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0826Cupn7TcFk7PeF35kpdFV`w;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08230CQtsnYLPfSwLvYOh80itg;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0820av2EdSD`IWoQzZaWUD6VNw;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-081dLyz7l7Q2j7wpiJyQvREDig;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-081aE4YsWuzNtylJsrrXDRPpJw;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08178PP4lMUYpgYq8P52Jn`2vg;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0814SHnrAwRgnajljOeOsxph6A;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0811JA_CvNGjag8HGBcpHMt7ag;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-080e3ERtfd7bk2Kvwpo0gBczhQ;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-080b4OdhNrpwOTslfNyvvMSq1Q;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08087iV`FPifr5gtrxb6pmgBVw;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0805ezBBZ9Rr5Uxix_`iaS6i0A;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08021pc96y1seSQwJcQrD8WMwQ;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07ffx`4TeZoMqeci8hGz9zRAQw;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07fcJ8HxRMec4Qr2kgAJ`ZQj5w;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.175.136:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c
>> >>>>>>>>>>>>>> > \r\nMax-Forwards: 0\r\nFrom: <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo:
>> >>>>>>>>>>>>>> > > <sip:[email protected]
>> >>>>>>>>>>>>>> > >\r\nCall-Id:
>> >>>>>>>>>>>>>> > > bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq:
>> >>>>>>>>>>>>>> > > 25984
>> >>>>>>>>>>>>>> > REGISTER\r\nUser-Agent: SFLphone\r\nContact:
>> >>>>>>>>>>>>>> > <sip:[email protected]:5060
>> >>>>>>>>>>>>>> > >\r\nExpires: 600\r\nAllow: PRACK, SUBSCRIBE, NOTIFY,
>> >>>>>>>>>>>>>> > > REFER,
>> >>>>>>>>>>>>>> > > INVITE,
>> >>>>>>>>>>>>>> > ACK, BYE, CANCEL, UPDATE, INFO, REGISTER, OPTIONS,
>> >>>>>>>>>>>>>> > MESSAGE\r
>> >>>>>>>>>>>>>> > \nContent-Length: 0\r\nDate: Fri, 30 Mar 2012 17:30:10
>> >>>>>>>>>>>>>> > GMT\r\n\r
>> >>>>>>>>>>>>>> > \n====================END===================="
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > "2012-03-30T17:30:14.399076Z":
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 104805:INCOMING:INFO:voiptest.netappsid.local:SipClientUdp-12:
>> >>>>>>>>>>>>>> > 4237A940:SipXProxy:"Read SIP message:\n----Local
>> >>>>>>>>>>>>>> > Host:192.168.0.
>> >>>>>>>>>>>>>> > 1---- Port: 5060----\n----Remote Host:192.168.175.22----
>> >>>>>>>>>>>>>> > Port:
>> >>>>>>>>>>>>>> > 5060----\nSIP/2.0 483 Too many hops\r\nFrom:
>> >>>>>>>>>>>>>> > <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo:
>> >>>>>>>>>>>>>> > > <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=N39HZK\r\nCall-Id:
>> >>>>>>>>>>>>>> > > bc3d355a-5161-4c83-b5f0-a59c471be90d\r
>> >>>>>>>>>>>>>> > \nCseq: 25984 REGISTER\r\nVia: SIP/2.0/UDP 192.168.0.1:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;branch=z9hG4bK-XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.
>> >>>>>>>>>>>>>> > 0.2;rport=5060\r\nVia: SIP/2.0/UDP
>> >>>>>>>>>>>>>> > 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.175.136:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c
>> >>>>>>>>>>>>>> > \r\nWarning: 399 192.168.0.1 \"Too many
>> >>>>>>>>>>>>>> > hops\"\r\nContent-Type:
>> >>>>>>>>>>>>>> > message/sipfrag\r\nServer: sipXecs/4.4.0
>> >>>>>>>>>>>>>> > sipXecs/sipXproxy
>> >>>>>>>>>>>>>> > (Linux)\r
>> >>>>>>>>>>>>>> > \nContent-Length: 3167\r\nDate: Fri, 30 Mar 2012 17:30:12
>> >>>>>>>>>>>>>> > GMT\r\n\r
>> >>>>>>>>>>>>>> > \nREGISTER sip:192.168.175.22 SIP/2.0\r\nRecord-Route:
>> >>>>>>>>>>>>>> > <sip:192.168.
>> >>>>>>>>>>>>>> > 0.1:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 7EMTlmNzZjMmMtOWEwYy00ZjI0LTlmMmMtYWZkODZkMDNlZjM1.900_ntap%2ACrT%
>> >>>>>>>>>>>>>> > 7EMTkyLjE2OC4wLjI6NDY5OTM7dHJhbnNwb3J0PXVkcA%60%60%
>> >>>>>>>>>>>>>> > 214a544449ed5ce5e50a94e999a899bdc5>\r\nVia: SIP/2.0/TCP
>> >>>>>>>>>>>>>> > 192.168.0.1:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;branch=z9hG4bK-XX-0832i5x33`VKc22zP3mkGNjmfQ;received=192.168.
>> >>>>>>>>>>>>>> > 0.2;rport=46993\r\nVia: SIP/2.0/TCP
>> >>>>>>>>>>>>>> > 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-082fq1WJ8M5x6b4tDeiljIBDTA;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-082csuOFUit3bmLpyKgObSVCXA;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0829VHLuUQt1lIHkHqgVbjqDKQ;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0826Cupn7TcFk7PeF35kpdFV`w;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08230CQtsnYLPfSwLvYOh80itg;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0820av2EdSD`IWoQzZaWUD6VNw;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-081dLyz7l7Q2j7wpiJyQvREDig;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-081aE4YsWuzNtylJsrrXDRPpJw;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08178PP4lMUYpgYq8P52Jn`2vg;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0814SHnrAwRgnajljOeOsxph6A;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0811JA_CvNGjag8HGBcpHMt7ag;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-080e3ERtfd7bk2Kvwpo0gBczhQ;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-080b4OdhNrpwOTslfNyvvMSq1Q;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08087iV`FPifr5gtrxb6pmgBVw;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-0805ezBBZ9Rr5Uxix_`iaS6i0A;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/TCP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-08021pc96y1seSQwJcQrD8WMwQ;received=192.168.0.2;rport=46993\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07ffx`4TeZoMqeci8hGz9zRAQw;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07fcJ8HxRMec4Qr2kgAJ`ZQj5w;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07f9Y5qFu6pl6TjooSuxLgqdow;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK-
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > XX-07f6AirluMWLBMyodL4I7TqoSg;received=192.168.0.2;rport=5060\r
>> >>>>>>>>>>>>>> > \nVia: SIP/2.0/UDP 192.168.175.136:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c
>> >>>>>>>>>>>>>> > \r\nMax-Forwards: 0\r\nFrom: <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo:
>> >>>>>>>>>>>>>> > > <sip:[email protected]
>> >>>>>>>>>>>>>> > >\r\nCall-Id:
>> >>>>>>>>>>>>>> > > bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq:
>> >>>>>>>>>>>>>> > > 25984
>> >>>>>>>>>>>>>> > REGISTER\r\nUser-Agent: SFLphone\r\nContact:
>> >>>>>>>>>>>>>> > <sip:[email protected]:5060
>> >>>>>>>>>>>>>> > >\r\nExpires: 600\r\nAllow: PRACK, SUBSCRIBE, NOTIFY,
>> >>>>>>>>>>>>>> > > REFER,
>> >>>>>>>>>>>>>> > > INVITE,
>> >>>>>>>>>>>>>> > ACK, BYE, CANCEL, UPDATE, INFO, REGISTER, OPTIONS,
>> >>>>>>>>>>>>>> > MESSAGE\r
>> >>>>>>>>>>>>>> > \nContent-Length: 0\r\nDate: Fri, 30 Mar 2012 17:30:10
>> >>>>>>>>>>>>>> > GMT\r\n\r
>> >>>>>>>>>>>>>> > \n====================END===================="
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > "2012-03-30T17:30:10.176058Z":
>> >>>>>>>>>>>>>> > 101184:NAT:DEBUG:voiptest.netappsid.local:SipRouter-15:
>> >>>>>>>>>>>>>> > 4287F940:SipXProxy:"NTAP considering REGISTER
>> >>>>>>>>>>>>>> > sip:192.168.175.22
>> >>>>>>>>>>>>>> > SIP/2.0\r\nVia: SIP/2.0/UDP 192.168.175.136:
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > 5060;rport=5060;branch=z9hG4bKPj3b0817f3-43c8-4ce0-a346-d8008040fe2c
>> >>>>>>>>>>>>>> > \r\nMax-Forwards: 70\r\nFrom: <sip:[email protected]
>> >>>>>>>>>>>>>> > >;tag=19f76c2c-9a0c-4f24-9f2c-afd86d03ef35\r\nTo:
>> >>>>>>>>>>>>>> > > <sip:[email protected]
>> >>>>>>>>>>>>>> > >\r\nCall-Id:
>> >>>>>>>>>>>>>> > > bc3d355a-5161-4c83-b5f0-a59c471be90d\r\nCseq:
>> >>>>>>>>>>>>>> > > 25984
>> >>>>>>>>>>>>>> > REGISTER\r\nUser-Agent: SFLphone\r\nContact:
>> >>>>>>>>>>>>>> > <sip:[email protected].
>> >>>>>>>>>>>>>> > 136:5060;x-sipX-nonat>\r\nExpires: 600\r\nAllow: PRACK,
>> >>>>>>>>>>>>>> > SUBSCRIBE,
>> >>>>>>>>>>>>>> > NOTIFY, REFER, INVITE, ACK, BYE, CANCEL, UPDATE, INFO,
>> >>>>>>>>>>>>>> > REGISTER,
>> >>>>>>>>>>>>>> > OPTIONS, MESSAGE\r\nContent-Length: 0\r\nDate: Fri, 30
>> >>>>>>>>>>>>>> > Mar
>> >>>>>>>>>>>>>> > 2012 17:30:10 GMT"
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > --
>> >>>>>>>>>>>>>> > Michael Picher, Director of Technical Services
>> >>>>>>>>>>>>>> > eZuce, Inc.
>> >>>>>>>>>>>>>> > 300 Brickstone Square
>> >>>>>>>>>>>>>> > Suite 201
>> >>>>>>>>>>>>>> > Andover, MA. 01810
>> >>>>>>>>>>>>>> > O.978-296-1005 X2015
>> >>>>>>>>>>>>>> > M.207-956-0262
>> >>>>>>>>>>>>>> > @mpicher <http://twitter.com/mpicher>
>> >>>>>>>>>>>>>> > www.ezuce.com
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > ------------------------------------------------------------------------------------------------------------
>> >>>>>>>>>>>>>> > There are 10 kinds of people in the world, those who
>> >>>>>>>>>>>>>> > understand
>> >>>>>>>>>>>>>> > binary and those who don't.
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > --
>> >>>>>>>>>>>>>> > ~~~~~~~~~~~~~~~~~~
>> >>>>>>>>>>>>>> > Tony Graziano, Manager
>> >>>>>>>>>>>>>> > Telephone: 434.984.8430
>> >>>>>>>>>>>>>> > sip: [email protected]
>> >>>>>>>>>>>>>> > Fax: 434.465.6833
>> >>>>>>>>>>>>>> > ~~~~~~~~~~~~~~~~~~
>> >>>>>>>>>>>>>> > Linked-In Profile:
>> >>>>>>>>>>>>>> > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> >>>>>>>>>>>>>> > Ask about our Internet Fax services!
>> >>>>>>>>>>>>>> > ~~~~~~~~~~~~~~~~~~
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > LAN/Telephony/Security and Control Systems Helpdesk:
>> >>>>>>>>>>>>>> > Telephone: 434.984.8426
>> >>>>>>>>>>>>>> > sip: [email protected]
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > Helpdesk Customers: http://myhelp.myitdepartment.net
>> >>>>>>>>>>>>>> > Blog: http://blog.myitdepartment.net
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > --
>> >>>>>>>>>>>>>> > ~~~~~~~~~~~~~~~~~~
>> >>>>>>>>>>>>>> > Tony Graziano, Manager
>> >>>>>>>>>>>>>> > Telephone: 434.984.8430
>> >>>>>>>>>>>>>> > sip: [email protected]
>> >>>>>>>>>>>>>> > Fax: 434.465.6833
>> >>>>>>>>>>>>>> > ~~~~~~~~~~~~~~~~~~
>> >>>>>>>>>>>>>> > Linked-In Profile:
>> >>>>>>>>>>>>>> > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> >>>>>>>>>>>>>> > Ask about our Internet Fax services!
>> >>>>>>>>>>>>>> > ~~~~~~~~~~~~~~~~~~
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> > LAN/Telephony/Security and Control Systems Helpdesk:
>> >>>>>>>>>>>>>> > Telephone: 434.984.8426
>> >>>>>>>>>>>>>> > sip: [email protected]
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > Helpdesk Customers: http://myhelp.myitdepartment.net
>> >>>>>>>>>>>>>> > Blog: http://blog.myitdepartment.net
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>> >
>> >>>>>>>>>>>>>> > _______________________________________________
>> >>>>>>>>>>>>>> > sipx-users mailing list
>> >>>>>>>>>>>>>> > [email protected]
>> >>>>>>>>>>>>>> > List Archive:
>> >>>>>>>>>>>>>> > http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> _______________________________________________
>> >>>>>>>>>>>>>> sipx-users mailing list
>> >>>>>>>>>>>>>> [email protected]
>> >>>>>>>>>>>>>> List Archive:
>> >>>>>>>>>>>>>> http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> _______________________________________________
>> >>>>>>>>> sipx-users mailing list
>> >>>>>>>>> [email protected]
>> >>>>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Michael Picher, Director of Technical Services
>> >>>>>>>> eZuce, Inc.
>> >>>>>>>>
>> >>>>>>>> 300 Brickstone Square
>> >>>>>>>>
>> >>>>>>>> Suite 201
>> >>>>>>>>
>> >>>>>>>> Andover, MA. 01810
>> >>>>>>>>
>> >>>>>>>> O.978-296-1005 X2015
>> >>>>>>>> M.207-956-0262
>> >>>>>>>> @mpicher <http://twitter.com/mpicher>
>> >>>>>>>> www.ezuce.com
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> ------------------------------------------------------------------------------------------------------------
>> >>>>>>>> There are 10 kinds of people in the world, those who understand
>> >>>>>>>> binary and those who don't.
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> _______________________________________________
>> >>>>>>>> sipx-users mailing list
>> >>>>>>>> [email protected]
>> >>>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> _______________________________________________
>> >>>>>>> sipx-users mailing list
>> >>>>>>> [email protected]
>> >>>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> ~~~~~~~~~~~~~~~~~~
>> >>>>>> Tony Graziano, Manager
>> >>>>>> Telephone: 434.984.8430
>> >>>>>> sip: [email protected]
>> >>>>>> Fax: 434.465.6833
>> >>>>>> ~~~~~~~~~~~~~~~~~~
>> >>>>>> Linked-In Profile:
>> >>>>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> >>>>>> Ask about our Internet Fax services!
>> >>>>>> ~~~~~~~~~~~~~~~~~~
>> >>>>>>
>> >>>>>> LAN/Telephony/Security and Control Systems Helpdesk:
>> >>>>>> Telephone: 434.984.8426
>> >>>>>> sip: [email protected]
>> >>>>>>
>> >>>>>> Helpdesk Customers: http://myhelp.myitdepartment.net
>> >>>>>> Blog: http://blog.myitdepartment.net
>> >>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> sipx-users mailing list
>> >>>>>> [email protected]
>> >>>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> sipx-users mailing list
>> >>>>> [email protected]
>> >>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> ~~~~~~~~~~~~~~~~~~
>> >>>> Tony Graziano, Manager
>> >>>> Telephone: 434.984.8430
>> >>>> sip: [email protected]
>> >>>> Fax: 434.465.6833
>> >>>> ~~~~~~~~~~~~~~~~~~
>> >>>> Linked-In Profile:
>> >>>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> >>>> Ask about our Internet Fax services!
>> >>>> ~~~~~~~~~~~~~~~~~~
>> >>>>
>> >>>> LAN/Telephony/Security and Control Systems Helpdesk:
>> >>>> Telephone: 434.984.8426
>> >>>> sip: [email protected]
>> >>>>
>> >>>> Helpdesk Customers: http://myhelp.myitdepartment.net
>> >>>> Blog: http://blog.myitdepartment.net
>> >>>>
>> >>>> _______________________________________________
>> >>>> sipx-users mailing list
>> >>>> [email protected]
>> >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> sipx-users mailing list
>> >>> [email protected]
>> >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> ~~~~~~~~~~~~~~~~~~
>> >> Tony Graziano, Manager
>> >> Telephone: 434.984.8430
>> >> sip: [email protected]
>> >> Fax: 434.465.6833
>> >> ~~~~~~~~~~~~~~~~~~
>> >> Linked-In Profile:
>> >> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> >> Ask about our Internet Fax services!
>> >> ~~~~~~~~~~~~~~~~~~
>> >>
>> >> LAN/Telephony/Security and Control Systems Helpdesk:
>> >> Telephone: 434.984.8426
>> >> sip: [email protected]
>> >>
>> >> Helpdesk Customers: http://myhelp.myitdepartment.net
>> >> Blog: http://blog.myitdepartment.net
>> >>
>> >> _______________________________________________
>> >> sipx-users mailing list
>> >> [email protected]
>> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >
>> >
>> >
>> > _______________________________________________
>> > sipx-users mailing list
>> > [email protected]
>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~
>> Tony Graziano, Manager
>> Telephone: 434.984.8430
>> sip: [email protected]
>> Fax: 434.465.6833
>> ~~~~~~~~~~~~~~~~~~
>> Linked-In Profile:
>> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>> Ask about our Internet Fax services!
>> ~~~~~~~~~~~~~~~~~~
>>
>> --
>>
>> LAN/Telephony/Security and Control Systems Helpdesk:
>> Telephone: 434.984.8426
>> sip: [email protected]
>>
>> Helpdesk Customers: http://myhelp.myitdepartment.net
>> Blog: http://blog.myitdepartment.net
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/



-- 
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

-- 
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to