7975 can't call PRI PBX , but 7911 work well

Unanswered Question
Sep 10th, 2010


Hi,

we have CCM 7.1 and one H323 voice gateway connect to AVAYA BPX with PRI E1.another H323 VG connect to PSTN with PRI E1.

our all ipphone in region A,
PSTN's voice gateway in region B
AVAYA's voice gateway in region C.

codec design as next:
G.711: A<-->A,A<-->B,B<-->B,C<-->C
G.729: A<-->c,B<-->C

it works well when 7911 call to AVAYA BPX and all ipphone call to PSTN.
But 7975 call to AVAYA BPX, the Call immediately disconnect after avaya's phone one ring,I can not know what's current codec on 7975.

next I take a call from 7975 to 7911, it's ok,and the call status of 7975 display current codec is g.711,then I use 7911 transfer the call to AVAYA BPX,7975 call to AVAYA PBX successfully ,now the call status of 7975 change to g.729.


show call histroy voice with a successful call from 7911(DN:1002) to AVAYA(DN:117000) at next :


GENERIC:
SetupTime=18313950660 ms
Index=312783
PeerAddress=1002
PeerSubAddress=
PeerId=0
PeerIfIndex=0
LogicalIfIndex=0
DisconnectCause=10 
DisconnectText=normal call clearing (16)
ConnectTime=18313952040 ms
DisconnectTime=18313954740 ms
CallDuration=00:00:02 sec
CallOrigin=2
ReleaseSource=2
ChargedUnits=0
InfoType=speech
TransmitPackets=133
TransmitBytes=1755215008
ReceivePackets=129
ReceiveBytes=2544
VOIP:
ConnectionId[0x807AB3B3 0x52E491C8 0x900D002 0xA401F38]
IncomingConnectionId[0x807AB3B3 0x52E491C8 0x900D002 0xA401F38]
CallID=312797
RemoteIPAddress=192.168.242.84
RemoteUDPPort=24630
RemoteSignallingIPAddress=192.168.242.84
RemoteSignallingPort=53364
RemoteMediaIPAddress=192.168.31.56
RemoteMediaPort=24630
SRTP = off
TextRelay = off
Fallback Icpif=0
Fallback Loss=0
Fallback Delay=0
RoundTripDelay=0 ms
SelectedQoS=best-effort
tx_DtmfRelay=inband-voice
FastConnect=FALSE

AnnexE=FALSE

Separate H245 Connection=TRUE

H245 Tunneling=FALSE

SessionProtocol=cisco
ProtocolCallId=
SessionTarget=
OnTimeRvPlayout=1230
GapFillWithSilence=0 ms
GapFillWithPrediction=0 ms
GapFillWithInterpolation=0 ms
GapFillWithRedundancy=0 ms
HiWaterPlayoutDelay=70 ms
LoWaterPlayoutDelay=70 ms
PlayoutMode = undefined
PlayoutInitialDelay=0 ms
ReceiveDelay=70 ms
LostPackets=0
EarlyPackets=0
LatePackets=0
VAD = disabled
CoderTypeRate=g729br8
CodecBytes=20
cvVoIPCallHistoryIcpif=0
MediaSetting=flow-through
CallerName=
CallerIDBlocked=False
OriginalCallingNumber=1002
OriginalCallingOctet=0x0
OriginalCalledNumber=117000
OriginalCalledOctet=0x80
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0xFF
TranslatedCallingNumber=1002
TranslatedCallingOctet=0x0
TranslatedCalledNumber=117000
TranslatedCalledOctet=0x80
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0xFF
GwReceivedCalledNumber=117000
GwReceivedCalledOctet3=0x80
GwReceivedCallingNumber=1002
GwReceivedCallingOctet3=0x0
GwReceivedCallingOctet3a=0x81
MediaInactiveDetected=no
MediaInactiveTimestamp=
MediaControlReceived=
LongDurationCallDetected=no
LongDurationCallTimerStamp=
LongDurationCallDuration=
Username=

GENERIC:
SetupTime=18313950680 ms
Index=312784
PeerAddress=117000
PeerSubAddress=
PeerId=1
PeerIfIndex=73
LogicalIfIndex=71
DisconnectCause=10 
DisconnectText=normal call clearing (16)
ConnectTime=18313952040 ms
DisconnectTime=18313954780 ms
CallDuration=00:00:02 sec
CallOrigin=1
ReleaseSource=2
ChargedUnits=0
InfoType=speech
TransmitPackets=129
TransmitBytes=3576
ReceivePackets=133
ReceiveBytes=2392
TELE:
ConnectionId=[0x807AB3B3 0x52E491C8 0x900D002 0xA401F38]
IncomingConnectionId=[0x807AB3B3 0x52E491C8 0x900D002 0xA401F38]
CallID=312798
Port=0/1/0:15 (312798)
BearerChannel=0/1/0.30
TxDuration=2620 ms
VoiceTxDuration=1360 ms
FaxTxDuration=0 ms
CoderTypeRate=g729br8
NoiseLevel=-72
ACOMLevel=53
SessionTarget=
ImgPages=0
CallerName=
CallerIDBlocked=False
AlertTimepoint=1134081496 ms
LongDurationCallDetected=no
LongDurCallTimeStamp=
LongDurCallDuration=
OriginalCallingNumber=1002
OriginalCallingOctet=0x0
OriginalCalledNumber=117000
OriginalCalledOctet=0x80
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0xFF
TranslatedCallingNumber=1002
TranslatedCallingOctet=0x0
TranslatedCalledNumber=117000
TranslatedCalledOctet=0x80
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0xFF
GwReceivedCalledNumber=117000
GwReceivedCalledOctet3=0x80
GwOutpulsedCalledNumber=7000
GwOutpulsedCalledOctet3=0x80
GwReceivedCallingNumber=1002
GwReceivedCallingOctet3=0x0
GwReceivedCallingOctet3a=0x81
GwOutpulsedCallingNumber=1002
GwOutpulsedCallingOctet3=0x0
GwOutpulsedCallingOctet3a=0x81
DSPIdentifier=0/1:5

A unsuccessful call from 7975(DN:1200) to AVAYA(DN:117000) at next :


GENERIC:
SetupTime=18314086930 ms
Index=312799
PeerAddress=1200
PeerSubAddress=
PeerId=12
PeerIfIndex=76
LogicalIfIndex=0
DisconnectCause=2F 
DisconnectText=no resource (47)
ConnectTime=0 ms
DisconnectTime=18314087000 ms
CallDuration=00:00:00 sec
CallOrigin=2
ReleaseSource=2
ChargedUnits=0
InfoType=speech
TransmitPackets=0
TransmitBytes=0
ReceivePackets=0
ReceiveBytes=0
VOIP:
ConnectionId[0x806EC304 0xDAE491C8 0xA00D102 0xA401F4A]
IncomingConnectionId[0x806EC304 0xDAE491C8 0xA00D102 0xA401F4A]
CallID=312811
RemoteIPAddress=192.168.242.84
RemoteUDPPort=0
RemoteSignallingIPAddress=192.168.242.84
RemoteSignallingPort=53399
RemoteMediaIPAddress=0.0.0.0
RemoteMediaPort=0
SRTP = off
TextRelay = off
Fallback Icpif=0
Fallback Loss=0
Fallback Delay=0
RoundTripDelay=0 ms
SelectedQoS=best-effort
tx_DtmfRelay=inband-voice
FastConnect=FALSE

AnnexE=FALSE

Separate H245 Connection=TRUE

H245 Tunneling=FALSE

SessionProtocol=cisco
ProtocolCallId=
SessionTarget=
OnTimeRvPlayout=0
GapFillWithSilence=0 ms
GapFillWithPrediction=0 ms
GapFillWithInterpolation=0 ms
GapFillWithRedundancy=0 ms
HiWaterPlayoutDelay=0 ms
LoWaterPlayoutDelay=0 ms
ReceiveDelay=0 ms
LostPackets=0
EarlyPackets=0
LatePackets=0
VAD = enabled
CoderTypeRate=None
CodecBytes=0
cvVoIPCallHistoryIcpif=0
MediaSetting=flow-through
CallerName=
CallerIDBlocked=False
OriginalCallingNumber=1200
OriginalCallingOctet=0x0
OriginalCalledNumber=117000
OriginalCalledOctet=0x80
OriginalRedirectCalledNumber=
OriginalRedirectCalledOctet=0xFF
TranslatedCallingNumber=1200
TranslatedCallingOctet=0x0
TranslatedCalledNumber=117000
TranslatedCalledOctet=0x80
TranslatedRedirectCalledNumber=
TranslatedRedirectCalledOctet=0xFF
GwReceivedCalledNumber=117000
GwReceivedCalledOctet3=0x80
GwReceivedCallingNumber=1200
GwReceivedCallingOctet3=0x0
GwReceivedCallingOctet3a=0x81
MediaInactiveDetected=no
MediaInactiveTimestamp=
MediaControlReceived=
LongDurationCallDetected=no
LongDurationCallTimerStamp=
LongDurationCallDuration=
Username=

I checked the error code :

DisconnectCause=2F 
DisconnectText=no resource (47)

Maybe it means DSP resource lack,but the AVAYA VG has enough DSP resource.


l have a suspicion that 7975 sent some special message to AVAYA PBX,but the PBX can not recognise or accepte .

Any help would be appreciated.

Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ilicveselin Fri, 09/10/2010 - 09:12

Hello Rick,

I had similar problem when my ATA 186 could not call to Avaya (one ring on avaya phone, and that is all), and other phones did. I also had capture in wireshark with code "no resource available".

Problem was slolved by changing the codec on ATA to g729 despite the settings on Avaya was the G711.

I'm guessing that both 7911 and 7975 are in same device pool and had same CSS and partitions apllied to phone and lines.

Maybe you can try to look at the stream on the web page of the 7975 phone when the phone is transfered and connected to the avaya gw, and see what IP address is remote IP address - maybe it is dsp resource address on voice gateways, and because that the call is posible in that case.

Maybe 7975 is trying to use some defferent flavour of g729 codec, where the 7911 uses g729br8.

Felipe Garrido Mon, 09/13/2010 - 07:23

Can you enable and collect the following debugs for a failed call on the gateway.

debug voip ccapi inout

debug h245 asn1

debug h225 q931

debug h225 asn1

Please note the calling and called party numbers.

Also, include the running configuration of the gateway.

-Felipe

Actions

This Discussion

Related Content