2.0 Interoperability Requirements v2


Service Provider: Junction Networks
Software Revision: Asterisk 1.6.2
Micro PBX Hardware: Shuttle K4500-RS
VoIP phones: GrandStream GXP-2000
Media Gateway: GrandStream HT-503 ver 1.0.1.41

2.1 Junction Networks Interoperability

2.1 Junction Networks Interoperability
Requirement ID
TC Name
Level
Result
Description
Notes
2.1.1
Registration
Required
PASS
The muPBX_v1 shall register with Junction NetworksNone
2.1.2
Registration
Required
PASS
The standard approach is used to challenge all requests (the Proxy-to-User Authentication scheme as outlined in Section 22.3 of RFC 3261). Customers are identified by their username. If identification by username fails, the authorization username is used. None
2.1.3
Caller-ID
Required
PASS
If the username is a valid phone number (ten or eleven digits), it is used as the caller-id number associated with a call. Otherwise, if the display name is a valid phone number, it is used as the caller-id number associated with a call.Verified the muPBX sends calling number but the CNAME is not supported in the PSTN network.
2.1.4
iLBC Support
Optional
NT
Check if your VoIP device supports iLBC compressed codec and is chosen as default or preferred codec. iLBC codec works better if you have very low speed of Internet connection or high latency such as satellite Internet connection. You can find codec options usually in advanced configuration of your VoIP device.Not Tested.
2.1.5
Long Call
Required
PASS
Verify muPBX is capable of sustaining a call for over 2 hours.Verified orig calls and terminating calls for 15 minutes. Verified the session timers in both directions.
2.1.6
Numbering
Required
PASS
The standard e.164 numbering plan (ITU) is used. North American numbers are required to be prefixed with a '1'.None
2.1.7
Incoming DID
Required
PASS
Verify incoming calls based on the DID that was called, registering with Junction Networks can be helpful if a customer subscribes to more than one DID. This server is recommended for use with SIP servers and IP PBXes.None
2.1.8
NAT Traversal
Required
PASS
Use SIP keep-alive packets or set your Registration interval below the NAT binding expiration time (90 seconds will usually suffice).Set defaultexpiry=90 in sip.conf.
2.1.9
REFER
Optional
PASS
Verify the muPBX supports REFER requests as defined in RFC 3515.Verified blind transfer using the SIP REFER method.
2.1.10
Comfort Noise
Optional
NT
Verify the muPBX supports comfort noise as specified in RFC 3389.Not Tested.
2.1.11
Silence Suppression
Required
PASS
Verify Voice Activity Detection (VAD) can be disabled.None
2.1.12
911 or E911 Support
Optional
FAIL
Verify Junction Networks supports 911 or E911.Verified Junction Networks does not support 911 services.
2.1.13
DID Routing
Optional
PASS
DID Routing provides optional extended service features such as contingency failover, routing calls to static IP addresses, routing calls utilizing multiple protocols, routing calls back into the PSTN, and adjustable timeouts.Verified DID routing but not failover.
2.1.14
Stun Server Support
Optional
NT
Verify Junction Networks Stun Server support.Not Tested.
2.1.15
Failover
Optional
NT
Failover Scenarios: 1.) Your device is not registered at all. There is therefore nowhere to send the INVITE. We fail over immediately. 2.) 5 SIP or IAX INVITE requests - 1 per second for 5 seconds - without a return response. Fail-over after 5 seconds. 3.) Rejected INVITE. If you send back "congestion" or otherwise respond to the INVITE but respond in the negative, we fail over immediately upon receipt of the negative response. 4.) If you have a SIP device and it does not pick up the call after x seconds (the seconds are up to you with a default of 120), we fail over after x seconds of ring-no-answer.Not Tested.
2.1.16
Variable Length RFC2833
Optional
FAIL
Verify the Junction Networkssupports variable length DTMF transmission using RFC2833. Verify that a digit press over 2 seconds sends 2 seconds of RFC2833 RTP Events.Verified Junction Networks does not support variable length DTMF; fixed DTMF at 800ms.
2.1.17
Minimum DTMF Cycle Time
Required
PASS
Verify the Junction Networks sends DTMF inband/outband with a cycle time of no less than 93 ms.None.
2.1.18
Minimum Inter-Digit Time
Required
PASS
Verify a minimum interdigit time of no less than 40 ms.Verified interdigit time of 190ms.
2.1.19
Minimum Digit On-Time
Required
PASS
Verify a minimum DTMF digit on-time of no less than 40 ms.None
ID
TCNAME
Required
RESULT
DescriptionVerified fixed ON time DTMF of 800ms.




Menu [toggle]