SIP TRUNK
Re: SIP TRUNK
After SIP TG creation you need to make shutdown.
F.e. after command "killall sipmotor" you must have incident about SIP TG out of services, and back in services. If this incident absent - you need shutdown.
F.e. after command "killall sipmotor" you must have incident about SIP TG out of services, and back in services. If this incident absent - you need shutdown.
Re: SIP TRUNK
In TG you have number compatible with -1 and number of digits to send 0 (!). Try to use discriminator or at first manage number of digits to send 4.
-
root
Re: SIP TRUNK
The config does not match to the provided trace, is the routing number 6 also linkedtalkhalidi wrote:thanks ,
i have attached the configuration of OXE. please note that the IP address for OXE is 192.168.254.240 , AVAYA 192.168.254.200.
am stuck since one week and couldnot find clue for my proble. appreciate your help guys.
to network 2? From my point of view your config looks good, but the trace show that
the OXE send the INVITE to the OXE itself instead of AVAYA IP which is defined in the
SIP ext GW 2. I don't know why ;-(
Did you tried with QSIG-GF instead of ABCF in the routing table?
Could you provide an call handling trace:
trc i
tuner +cpl +cpu +at hybrid=on
actdbg sip=on abcf=on
mtracer -a
-
talkhalidi
Re: SIP TRUNK
please find the attached traces . this is faced when try to call from Avaya to Alcatel.
-
talkhalidi
Re: SIP TRUNK
please find attached traces, forgot to attach it in the prevoius post.
any luck
any luck
You do not have the required permissions to view the files attached to this post.
-
cavagnaro
Re: SIP TRUNK
and what is cm-resubscribe@192.168.254.200?? In OXE you have to use numeric format to call extensions. Unless this is a softphone like xlite or sjphone?
-
root
Re: SIP TRUNK
I don't know what the trace have to do with the previous discused problem.talkhalidi wrote:please find attached traces, forgot to attach it in the prevoius post.
any luck
The trace show that a NOTIFY from AVAYA (see the UA header) is forwarded
by the OXE to the AVAYA due to the URI domain part. OXE forward to UDP,
but AVAYA listen only on TCP this is not conform to RFC 3261 which says
that a UA must also listen for UDP and TCP.
Your problems seems to be deeper, you should consult an OXE expert
which has access to the system to solve your problems.
-
almatel
Re: SIP TRUNK
Hi, all
may be I am not an expert in OXE, but i did many sip trunk configuration and all of them is working good ,so let me ask u first to change the Public Network COS of sip TRGRP from 31 to any other value ( 5 ) for example and number compatible with :1 for example and inside the Discr 1 create a 57 as a calling NO. with any area, then make the COS 5 a- access to this area =1, b- access to TRGRP 2 =1 ., then make a call.
regards
may be I am not an expert in OXE, but i did many sip trunk configuration and all of them is working good ,so let me ask u first to change the Public Network COS of sip TRGRP from 31 to any other value ( 5 ) for example and number compatible with :1 for example and inside the Discr 1 create a 57 as a calling NO. with any area, then make the COS 5 a- access to this area =1, b- access to TRGRP 2 =1 ., then make a call.
regards
-
root
Re: SIP TRUNK
but if it's is a problem of rigths then the OXE never send out an INVITE the callalmatel wrote:Hi, all
may be I am not an expert in OXE, but i did many sip trunk configuration and all of them is working good ,so let me ask u first to change the Public Network COS of sip TRGRP from 31 to any other value ( 5 ) for example and number compatible with :1 for example and inside the Discr 1 create a 57 as a calling NO. with any area, then make the COS 5 a- access to this area =1, b- access to TRGRP 2 =1 ., then make a call.
regards
is normaly rejected before, am I right?

