Hi Josh,

That's strange. In my Solaris server typing netstat -a | grep 9200 returns:

*.9200                              Idle

The problem is firewall/access issue.

UDP Ports 9200 - 9203 (9202 & 9203 if you enable wtls) are standard for wap 1.x 
and your mobile will use them by default. You need to have a wap 1.x mobile and 
possibly an Internet enabled SIM card, so that you can access your gateway by 
IP. You have also to allow connections to your WAP ports from  your MSN to your 
gateway.

BR,
Nikos
  ----- Original Message ----- 
  From: Kao. Josh (GSM) 
  To: Nikos Balkanas ; [email protected] 
  Sent: Friday, February 06, 2009 8:29 AM
  Subject: RE: Can't find a port to receive link request in wap gateway


  Dear Nikos, 

   

  I check “netstat –a|grep 9200” and it doesn’t show anything. 

  Since I supposed bearerbox is bound to tcp port, I didn’t check udp port 
before. 

  So I try “netstat -tulnp” and it shows there is bearerbox process running on 
the udp port 9200 and 9201 respectly. 

  I attach the netstat –tulnp result in the following.

   

  [r...@localhost sbin]# netstat -tulnp

  Active Internet connections (only servers)

  Proto Recv-Q Send-Q Local Address               Foreign Address             
State       PID/Program name   

  tcp        0      0 0.0.0.0:13000               0.0.0.0:*                   
LISTEN      5611/bearerbox      

  tcp        0      0 0.0.0.0:13002               0.0.0.0:*                   
LISTEN      5611/bearerbox      

  tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   
LISTEN      2040/rpcbind        

  tcp        0      0 127.0.0.1:631               0.0.0.0:*                   
LISTEN      2647/cupsd          

  tcp        0      0 127.0.0.1:25                0.0.0.0:*                   
LISTEN      2510/sendmail: acce 

  tcp        0      0 0.0.0.0:58235               0.0.0.0:*                   
LISTEN      2060/rpc.statd      

  tcp        0      0 :::22                       :::*                        
LISTEN      2489/sshd           

  udp        0      0 0.0.0.0:32768               0.0.0.0:*                     
          2060/rpc.statd      

  udp        0      0 0.0.0.0:32769               0.0.0.0:*                     
          2629/avahi-daemon:  

  udp        0      0 0.0.0.0:943                 0.0.0.0:*                     
          2040/rpcbind        

  udp        0      0 0.0.0.0:964                 0.0.0.0:*                     
          2060/rpc.statd      

  udp        0      0 0.0.0.0:5353                0.0.0.0:*                     
          2629/avahi-daemon:  

  udp        0      0 0.0.0.0:111                 0.0.0.0:*                     
          2040/rpcbind        

  udp        0      0 0.0.0.0:9200                0.0.0.0:*                     
          5611/bearerbox      

  udp        0      0 0.0.0.0:9201                0.0.0.0:*                     
          5611/bearerbox      

  udp        0      0 0.0.0.0:631                 0.0.0.0:*                     
          2647/cupsd

   

  So bearerbox is bound to udp 9200 and 9201, but my cell phone still can’t 
connect to it, do you what happen?

  By the way, just for curious. Since link request uses tcp connection, but 
bearerbox is bount to udp port, how do we make them meet together?

   

  Best Regards,

  Josh

   

   


------------------------------------------------------------------------------

  From: Nikos Balkanas [mailto:[email protected]] 
  Sent: Thursday, February 05, 2009 6:36 PM
  To: Kao. Josh (GSM); [email protected]
  Subject: Re: Can't find a port to receive link request in wap gateway

   

  Hi Kao,

   

  Are you sure that "netstat -a | grep 9200" doesn't show anything? 

  If you look at your udpc_create it clearly shows that bearerbox binds to udp 
9200.

   

  Probably your netstat output is wrong.

   

  BR,

  Nikos












  
================================================================================================================================================================
  This message may contain information which is private, privileged or 
confidential of Compal Communications, Inc. If you are not the intended 
recipient of 
  this message, please notify the sender and destroy/delete the message. Any 
review, retransmission, dissemination or other use of, or taking of any 
  action in reliance upon this information, by persons or entities other than 
the intended recipient is prohibited.
  
================================================================================================================================================================
  


Reply via email to