h323 gateway

Problemy związane z Unified Communications
Wiadomość
Autor
ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

h323 gateway

#1

#1 Post autor: ukaszq »

Witam,

Mam taką instrakturę: PSTN---(SIP-trunk)---CUBE---(h323)---CUCM
Próbuję podłączyć PSTNa do CUCMa ale mam problem. Szukam rozwiązania, przyczyny ale nie potrafię już sobie poradzić.
Komunikacja PSTNa do CUBE jest i otrzymuje pakiety, kiedy chcę wyjść do CUCMa z mojego routera mam błąd. W CUCM mam skonfigurowany h323 gateway.

Problem pojawia się kiedy chcę się wdzwonić na jeden z moich numerów. Na CUBE otrzymuję pakiety widzę że są one przekazywane również na dial-peer 102 co wskazuje na przekazanie rozmów do CUCM. W tym momencie połączenie jest rozrywane. Nie wiem gdzie leży problem czy w CUCM czy w konfiguracji h323 po stronie CUBE?

Oto mój config CUBE:

Kod: Zaznacz cały

voice service voip
 ip address trusted list
  ipv4 82.204.22.4
  ipv4 10.22.15.214
  ipv4 10.22.14.60
 mode border-element
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
 h323
 sip
  bind control source-interface GigabitEthernet0/0
  bind media source-interface GigabitEthernet0/0
  registrar server
  outbound-proxy ipv4:82.204.22.4
  early-offer forced
!
voice class codec 1
 codec preference 1 g729r8
 codec preference 2 g711alaw
 codec preference 3 g711ulaw
!
voice class h323 1
  h225 timeout tcp establish 2
  h225 timeout setup 2
  call preserve
!

interface GigabitEthernet0/0
 description EXT_SIP
 ip address 1.1.1.1 255.255.255.0
 ip access-group 111 in
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 duplex auto
 speed auto
 no cdp enable
!
interface GigabitEthernet0/1
 description TO_CUCM
 ip address 10.22.15.60 255.255.255.0
 no ip unreachables
 duplex auto
 speed auto
 no cdp enable
 h323-gateway voip interface
 h323-gateway voip bind srcaddr 10.22.15.60
!

dial-peer voice 101 voip
 description **IN*FROM*PSTN**
 session protocol sipv2
 session transport udp
 incoming called-number .
 dtmf-relay rtp-nte
 codec g711ulaw
!
dial-peer voice 102 voip
 description **FROM*PSTN*TO*CUCM**
 destination-pattern 1426222..
 session target ipv4:10.22.15.214 //CUCM IP
 voice-class h323 1
 dtmf-relay h245-alphanumeric
 codec g711ulaw
 no vad
Oto logi z połączenia:

Kod: Zaznacz cały

INVITE sip:142622207@195.110.3.12:5060 SIP/2.0
Via: SIP/2.0/UDP 82.204.22.4:5060;branch=z9hG4bK86250k203oshb75557s1.1
From: <sip:126204570@appserv1m.ngn.inetia.pl;user=phone>;tag=SDsc7od01-1905017209-1390827680215-
To: "142622207 142622207"<sip:142622207@xyz.net.pl>
Call-ID: SDsc7od01-105a48a9e8868d21afa4ba3b6a12ff15-aovtvc0
CSeq: 702879980 INVITE
Contact: <sip:126204570@82.204.22.4:5060;transport=udp>
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept: multipart/mixed,application/media_control+xml,application/sdp
Supported:
Max-Forwards: 19
Content-Type: application/sdp
Content-Length: 183

v=0
o=BroadWorks 83245026 1 IN IP4 82.204.22.4
s=-
c=IN IP4 82.204.22.4
t=0 0
m=audio 18556 RTP/AVP 18 8 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

*Jan 27 13:00:28.114: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=142622207, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.114: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.114: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.114: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=142622207, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Jan 27 13:00:28.114: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:28.118: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=126204570, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.118: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
*Jan 27 13:00:28.118: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jan 27 13:00:28.118: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=126204570, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.118: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
*Jan 27 13:00:28.118: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jan 27 13:00:28.118: //-1/D444708A8404/DPM/dpAssociateIncomingPeerCore:
   Calling Number=126204570, Called Number=142622207, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.118: //-1/D444708A8404/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=101
*Jan 27 13:00:28.118: //-1/D444708A8404/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchSafModulePlugin:
   dialstring=142622207, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchSafModulePlugin:
   dialstring=142622207, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=142622207, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=142622207, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=142622207, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=102
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=142622207, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=102
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=142622207, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
*Jan 27 13:00:28.122: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchSafModulePlugin:
   dialstring=142622207, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
*Jan 27 13:00:28.122: //-1/D444708A8404/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:28.126: //640/D444708A8404/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 82.204.22.4:5060;branch=z9hG4bK86250k203oshb75557s1.1
From: <sip:126204570@appserv1m.ngn.inetia.pl;user=phone>;tag=SDsc7od01-1905017209-1390827680215-
To: "142622207 142622207"<sip:142622207@xyz.net.pl>
Date: Mon, 27 Jan 2014 13:00:28 GMT
Call-ID: SDsc7od01-105a48a9e8868d21afa4ba3b6a12ff15-aovtvc0
CSeq: 702879980 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.3.3.M
Content-Length: 0


*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=126204570, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=126204570
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
   Result=NO_MATCH(-1)
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=142622207, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=102
*Jan 27 13:00:28.138: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Jan 27 13:00:28.142: //640/D444708A8404/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 82.204.22.4:5060;branch=z9hG4bK86250k203oshb75557s1.1
From: <sip:126204570@appserv1m.ngn.inetia.pl;user=phone>;tag=SDsc7od01-1905017209-1390827680215-
To: "142622207 142622207"<sip:142622207@xyz.net.pl>;tag=19A41A54-47
Date: Mon, 27 Jan 2014 13:00:28 GMT
Call-ID: SDsc7od01-105a48a9e8868d21afa4ba3b6a12ff15-aovtvc0
CSeq: 702879980 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:142622207@195.110.3.12:5060>
Supported: sdp-anat
Reason: Q.850;cause=1
Server: Cisco-SIPGateway/IOS-15.3.3.M
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250

v=0
o=CiscoSystemsSIP-GW-UserAgent 1750 1319 IN IP4 195.110.3.12
s=SIP Call
c=IN IP4 195.110.3.12
t=0 0
m=audio 16686 RTP/AVP 0 101
c=IN IP4 195.110.3.12
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=126204570, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=126204570
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
   Result=NO_MATCH(-1)
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=142622207, Peer Info Type=DIALPEER_INFO_SPEECH
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=142622207
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Jan 27 13:00:28.142: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=102
*Jan 27 13:00:40.162: //640/D444708A8404/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 82.204.22.4:5060;branch=z9hG4bK86250k203oshb75557s1.1
From: <sip:126204570@appserv1m.ngn.inetia.pl;user=phone>;tag=SDsc7od01-1905017209-1390827680215-
To: "142622207 142622207"<sip:142622207@xyz.net.pl>;tag=19A41A54-47
Date: Mon, 27 Jan 2014 13:00:28 GMT
Call-ID: SDsc7od01-105a48a9e8868d21afa4ba3b6a12ff15-aovtvc0
CSeq: 702879980 INVITE
Allow-Events: telephone-event
Warning: 399 195.110.3.12 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-15.3.3.M
Reason: Q.850;cause=1
Content-Length: 0
Proszę o pomoc.

lucky_luke
member
member
Posty: 28
Rejestracja: 18 sie 2010, 10:02

#2

#2 Post autor: lucky_luke »

Proponuje zrobić z obu stron trunk tego samego typu (np. SIP).
W przeciwnym wypadku prawdopodobnie będą "zjadane" dodatkowe zasoby na potrzeby konwersji SIP <> H.323, np. MTP

Awatar użytkownika
FrozenShadoow
wannabe
wannabe
Posty: 203
Rejestracja: 06 paź 2005, 23:06

#3

#3 Post autor: FrozenShadoow »

A jak masz SIP:
Early offer czy delayed
i H.323:
Slow czy Fast start?
Nie wyrażaj małej rzeczy w wielu słowach, lecz wielką w niewielu

Awatar użytkownika
krabu
wannabe
wannabe
Posty: 346
Rejestracja: 30 paź 2007, 11:17
Lokalizacja: Krakow

#4

#4 Post autor: krabu »

Witaj,

Na pierwszy rzut oka wydaje się, że masz coś nie tak po stronie CUBE - CUCM.
Do operatora odsyłasz SIP'em 404, dlatego, że pewnie po H.323 od CUCM dostajesz coś w stylu Unallocated number.

1) Wyłącz wszystkie logi na CUBE i prześlij sam debug z h.225 z próby połączenia (debug h225 q931)
2) Upewnij się, że twój CUCM jak dostanie na trunku h.323 numer 142622207 to wie co z nim zrobić, czyli potrzebujesz jakąś konwersja na numer lokalny - może nie wchodząc w głębsze sprawy po prostu brakuje takiej konwersji...
.be like a Lucky Luke

Awatar użytkownika
krabu
wannabe
wannabe
Posty: 346
Rejestracja: 30 paź 2007, 11:17
Lokalizacja: Krakow

#5

#5 Post autor: krabu »

FrozenShadoow pisze:A jak masz SIP:
Early offer czy delayed
i H.323:
Slow czy Fast start?
Widać wszystko po tym co przesłał.
.be like a Lucky Luke

ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

#6

#6 Post autor: ukaszq »

FrozenShadoow pisze:A jak masz SIP:
Early offer czy delayed
i H.323:
Slow czy Fast start?
Jeśli chodzi o H.323 mam Fast na CUBE domyslnie, natomiast w CUCM zaznaczona mam ta opcje.
SIP mam Early offer.

ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

#7

#7 Post autor: ukaszq »

krabu pisze:Witaj,

Na pierwszy rzut oka wydaje się, że masz coś nie tak po stronie CUBE - CUCM.
Do operatora odsyłasz SIP'em 404, dlatego, że pewnie po H.323 od CUCM dostajesz coś w stylu Unallocated number.

1) Wyłącz wszystkie logi na CUBE i prześlij sam debug z h.225 z próby połączenia (debug h225 q931)
2) Upewnij się, że twój CUCM jak dostanie na trunku h.323 numer 142622207 to wie co z nim zrobić, czyli potrzebujesz jakąś konwersja na numer lokalny - może nie wchodząc w głębsze sprawy po prostu brakuje takiej konwersji...
Jeśli chodzi o debug z h.225:

Kod: Zaznacz cały

*Jan 27 20:19:03.768: Changing to new event: CONNECT
h323chan_chn_connect: connecting to 10.22.15.214:1720

*Jan 27 20:19:03.768: h323chan_gw_conn: Created socket fd=2
*Jan 27 20:19:03.772: h323chan_gw_conn: connect in progress on fd=2h323chan_chn_connect: using fd=2, owner_data(ccb) 0x22D6B96C
changing from NONE state to CONNECTING state

*Jan 27 20:19:03.772: h323chan_chn_process_read_socket: fd=2 of type CONNECT_PENDING has data

*Jan 27 20:19:03.772: Changing to new event: CONNECTED
changing from CONNECTING state to CONNECTED state

*Jan 27 20:19:03.772: compose_TunnelledSignallingMessage_ciscoNo tunnelled content.
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x0055
Message Type           : 0x05: SETUP
 Bearer Capability: Length Of IE=3
 Data 8090A3
 Calling Party Number: Length Of IE=11
 Data 0080353136303930303836
 Called Party Number: Length Of IE=10
 Data 80313233363239323037
 User-User: Length Of IE=137
 Data 052080060008914A00042800B500001240013C05010000199DFC4486C711E3847BC0E4BC3513E200CD1D820007000AE29E3CCA801100199DFC4486C711E3847DC0E4BC3513E23402130000000C6013800B050001000AE29E3C4175801E400000060401004C60138012150001000AE29E3C4174000AE29E3C4175800100010001800180010010800180
Hex representation of the SETUP TPKT to send.: 080200550504038090A36C0B0080353136303930303836700A803132333632393230377E0089052080060008914A00042800B500001240013C05010000199DFC4486C711E3847BC0E4BC3513E200CD1D820007000AE29E3CCA801100199DFC4486C711E3847DC0E4BC3513E23402130000000C6013800B050001000AE29E3C4175801E400000060401004C60138012150001000AE29E3C4174000AE29E3C4175800100010001800180010010800180
h225SetupRequest: Q.931 SETUP sent from fd=2
*Jan 27 20:19:03.776: h323chan_chn_process_read_socket: fd=2 of type CONNECTED has data

*Jan 27 20:19:03.776: h323chan_recvdata: No Data on fd=2
PROCESS_READ: FAILED/NOT COMPLETE,rc 10, fd=2

*Jan 27 20:19:03.780: h323chan_chn_process_read_socket: fd=2 of type CONNECTED has data

Hex representation of the SETUP TPKT received: 080280555A080280817E0022052580060008914A000511001100199DFC4486C711E3847DC0E4BC3513E210800100

  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x8055
Message Type           : 0x5A: RELEASE_COMP
 Cause: Length Of IE=2
 Data 8081
 User-User: Length Of IE=34
 Data 052580060008914A000511001100199DFC4486C711E3847DC0E4BC3513E210800100h225ParseData: Q.931 RELEASE COMPLETE received on fd=2
*Jan 27 20:19:03.784: compose_TunnelledSignallingMessage_ciscoNo tunnelled content.
  Q931 Message IE Decodes
Protocol Discriminator : 0x08
CRV Length             : 2
CRV Value              : 0x0055
Message Type           : 0x5A: RELEASE_COMP
 Cause: Length Of IE=2
 Data 8081
 User-User: Length Of IE=34
 Data 052580060008914A000411001100199DFC4486C711E3847DC0E4BC3513E210800180
Hex representation of the RELEASE COMPLETE TPKT to send.: 080200555A080280817E0022052580060008914A000411001100199DFC4486C711E3847DC0E4BC3513E210800180
h225TerminateRequest: Q.931 RELEASE COMPLETE sent from fd=2. Call state changed to [Null].
*Jan 27 20:19:03.784: h323chan_close: TCP connection from fd=2 closed

Awatar użytkownika
krabu
wannabe
wannabe
Posty: 346
Rejestracja: 30 paź 2007, 11:17
Lokalizacja: Krakow

#8

#8 Post autor: krabu »

Witaj,

Widać więc, że wysyłasz do CUCM SETUP a CUCM na ten SETUP odpowiada Ci od razu RELEASE_COMP z Cause Code'em, który przypomina mi unallocated number - nie ma przy sobie teraz tabelki z Cause Codami. Tak wiec wygląda, że sygnalizacja dochodzi do CUCM, a ten nie wie gdzie ma to połączenie skierować.

1) Po stronie CUCM jak konfigurowałeś ten h.323 gateway to zrobiłeś jakąś transformacje, aby numer przychodzący (called) przekierować na jakiś numer wewnętrzny czy też cokolwiek innego, na co chcesz aby takie połączenie spadało?

2) Czy przy konfiguracji tego gateway'a dla inbound calls nadałeś mu odpowiedni CSS, tak by widział destination?
.be like a Lucky Luke

ukaszq
wannabe
wannabe
Posty: 149
Rejestracja: 12 cze 2011, 21:53

#9

#9 Post autor: ukaszq »

Witam,

Znalazłem błąd zgodnie z Waszymi sugestiami. Problem leżał w CUCM w translations pattern. Miałem nieprawidłowo ustawioną maskę. Dziękuję za pomoc! :)

ODPOWIEDZ