TN1 - Revision history

Mwp: /* RTP Packet Size */

2019-10-25T09:12:25Z

RTP Packet Size

Mwp at 04:33, 6 April 2019

2019-04-06T04:33:51Z

Mwp at 04:31, 6 April 2019

2019-04-06T04:31:47Z

Mwp at 04:30, 6 April 2019

2019-04-06T04:30:32Z

Mwp at 11:18, 8 March 2019

2019-03-08T11:18:57Z

Mwp at 08:36, 30 December 2018

2018-12-30T08:36:02Z

Mwp at 08:28, 30 December 2018

2018-12-30T08:28:23Z

Mwp at 08:24, 30 December 2018

2018-12-30T08:24:15Z

Mwp: Created page with "= TN1: Configuring a SPA504g for use with IP-Phone-C = == RTP Packet Size == The IP-Phone-C SIP server only accepts the SDP attribute value a=ptime:20. Any other value will r..."

2018-12-30T08:19:05Z

Created page with "= TN1: Configuring a SPA504g for use with IP-Phone-C = == RTP Packet Size == The IP-Phone-C SIP server only accepts the SDP attribute value a=ptime:20. Any other value will r..."

New page

= TN1: Configuring a SPA504g for use with IP-Phone-C =

== RTP Packet Size ==
The IP-Phone-C SIP server only accepts the SDP attribute value a=ptime:20. Any other value will result in a "488 Not Acceptable Here" with the warning "307 Session description parameter not understood".

The SPA504g emits this value with the following configuration:
SIP > RTP Packet Size = 0.02

@@ Line 23: / Line 23: @@
 == RTP Packet Size ==
-The IP-Phone-C SIP server only accepts a SDP attribute a=ptime with the value 20. Any other value will result in a "488 Not Acceptable Here" response, incorporating a "307 Session description parameter not understood" warning. This is an extremely difficult issue to debug without a priori, and the engineer involved should be ashamed of themselves for not providing a more meaningful error response.
+The IP-Phone-C SIP server only accepts a SDP attribute a=ptime with the value 20. Any other value will result in a "488 Not Acceptable Here" response, incorporating a "307 Session description parameter not understood" warning. This is an extremely difficult issue to debug without a priori knowledge, and the engineer involved should be ashamed of themselves for not providing a more meaningful error response.
 The SPA504g emits the correct value with the following configuration:

@@ Line 1: / Line 1: @@
-= Configuring a SPA504g for use with IP-Phone-C =
+= Configuring a Cisco SPA504g for use with IP-Phone-C =
 [https://asahi-net.jp/en/service/ipphone-c/ IP-Phone-C] is a VOIP service provided by [https://asahi-net.jp AsahiNet]. It is a rebranding of NTT's [https://ja.wikipedia.org/wiki/%E3%83%95%E3%83%AC%E3%83%83%E3%83%84#%E3%81%B2%E3%81%8B%E3%82%8A%E9%9B%BB%E8%A9%B1 Hikari] VOIP service, so these notes may be applicable to similar services from other resellers.
-The information in this note should be applicable to other VOIP handsets as well, although their configuration details will vary.
+This note describes how to configure a [https://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/small-business-spa500-series-ip-phones/data_sheet_c78-548564.html SPA504g] VOIP handset with the IP-Phone-C service. This information should be applicable to other VOIP handsets, although their configuration details will vary.
 == Subscriber Information ==

← Older revision		Revision as of 04:31, 6 April 2019
Line 2:		Line 2:

	[https://asahi-net.jp/en/service/ipphone-c/ IP-Phone-C] is a VOIP service provided by [https://asahi-net.jp AsahiNet]. It is a rebranding of NTT's [https://ja.wikipedia.org/wiki/%E3%83%95%E3%83%AC%E3%83%83%E3%83%84#%E3%81%B2%E3%81%8B%E3%82%8A%E9%9B%BB%E8%A9%B1 Hikari] VOIP service, so these notes may be applicable to similar services from other resellers.		[https://asahi-net.jp/en/service/ipphone-c/ IP-Phone-C] is a VOIP service provided by [https://asahi-net.jp AsahiNet]. It is a rebranding of NTT's [https://ja.wikipedia.org/wiki/%E3%83%95%E3%83%AC%E3%83%83%E3%83%84#%E3%81%B2%E3%81%8B%E3%82%8A%E9%9B%BB%E8%A9%B1 Hikari] VOIP service, so these notes may be applicable to similar services from other resellers.
		+
		+	The information in this note should be applicable to other VOIP handsets as well, although their configuration details will vary.

	== Subscriber Information ==		== Subscriber Information ==

@@ Line 1: / Line 1: @@
 = Configuring a SPA504g for use with IP-Phone-C =
 == Subscriber Information ==
-Configure an extension as follows:
+Configure an extension on the handset as follows:
- EXT > Display Name = <Phone Number>
+ EXT > Display Name = <Your 050 Phone Number>
- EXT > User Id = <Phone Number>
+ EXT > User Id = <Your 050 Phone Number>
- EXT > Password = <Password>
+ EXT > Password = <Your Password>
  EXT > Use Auth Id = Yes
- EXT > Auth Id = <User Id>
+ EXT > Auth Id = <Your User Id>
 == Audio Configuration ==
@@ Line 19: / Line 21: @@
 == RTP Packet Size ==
-The IP-Phone-C SIP server only accepts a SDP attribute a=ptime with the value 20. Any other value will result in a "488 Not Acceptable Here" response, incorporating a "307 Session description parameter not understood" warning. The engineer who programmed this is a bad person.
+The IP-Phone-C SIP server only accepts a SDP attribute a=ptime with the value 20. Any other value will result in a "488 Not Acceptable Here" response, incorporating a "307 Session description parameter not understood" warning. This is an extremely difficult issue to debug without a priori, and the engineer involved should be ashamed of themselves for not providing a more meaningful error response.
 The SPA504g emits the correct value with the following configuration:

← Older revision		Revision as of 11:18, 8 March 2019
Line 1:		Line 1:
−	= ~~TN1:~~ Configuring a SPA504g for use with IP-Phone-C =	+	= Configuring a SPA504g for use with IP-Phone-C =

	== Subscriber Information ==		== Subscriber Information ==

@@ Line 11: / Line 11: @@
 == Audio Configuration ==
 The IP-Phone-C SIP server only supports the G711u codec. Other codecs, or too many proposed codecs, may trigger a "488 Not Acceptable Here" response. Therefore configuration with just G711u is recommended.
  EXT > Preferred Codec = G711u
  EXT > Use Pref Codec Only = Yes
 == RTP Packet Size ==