Confrence Omnitouch 4135 IP calling to extensions and outbo

mejust
Member
Posts: 76
Joined: 18 Jan 2008 14:14
Location: Luanda

Confrence Omnitouch 4135 IP calling to extensions and outbo

Post by mejust »

Hello

Im working for the first time with R11 and for the first time I installed a Conference Onitouch 4135 IP.
Im able to call from any extension to the 4135 IP but no the other way around.
Every time I call to an extension I get an 480 Temporarily Unavailable.
If I configure an extension in the entity where it says the 1st Night routing every time I call an extension, the call overflows to the extension configures in the entity, same thing happens when I call to an external number.

Any Suggestions

Delivery software version : k1.400 ;
Patch version : 30 ;
Dynamic patch version : f ;

MAO software version : K1.400.23 ;
Software Version Name : R11.0 ;
System Country : PORTUGAL ( 8);
System for Large Config : no;

Thanks in advanced

The question is why does the 4135 Ip overflow to the Entity ?
I think the problem is that the alcatel system doesn't recolonize the extension that Im calling that´s why there is an overflow to the entity.
You do not have the required permissions to view the files attached to this post.
mejust
Member
Posts: 76
Joined: 18 Jan 2008 14:14
Location: Luanda

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by mejust »

Update

I did a trance on the PBX and the 4135 isn't sending the extension number " no Called Number "

| (074782:000134) Concatenated-Physical-Event :
| long: 195 desti: 0 source: 0 cryst: 19 cpl: 0 us: 0 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 68
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=2) a0 90 -> T2 : No B channel
| IE:[1c] FACILITY (l=106)
| [91] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [80] Source Entity (l=1) End_PTNX
| [82] Destination Entity (l=1) End_PTNX
| [8b] Interpretation APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=16):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=4) '4135'
| [a1] INVOKE (l=29):
| Invoke Ident. : 2ef5 (12021)
| OP: ECMA RO_QSIG_LEG_INFORMATION2 (21)
| [30] Sequence (l=17)
| [02] Integer (l=1) 01
| [0a] Enumerated (l=1) 00
| [a1] Context specific (l=9)
| [a0] Context specific (l=7)
| [80] Context specific (l=5) 32 34 30 30 31
| [a1] INVOKE (l=43):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=30)
| [80] Feature identifier (l=5) 46 04 70 1f 20
| [82] Cug (l=1) 00
| [ab] Sequence of Project data (l=18)
| [30] Sequence (l=16)
| OP :RO_CLASSMARKS_SUPPLEMENTARY_INFO_1 (134623571)
| [30] Sequence (l=10)
| [80] Trunk group feature (l=5) 06 00 00 20 04
| [83] Current entity (l=1) 01
| IE:[6c] CALLING_NUMBER (l=7) -> 09 81 Num : 24000
| IE:[70] CALLED_NUMBER (l=1) -> 80 Num :
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> EXTENSION (1)
| [9f] Non-locking shift. codeset : 7
| IE:[06] EI_IP_PAYLOADS (l=3) : (COMP/ECE/VAD)
| -> G729/0/0 G711a/0/0 G722_64/0/0
| [97] Locking shift. codeset : 7
| IE:[0a] EI_RTP_INFO (l=30)
| -> stop_packet=0 stop_rtp=0 h323=0 wc=1 rf=0 udp=1 rqm=0
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=101
| -> Port RTP = 4004, IPv4 : 192. 168. 92. 100.
| -> Port RTCP SR = 4005, IPv4 : 192. 168. 92. 100.
| -> Port RTCP RR = 4005, IPv4 : 192. 168. 92. 100.
| -> Port Fax = 0, IPv4 : 0. 0. 0. 0.
|______________________________________________________________________________

Meaning the pbx doesn´t know where to send the call . Automatically it overflows to the entity .
mejust
Member
Posts: 76
Joined: 18 Jan 2008 14:14
Location: Luanda

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by mejust »

Really Nobody can help me ?
User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4058
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by tot3nkopf »

4135 is configured as SIP extension or SIP device? Did you looked at the technical coms regarding 4135 installation and configuration?
mejust
Member
Posts: 76
Joined: 18 Jan 2008 14:14
Location: Luanda

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by mejust »

Hello

I configured the 4135 as a SIP DEVICE .
I followed the following technical com : "TC1252en-Ed02 INSTALLATION, UPGRADE AND TROUBLESHOOTING ON OMNITOUCH 4135 IP", though there isnt much info based on configuration between OXE and 4135 IP.
Not even the Manual for R11 says anything about it.


tot3nkopf wrote:4135 is configured as SIP extension or SIP device? Did you looked at the technical coms regarding 4135 installation and configuration?
You do not have the required permissions to view the files attached to this post.
User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4058
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by tot3nkopf »

SIP/2.0 480 Temporarily not available
T2 : No B channel
Is 24000 in the same node?
Do you have compressors resources in the domain 4135 is configured in?
Intra/extra domain compression is?
mejust
Member
Posts: 76
Joined: 18 Jan 2008 14:14
Location: Luanda

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by mejust »

Yes 24000 is in the same node

All the phones are in the same domain 0

Yes I have compressors resources in the domain :

Node Number (reserved) : 1 |
| Shelf Address : 2 |
| Board Address : 0 |
| |
| Interface Type + GD3 |
| Virtual board + NO |
| Usage State + Busy |
| Operational State + Enabled |
| Main/Standby State + Main (Master) |
| Country + Default |
| Incidents Teleservice + YES |
| Daughter Board + None |
| Nb of Compressors for IP Devices : 13 |
| N part conferences configuration + No conference |
| N part conference type + Add-on |
| Zone Paging + YES |
| Use of volume in system + YES |
| Local volume (dB) : 0 |
| AFU daughter board + YES |
| AFU Directory Number : -------- |
| |
+--------------------------------------------------------------------+
Intra Domain Coding Algorithm + With Compression |
| Extra Domain Coding Algorithm + With Compression |


Calling to 4135 from TDM and IP Touch works .

If I configure an extension in the entity area where it says first night routing, any call I make on the 4135 even if it´s a extension that doesn't exist the extension rings (configured in the entity) .

Meaning That the Alcatel system isn´t recognizing the extension that Im calling so it sends the call to the entity .
I if delete the extension configured in the Identity I get the not available message on the 4135 and on the PBX I receive "26/02/14 14:26:14 000001M|019/00/0/001|=3:1307x003=MCDU in distri tab entity 1, col Night , line 4 incorrect or missing" message.




tot3nkopf wrote:
SIP/2.0 480 Temporarily not available
T2 : No B channel
Is 24000 in the same node?
Do you have compressors resources in the domain 4135 is configured in?
Intra/extra domain compression is?
haroun
Senior Member
Posts: 1464
Joined: 29 Mar 2010 11:09

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by haroun »

dialling plan in the 4135 checked may be your phone is changing numbering,240002 does it exist in your pbx as sip estension -user- or sip devise -under translator?
haroun
Senior Member
Posts: 1464
Joined: 29 Mar 2010 11:09

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by haroun »

check also external sip gateway for 24002 if it is sip device -routing , associated network , associeted sip exgw and so on
mejust
Member
Posts: 76
Joined: 18 Jan 2008 14:14
Location: Luanda

Re: Confrence Omnitouch 4135 IP calling to extensions and o

Post by mejust »

I solved my Problem
I configured the 4135 as a SIP EXTENSION instead of a SIP DEVICE and now it works fine.
I'm able to call both ways .

TC1252en-Ed02 tells you to configure as a SIP Device, maybe in R9 and R10 it works, but on R11 you have to configure this as a SIP Extension

Thks Guys for trying to help me.
Post Reply

Return to “SIP”