Home » Forums » Community Edition » trixbox endpoints

Nokia N95 SIP client

ric9887
Posts: 47
 Member Since:
2006-08-13
Submitted by ric9887 on Wed, 05/02/2007 - 3:30am.

I have setup SIP on my N95 connected though T-mobile following the link below.

http://voxilla.com/voxilla-stories/voxilla-how-to-guides/using-th...

My phone initially registers ok as an extension and I can make and receive calls ok.
-- Registered SIP '204' at 149.254.192.195 port 54707 expires 3600
-- Saved useragent "Nokia RM-159 V 11.0.026" for peer 204

SIP SHOW PEERS shows the phone and the status is OK.
204/204 14x.2xx.1xx.1xx D N 54707 OK (487 ms)
202/202 192.168.0.202 D 5060 OK (55 ms)
201/201 192.168.0.201 D 5060 OK (57 ms)
200/200 192.168.0.200 D 5060 OK (57 ms)

However, after a few mins the phone shows as unreachable.
pbx*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
204/204 14x.2xx.1xx.1xx D N 54707 UNREACHABLE
202/202 192.168.0.202 D 5060 OK (57 ms)
201/201 192.168.0.201 D 5060 OK (56 ms)
200/200 192.168.0.200 D 5060 OK (57 ms)

The PBX is behind a firewall wth 5060 fwd'd to Trixbox, but I am not sure how the 54707 port is negotiated, I dont see it defined on the N95 client. The N95 and Trixbox are eitherside of a NAT.

Any help would be appreciated.

‹ 7 Digit Dialing with Polycom Phones DG-104s MGCP help needed ›

&nbsp

ric9887
Posts: 47
 Member Since:
2006-08-13
After a little further investigation
Thu, 05/10/2007 - 8:39am

After a little further investigation, I have found that if I change the QUALIFY value for the N95's extension to 200 then the phone remains contactable by *.

204/204 14x.25x.19x.19x D N 12165 LAGGED (264 ms)
202/202 192.168.0.202 D 5060 OK (57 ms)
201/201 192.168.0.201 D 5060 OK (56 ms)
200/200 192.168.0.200 D 5060 OK (57 ms)

I am not entirely sure why it says lagged, the initial value I used for this was YES which I believe is equal to 2000. I am guessing the NAT server on the T-Mobile network could be timing the connection out after 200ms.

This obviously incurs overhead on the T-Mobile internet connection to keep the session alive. Im just wondering what another solution for this would be. Is there a concept of a keepalive parameter which could be implemented in Nokia's SIP software which is less aggressive than the 200ms I have to use on the * side to keep the phone alive ?


&nbsp

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.