VG224 T.38
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > WebserverTalk Community > Voice Over IP > Voice over IP Cisco > VG224 T.38




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    VG224 T.38  
voip@mrga.ch


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-23-07 06:11 PM

Hello all

we still have a problem with a VG224 Gateway. We connected it to our
Callmanager
4.2(3) and configured some ports (MGCP). When we want to make a call
from a
phone attached to the VG224 the destination phone rings and I can pick
up the
call. However I don't get a voice connection. The call terminates and I
get the
busy signal. After that I have to reboot the Port on the VG224.

Has anyone an idea??

Thanks Reto

It seems that the problem is related to T.38 (see packet capture below):

No.     Time        Source                Destination           Protocol Inf
o
34 7.574297                                                MGCP     MDCX
205 AALN/S2/1@gw MGCP 0.1

Frame 34 (208 bytes on wire, 208 bytes captured)
Ethernet II,
Internet Protocol,
User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
Media Gateway Control Protocol
MDCX (ModifyConnection)
Transaction ID: 205
Endpoint: AALN/S2/1@gw-test-fx1.hel.kko.ch
Version: MGCP 0.1
[The response to this request is in frame 36]
Parameters
CallId (C): A0000000010000b0000000F5
ConnectionIdentifier (I): A
RequestIdentifier (X): 9
LocalConnectionOptions (L): L: p:20, a:PCMU, s:off, t:b8, fxr/fx:t38
Packetization period (p): 20
Codecs (a): PCMU
Silence Suppression (s): off
Type of Service (r): b8
Unknown parameter:  fxr/fx:t38
ConnectionMode (M): recvonly
RequestedEvents (R): L/hu
QuarantineHandling (Q): process,loop


No.     Time        Source                Destination           Protocol Inf
o
36 7.577209                                                MGCP     510 205
fx: setting cannot be supported

Frame 36 (82 bytes on wire, 82 bytes captured)
Ethernet II,
Internet Protocol,
User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
Media Gateway Control Protocol
Response Code: The transaction could not be executed, because a protocol
error was detected. (510)
Transaction ID: 205
Response String: fx: setting cannot be supported
[This is a response to a request in frame 34]
[Time from request: 0.002912000 seconds]





[ Post a follow-up to this message ]



    Re: VG224 T.38  
Fedorov, Konstantin


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-23-07 06:11 PM

Hi Reto,

Send a snip of you config.
Try to turn off T38 and check.

-----------------------
Sincerely Yours,
Konstantin Fedorov

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of voip@mrga.ch
Sent: Monday, April 23, 2007 5:20 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] VG224 T.38

Hello all

we still have a problem with a VG224 Gateway. We connected it to our
Callmanager
4.2(3) and configured some ports (MGCP). When we want to make a call
from a
phone attached to the VG224 the destination phone rings and I can pick
up the
call. However I don't get a voice connection. The call terminates and I
get the
busy signal. After that I have to reboot the Port on the VG224.

Has anyone an idea??

Thanks Reto

It seems that the problem is related to T.38 (see packet capture below):

No.     Time        Source                Destination           Protocol
Info
34 7.574297                                                MGCP
MDCX
205 AALN/S2/1@gw MGCP 0.1

Frame 34 (208 bytes on wire, 208 bytes captured)
Ethernet II,
Internet Protocol,
User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
Media Gateway Control Protocol
MDCX (ModifyConnection)
Transaction ID: 205
Endpoint: AALN/S2/1@gw-test-fx1.hel.kko.ch
Version: MGCP 0.1
[The response to this request is in frame 36]
Parameters
CallId (C): A0000000010000b0000000F5
ConnectionIdentifier (I): A
RequestIdentifier (X): 9
LocalConnectionOptions (L): L: p:20, a:PCMU, s:off, t:b8,
fxr/fx:t38
Packetization period (p): 20
Codecs (a): PCMU
Silence Suppression (s): off
Type of Service (r): b8
Unknown parameter:  fxr/fx:t38
ConnectionMode (M): recvonly
RequestedEvents (R): L/hu
QuarantineHandling (Q): process,loop


No.     Time        Source                Destination           Protocol
Info
36 7.577209                                                MGCP
510 205
fx: setting cannot be supported

Frame 36 (82 bytes on wire, 82 bytes captured)
Ethernet II,
Internet Protocol,
User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
Media Gateway Control Protocol
Response Code: The transaction could not be executed, because a
protocol
error was detected. (510)
Transaction ID: 205
Response String: fx: setting cannot be supported
[This is a response to a request in frame 34]
[Time from request: 0.002912000 seconds]



 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip





[ Post a follow-up to this message ]



    Re: VG224 T.38  
voip@mrga.ch


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-23-07 06:11 PM

mgcp
mgcp call-agent cmt1 service-type mgcp version 0.1
mgcp fax t38 inhibit

That's all we have configured with mgcp

Reto

Zitat von "Fedorov, Konstantin" <kfedor@amt.ru>:

> Hi Reto,
>
> Send a snip of you config.
> Try to turn off T38 and check.
>
> -----------------------
> Sincerely Yours,
> Konstantin Fedorov
>
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of voip@mrga.ch
> Sent: Monday, April 23, 2007 5:20 PM
> To: cisco-voip@puck.nether.net
> Subject: [cisco-voip] VG224 T.38
>
> Hello all
>
> we still have a problem with a VG224 Gateway. We connected it to our
> Callmanager
> 4.2(3) and configured some ports (MGCP). When we want to make a call
> from a
> phone attached to the VG224 the destination phone rings and I can pick
> up the
> call. However I don't get a voice connection. The call terminates and I
> get the
> busy signal. After that I have to reboot the Port on the VG224.
>
> Has anyone an idea??
>
> Thanks Reto
>
> It seems that the problem is related to T.38 (see packet capture below):
>
> No.     Time        Source                Destination           Protocol
> Info
>      34 7.574297                                                MGCP
> MDCX
> 205 AALN/S2/1@gw MGCP 0.1
>
> Frame 34 (208 bytes on wire, 208 bytes captured)
> Ethernet II,
> Internet Protocol,
> User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
> Media Gateway Control Protocol
>     MDCX (ModifyConnection)
>     Transaction ID: 205
>     Endpoint: AALN/S2/1@gw-test-fx1.hel.kko.ch
>     Version: MGCP 0.1
>     [The response to this request is in frame 36]
>     Parameters
>         CallId (C): A0000000010000b0000000F5
>         ConnectionIdentifier (I): A
>         RequestIdentifier (X): 9
>         LocalConnectionOptions (L): L: p:20, a:PCMU, s:off, t:b8,
> fxr/fx:t38
>             Packetization period (p): 20
>             Codecs (a): PCMU
>             Silence Suppression (s): off
>             Type of Service (r): b8
>             Unknown parameter:  fxr/fx:t38
>         ConnectionMode (M): recvonly
>         RequestedEvents (R): L/hu
>         QuarantineHandling (Q): process,loop
>
>
> No.     Time        Source                Destination           Protocol
> Info
>      36 7.577209                                                MGCP
> 510 205
> fx: setting cannot be supported
>
> Frame 36 (82 bytes on wire, 82 bytes captured)
> Ethernet II,
> Internet Protocol,
> User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
> Media Gateway Control Protocol
>     Response Code: The transaction could not be executed, because a
> protocol
> error was detected. (510)
>     Transaction ID: 205
>     Response String: fx: setting cannot be supported
>     [This is a response to a request in frame 34]
>     [Time from request: 0.002912000 seconds]
>
>
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>





[ Post a follow-up to this message ]



    Re: VG224 T.38  
Fedorov, Konstantin


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-23-07 06:11 PM


What about ccm-manager configuration ??

And try
No mgcp fax t38 inhibit - in general it must not resolve problem but
what changed ??

-----------------------
Sincerely Yours,
Konstantin Fedorov

-----Original Message-----
From: voip@mrga.ch [mailto:voip@mrga.ch]
Sent: Monday, April 23, 2007 7:06 PM
To: Fedorov, Konstantin
Cc: cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] VG224 T.38

mgcp
mgcp call-agent cmt1 service-type mgcp version 0.1
mgcp fax t38 inhibit

That's all we have configured with mgcp

Reto

Zitat von "Fedorov, Konstantin" <kfedor@amt.ru>:

> Hi Reto,
>
> Send a snip of you config.
> Try to turn off T38 and check.
>
> -----------------------
> Sincerely Yours,
> Konstantin Fedorov
>
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of voip@mrga.ch
> Sent: Monday, April 23, 2007 5:20 PM
> To: cisco-voip@puck.nether.net
> Subject: [cisco-voip] VG224 T.38
>
> Hello all
>
> we still have a problem with a VG224 Gateway. We connected it to our
> Callmanager
> 4.2(3) and configured some ports (MGCP). When we want to make a call
> from a
> phone attached to the VG224 the destination phone rings and I can pick
> up the
> call. However I don't get a voice connection. The call terminates and
I
> get the
> busy signal. After that I have to reboot the Port on the VG224.
>
> Has anyone an idea??
>
> Thanks Reto
>
> It seems that the problem is related to T.38 (see packet capture
below):
>
> No.     Time        Source                Destination
Protocol
> Info
>      34 7.574297                                                MGCP
> MDCX
> 205 AALN/S2/1@gw MGCP 0.1
>
> Frame 34 (208 bytes on wire, 208 bytes captured)
> Ethernet II,
> Internet Protocol,
> User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
> Media Gateway Control Protocol
>     MDCX (ModifyConnection)
>     Transaction ID: 205
>     Endpoint: AALN/S2/1@gw-test-fx1.hel.kko.ch
>     Version: MGCP 0.1
>     [The response to this request is in frame 36]
>     Parameters
>         CallId (C): A0000000010000b0000000F5
>         ConnectionIdentifier (I): A
>         RequestIdentifier (X): 9
>         LocalConnectionOptions (L): L: p:20, a:PCMU, s:off, t:b8,
> fxr/fx:t38
>             Packetization period (p): 20
>             Codecs (a): PCMU
>             Silence Suppression (s): off
>             Type of Service (r): b8
>             Unknown parameter:  fxr/fx:t38
>         ConnectionMode (M): recvonly
>         RequestedEvents (R): L/hu
>         QuarantineHandling (Q): process,loop
>
>
> No.     Time        Source                Destination
Protocol
> Info
>      36 7.577209                                                MGCP
> 510 205
> fx: setting cannot be supported
>
> Frame 36 (82 bytes on wire, 82 bytes captured)
> Ethernet II,
> Internet Protocol,
> User Datagram Protocol, Src Port: 2427 (2427), Dst Port: 2427 (2427)
> Media Gateway Control Protocol
>     Response Code: The transaction could not be executed, because a
> protocol
> error was detected. (510)
>     Transaction ID: 205
>     Response String: fx: setting cannot be supported
>     [This is a response to a request in frame 34]
>     [Time from request: 0.002912000 seconds]
>
>
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>





[ Post a follow-up to this message ]



    Re: VG224 T.38  
dhartma5@optonline.net


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-23-07 06:11 PM

I have seen this issue a lot and it's normally related to media resources.  
Call setup and call teardown work properly, but the final step of call setup
 fails.  Analyze your call manager trade file to see if the Call Manager is 
trying to use a transco
ding or media termination point resource.

Sincerely,
Dennis Hartmann






[ Post a follow-up to this message ]



    Re: VG224 T.38  
dhartma5@optonline.net


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
04-24-07 12:11 AM

Type-o.  I meant TRACE, not trade.   Check the TRACE file for call setup and
 see if there's an allocation error.  I have seen this issue happen with a S
IP trunk configuration in Call Manager 4.x.  Every call over a SIP trunk in 
4.x requires a MTP.
-Dennis Hartmann






[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 08:34 PM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register