headers
Ramesh Babu Kuppili | 3 Dec 2007 10:29
Favicon

Megaco digitmap

Hi all,
 
Please let me know the interpretation of
 
[0-9EF].L
 
in Megaco digitmap.
 
- ramesh
_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 6 comments |
headers
Ramesh Babu Kuppili | 3 Dec 2007 20:02
Favicon

RE: Megaco digitmap

Thanks for the clarification.  So E is for '#' and F is for '*' ?  Is there a RFC that maps these?
 
Thanks once again.
 
- ramesh

From: John Wainwright [mailto:john.wainwright <at> txpcorporation.com]
Sent: Monday, December 03, 2007 11:25 PM
To: Ramesh Babu Kuppili; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

To me this means that any of the digits 0-9, # and * are ‘expected’ and that the Long timer is applied after every digit is dialed.

 

My apologies if this interpretation is incorrect.

 

Regards

John

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 3:30 AM
To: megaco <at> ietf.org
Subject: [Megaco] Megaco digitmap

 

Hi all,

 

Please let me know the interpretation of

 

[0-9EF].L

 

in Megaco digitmap.

 

- ramesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 4 comments |
headers
Sriram Yagnaraman (WT01 - TES-Mobility & Carrier Infrastructure | 3 Dec 2007 20:19

RE: Megaco digitmap

Hi Ramesh,

 

I think [0-9EF].L means, any number (including zero digits) of digits (from 0 to 9, E = * and F = #) followed by a long digit time out. You could check out H.248.1 Annex E.6 DTMF Detection Package.

 

Regards,

Sriram

Phone: 919-905-0184 (ESN: 355)

-----Original Message-----
From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 2:02 PM
To: John Wainwright; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

 

Thanks for the clarification.  So E is for '#' and F is for '*' ?  Is there a RFC that maps these?

 

Thanks once again.

 

- ramesh

 

From: John Wainwright [mailto:john.wainwright <at> txpcorporation.com]
Sent: Monday, December 03, 2007 11:25 PM
To: Ramesh Babu Kuppili; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

To me this means that any of the digits 0-9, # and * are ‘expected’ and that the Long timer is applied after every digit is dialed.

 

My apologies if this interpretation is incorrect.

 

Regards

John

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 3:30 AM
To: megaco <at> ietf.org
Subject: [Megaco] Megaco digitmap

 

Hi all,

 

Please let me know the interpretation of

 

[0-9EF].L

 

in Megaco digitmap.

 

- ramesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
atul garg | 4 Dec 2007 14:46
Picon
Favicon

Need Sample H.248 buffer containing MediaTx and UpVersion fields(urgent)

Hi,

Please provide an H.248 buffer containing MediaTx and
UpVersion fields. 

Regards

      Share files, take polls, and discuss your passions - all under one roof. Go to http://in.promos.yahoo.com/groups
Permalink | Reply | 0 comments |
headers
John Wainwright | 3 Dec 2007 18:54

RE: Megaco digitmap

To me this means that any of the digits 0-9, # and * are ‘expected’ and that the Long timer is applied after every digit is dialed.

 

My apologies if this interpretation is incorrect.

 

Regards

John

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 3:30 AM
To: megaco <at> ietf.org
Subject: [Megaco] Megaco digitmap

 

Hi all,

 

Please let me know the interpretation of

 

[0-9EF].L

 

in Megaco digitmap.

 

- ramesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 5 comments |
headers
John Wainwright | 3 Dec 2007 20:14

RE: Megaco digitmap

Check out the digitmap example in 7.1.14.9 of the V2 document.  Also, the DTMF generator/detection packages details.

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 1:02 PM
To: John Wainwright; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

 

Thanks for the clarification.  So E is for '#' and F is for '*' ?  Is there a RFC that maps these?

 

Thanks once again.

 

- ramesh

 

From: John Wainwright [mailto:john.wainwright <at> txpcorporation.com]
Sent: Monday, December 03, 2007 11:25 PM
To: Ramesh Babu Kuppili; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

To me this means that any of the digits 0-9, # and * are ‘expected’ and that the Long timer is applied after every digit is dialed.

 

My apologies if this interpretation is incorrect.

 

Regards

John

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 3:30 AM
To: megaco <at> ietf.org
Subject: [Megaco] Megaco digitmap

 

Hi all,

 

Please let me know the interpretation of

 

[0-9EF].L

 

in Megaco digitmap.

 

- ramesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
John Wainwright | 3 Dec 2007 20:16

RE: Megaco digitmap

By the way I believe that E=* and F=#

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 1:02 PM
To: John Wainwright; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

 

Thanks for the clarification.  So E is for '#' and F is for '*' ?  Is there a RFC that maps these?

 

Thanks once again.

 

- ramesh

 

From: John Wainwright [mailto:john.wainwright <at> txpcorporation.com]
Sent: Monday, December 03, 2007 11:25 PM
To: Ramesh Babu Kuppili; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

To me this means that any of the digits 0-9, # and * are ‘expected’ and that the Long timer is applied after every digit is dialed.

 

My apologies if this interpretation is incorrect.

 

Regards

John

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 3:30 AM
To: megaco <at> ietf.org
Subject: [Megaco] Megaco digitmap

 

Hi all,

 

Please let me know the interpretation of

 

[0-9EF].L

 

in Megaco digitmap.

 

- ramesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
Yanssen, Rodrigo Duarte | 3 Dec 2007 20:29

RE: Megaco digitmap

Follow ITU-T H.248.1 Annex 4, 5 and 6 you can find the packets related with this mapping.

 

Signal name SignalID/Tone ID

DTMF character 0 d0 (0x0010)

DTMF character 1 d1 (0x0011)

DTMF character 2 d2 (0x0012)

DTMF character 3 d3 (0x0013)

DTMF character 4 d4 (0x0014)

DTMF character 5 d5 (0x0015)

DTMF character 6 d6 (0x0016)

DTMF character 7 d7 (0x0017)

DTMF character 8 d8 (0x0018)

DTMF character 9 d9 (0x0019)

DTMF character * ds (0x0020)

DTMF character # do (0x0021)

DTMF character A da (0x001a)

DTMF character B db (0x001b)

DTMF character C dc (0x001c)

DTMF character D dd (0x001d)

 

 

And these Signals ID that have a Tone ID related, is correlated with other table where you can translate these Tone ID in Digits:

 

DTMF Event Symbol

d0 "0"

d1 "1"

d2 "2"

d3 "3"

d4 "4"

d5 "5"

d6 "6"

d7 "7"

d8 "8"

d9 "9"

da "A" or "a"

db "B" or "b"

dc "C" or "c"

dd "D" or "d"

ds "E" or "e"

do "F" or "f"

 

 

So The Digit * is mapping to DS that is mapping to “E or e” and the Digit # to DO that is mapping to “F or f”.

 

Take care which event you are using in your Network, DD/CE or DD/STD, because each one can result in each table above.

 

Best Regards.

 

___________________________

Rodrigo Yanssen

Nokia Siemens Network

Phone:  +55-11-3908-3527

Mobile: +55-11-8674-3537 (New)

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: segunda-feira, 3 de dezembro de 2007 17:02
To: John Wainwright; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

 

Thanks for the clarification.  So E is for '#' and F is for '*' ?  Is there a RFC that maps these?

 

Thanks once again.

 

- ramesh

 

From: John Wainwright [mailto:john.wainwright <at> txpcorporation.com]
Sent: Monday, December 03, 2007 11:25 PM
To: Ramesh Babu Kuppili; megaco <at> ietf.org
Subject: RE: [Megaco] Megaco digitmap

To me this means that any of the digits 0-9, # and * are ‘expected’ and that the Long timer is applied after every digit is dialed.

 

My apologies if this interpretation is incorrect.

 

Regards

John

 

From: Ramesh Babu Kuppili [mailto:RKuppili <at> zhone.com]
Sent: Monday, December 03, 2007 3:30 AM
To: megaco <at> ietf.org
Subject: [Megaco] Megaco digitmap

 

Hi all,

 

Please let me know the interpretation of

 

[0-9EF].L

 

in Megaco digitmap.

 

- ramesh

________________________________________
Important notice: This e-mail and any attachment thereof contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank you. For alternate languages please go to http://www.siemens.com.ar/disclaimer/
_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |
headers
ambesh.poddar | 4 Dec 2007 15:46

Distinguishing between Audio & Video Payload types using SR in RTCP packet

Hi

 

I recently started working in MG. I have a question regarding the sender reports in RTCP.

 

Can you tell me how can we distinguish between an audio & video payload type using the sender report data of an RTCP packet in ethereal?

 

Regards,

Ambesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 1 comment |
headers
Schwarz Albrecht | 4 Dec 2007 16:12
Picon
Favicon

RE: Distinguishing between Audio & Video Payload types usingSR in RTCP packet

H.248 Interface:
Each RTP-based media component is mapped on a dedicated H.248 Stream.
Further: the RTP and RTCP flows could be both mapped on the same H.248 Stream. This is the assumption in all present H.248 profile specifications (with H.248 RTP terminations) as far as I know.
There are then two H.248 Streams, one for audio-over-RTP + RTCP and another Stream for video-over-RTP + RTCP.
 
=> Wireshark discrimination point: H.248 StreamID
RTP/RTCP-over-UDP/IP Interface:
Assumption: individual L4 ports for RTP and RTCP (i.e. the mode of Multiplexed RTP and RTCP on single L4 ports is not considered.)
=> Wireshark discrimination point: UDP port numbers
Of course, you've to correlate the info of both interfaces.
 
-Albrecht
 

From: ambesh.poddar <at> wipro.com [mailto:ambesh.poddar <at> wipro.com]
Sent: Dienstag, 4. Dezember 2007 15:47
To: megaco <at> ietf.org
Subject: [Megaco] Distinguishing between Audio & Video Payload types usingSR in RTCP packet

Hi

 

I recently started working in MG. I have a question regarding the sender reports in RTCP.

 

Can you tell me how can we distinguish between an audio & video payload type using the sender report data of an RTCP packet in ethereal?

 

Regards,

Ambesh

_______________________________________________
Megaco mailing list
Megaco <at> ietf.org
https://www1.ietf.org/mailman/listinfo/megaco
Permalink | Reply | 0 comments |

Gmane