Sample Sipura config for Hong Kong BroadBand "2b" service

Assumptions:

• Account created starting October 2005 (if your account is before October 2005 or is NOT a "2b" account, then you want to look here
• Softphone password: abcdef9876
• Phone number: 35129898

SIP > RTP Parameters
 RTP Packet Size: 0.020 (Crucial to enable incoming calls)

Line 1 > Proxy and Registration
 Proxy: s2hkbntel.net
 Use Outbound Proxy: yes
 Outbound Proxy: s21.hkbntel.net
 Use OB Proxy In Dialog: yes
 Register Expires: 120
 Use DNS SRV: no

Line 1 > Subscriber Information
 User ID: 35129898hk
 Password: abcdef9876

Line 1 > Audio Configuration
 DTMF Tx Method: InBand
 Symmetric RTP: yes (if it's a SPA-3000)

Regional > Vertical Service Activation Codes
 Block CID Per Call Act Code: 133
 Block CID Per Call Deact Code: 1357

Regional > Miscellaneous
 Caller ID Method: ETSI FSK With PR(UK) "(set this if you use a phone with caller display from HK)"

Network Address Translation Situation

If you are behind a Firewall/NAT router, you have two options:

1. Portforwarding
2. STUN

Portforwarding

The following ports must be portforwarded from your Firewall/NAT router to your SPA:

• UDP 5060
• The UDP port range specified from SIP > RTP Parameters > RTP Port Min until SIP > RTP Parameters > RTP Port Max

(Check the "STUN or RPORT" section below for details)

STUN Support

SIP > NAT Support Parameters
 Handle VIA received: yes
 Handle VIA rport: yes
 Insert VIA received: yes
 Insert VIA rport: yes
 Substitute VIA Addr: yes
 Send Resp To Src Port: yes
 STUN Enable: yes
 STUN Test Enable: yes
 STUN Server: any public STUN server
 NAT Keep Alive Intvl: 15 (can be increased after you are confident everything is configured properly)

Line 1 > NAT Settings
 NAT Mapping Enable: yes
 NAT Keep Alive Enable: yes
 NAT Keep Alive Msg: $PING
 NAT Keep Alive Dest: $PROXY

Dial Plan

Add the following to your dialplan to enable 8-digit and 852-prefixed 8-digit Hong Kong phone numbers. This diaplan should be added before the final right-parenthesis ')' character.

Line 1 > Dial Plan
 Dial Plan: <852:>[236789]xxxxxxxS0|[236789]xxxxxxxS0|1850xS0|188xS0

Therefore, if your original dialplan looked like this:
 Dial Plan: ([2-9]xxxxxx|011xx.|1[2-9]xx[2-9]xxxxxx)

The new HK enabled dialplan would be:
 Dial Plan: ([2-9]xxxxxx|011xx.|1[2-9]xx[2-9]xxxxxx|<852:>[236789]xxxxxxxS0|[236789]xxxxxxxS0|1850xS0|188xS0)

---

2b using at least 2 SIP Proxies

It has come to my attention that some "2b" subscribers have been moved to another SIP Proxy server. As a result, some subscribers cannot use s21.hkbntel.net as their SIP Proxy. The most obvious sign that you have been moved off of s21.hkbntel.net is if you can no longer REGISTER your presence with their SIP Proxy.

To see verify your account was moved to the other SIP Proxy, enable Debug Syslogging for your SPA.

If you see something like the following in your syslogs:

SIP/2.0 301 Moved Permanently

t: <sip:35129898@s2hkbntel.net>;tag=922074415
f: <sip:35129898@s2hkbntel.net>;tag=ec3f4cef5aa1376bo1
i: 46ccadff-b8c4c99b@192.168.1.102
CSeq: 136 REGISTER
v: SIP/2.0/UDP 169.129.0.3:5061;rport;branch=z9hG4bK-75923633
m: <sip:s2hkbntel.net:5060;maddr=203.80.89.139>
k: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec
l: 0

If you see the "301 Moved Permanently" SIP response, then that means HKBN has moved your account to another SIP Proxy besides s21.hkbntel.net. The new SIP Proxy you should use is listed in the "m:" line. The IP address after the "maddr=" is the new SIP Proxy. The IP address 203.80.89.139 corresponds to the hostname: s22.hkbntel.net. You will need to change your Line 1 > Proxy and Registration > Outbound Proxy to match the new SIP Proxy listed after the "maddr=". In the above example, the new setting would be:

Line 1 > Proxy and Registration
 Outbound Proxy: 203.80.89.139

Additionally, if you are still having problems, you might want to enable debugging on the SPA and submit the logs to the Linksys (Sipura) VoIP Support Forum or the VOIP Forum of BroadBandReports.com.

---

STUN or RPORT

This section talks about consideration between choosing STUN or RPORT method to find your public address. If you see "Login exceeded" error in your SPA, please read this section.

HKBN 2b do not allows multiple registrations. HKBN use address/port combination of your SPA to identify multiple registrations (i.e. "Contact" header in SIP REGISTER). This cause trouble if you use a NAT router that easily loose the UDP mapping (e.g., Windows XP ICS). Say, you have NAT router and is on public IP 123.123.123.123, and your private IP is 192.168.15.100, and you set SIP port on your SPA as 5060. Although your SPA opens 192.168.15.100:5060, your NAT router will remaps your UDP to 123.123.123.123:xxxxx. That means, your Contact header in SIP REGISTER will be 123.123.123.123:xxxxx. xxxxx is pseudo-random number and your NAT will lock the port number xxxxx for a period of time for your SPA (usually, more than 150 seconds, "SIP > NAT Support Parameters > NAT Keep Alive Intvl" must be smaller than this value).

If you power cycle your SPA, you may get another port number yyyyy, instead of xxxxx. HKBN will consider 123.123.123.123:yyyyy as a new registration. Since HKBN do not support multiple registrations, you will need to go to pa.2b.com.hk to do a reset registration to enable registration on 123.123.123.123:yyyyy.

Although STUN helps your SPA to find out 123.123.123.123:xxxxx and tell HKBN that the registration is bound to it. But if your NAT easily lose UDP mapping (change from xxxxx to yyyyy), you should use static port forwarding instead of STUN.

HKBN 2b server supports RECEIVED/RPORT to identify your public address/port (i.e. 123.123.123.123:xxxxx), instead of using STUN. This helps to make sure your SPA will not register multiple address/port and prevents "Login Exceeded" errors. It is because your contact header is always 123.123.123.123:5060, instead of 123.123.123.123:xxxxx. Unless your IP had been changed, you don't have to worry about multiple registration problem.

In your NAT router, you may need to forwarding UDP 16384-16492 to your SPA. You do not need to forward UDP 5060 because the connection is always initiated from your client, and the hole is up as long as you use PING/NOTIFY to keep it open. The range 16384-16492 can be found at SIP > RTP Parameters > RTP Port Min/Max.

SIP > NAT Support Parameters
 Handle VIA received: yes
 Handle VIA rport: yes
 Insert VIA received: yes
 Insert VIA rport: yes
 Substitute VIA Addr: no
 Send Resp To Src Port: yes
 STUN Enable: no
 STUN Test Enable: no
 STUN Server: <empty>
 EXT IP: <empty>
 EXT RTP Port Min: <empty>
 NAT Keep Alive Intvl: 150 (you can set this to a lower value depends on your NAT router UDP mapping timeout)

---

Testing your SPA

Dial 2881 8888 to MTR interactive voice system. Press 1 for Cantonese, then 1 for routes, then 1 for pricing. Then say two station names. This can help you to test both DTMF and send/receive RTP audio.

---

Sipura Documentation | Sipura | Hong Kong Broadband | STUN