Latest SVN - MTP2 alignment failing
Dear all, im trying to build up latest SVN with ciscosm. But mtp2 alignment failing. Below is the log shows on yate log. Can any one please shed some light on this. I have good working link/linkset on quite older svn.
thanks for any help
Nik.
<linkset1:WARN> Received SLTM ITU,xx-xx-xx:xx-xx-xx:0 (xxxx:xxx:0) on 0 with 4 bytes
<slt0:INFO> Received PDU message: Data Indication
Data dump: 00 00 80 00 00 01 00 00 00 11 00 00 00 00 00 0b 81 58 02 01 01 11 40 01 02 03 04
Protocol Type: 1
Message ID: 0
Channel ID: 0
<linkset1:WARN> Received SLTM ITU,xx-xx-xx:xx-xx-xx:0 (xxxx:xxx:0) on 0 with 4 bytes
<linkset1:NOTE> Cycling not in service link 0 'slt0' [0x926fc58]
<slt0:INFO> Sending PDU message: Disconnect Request
Data dump: 00 00 80 00 00 01 00 00 00 0a 00 00 00 00 00 00
Protocol Type: 1
Message ID: 0
Channel ID: 0
<slt0:NOTE> Link inhibition changed 0x01 -> 0x01 [0x9285dd8]
<slt0:INFO> Sending PDU message: Connect Request
Data dump: 00 00 80 00 00 01 00 01 00 06 00 00 00 00 00 04 00 00 00 03
Protocol Type: 1
Message ID: 1
Channel ID: 0
Message Description: Emergency alignment
<slt0:INFO> Received PDU message: Disconnect confirmation
Data dump: 00 00 80 00 00 01 00 01 00 0b 00 00 00 00 00 04 00 00 00 03
Protocol Type: 1
Message ID: 1
Channel ID: 0
Error: Not Handled
<slt0:INFO> Sending PDU message: Connect Request
Data dump: 00 00 80 00 00 01 00 01 00 06 00 00 00 00 00 04 00 00 00 03
Protocol Type: 1
Message ID: 1
Channel ID: 0
Message Description: Emergency alignment
<slt0:INFO> Received PDU message: Link state controller indication
Data dump: 00 00 80 00 00 01 00 01 00 22 00 00 00 00 00 08 00 00 00 07 00 00 00 00
Protocol Type: 1
Message ID: 1
Channel ID: 0
Message Description: We have aligned the link
Error: No error
<slt0:INFO> Received PDU message: Connect Confirmation
Data dump: 00 00 80 00 00 01 00 01 00 07 00 00 00 00 00 04 00 00 00 03
Protocol Type: 1
Message ID: 1
Channel ID: 0
Message Description: Emergency alignment
<slt0:INFO> Received PDU message: Data Indication
Data dump: 00 00 80 00 00 01 00 00 00 11 00 00 00 00 00 0b 81 58 02 01 01 11 40 01 02 03 04
Protocol Type: 1
Message ID: 0
Channel ID: 0
<linkset1:WARN> Received SLTM ITU,xx-xx-xx:xx-xx-xx:0 (xxxx:xxx:0) on 0 with 4 bytes
<slt0:INFO> Received PDU message: Data Indication
Data dump: 00 00 80 00 00 01 00 00 00 11 00 00 00 00 00 0b 81 58 02 01 01 11 40 01 02 03 04
Protocol Type: 1
Message ID: 0
Channel ID: 0
<linkset1:WARN> Received SLTM ITU,xx-xx-xx:xx-xx-xx:0 (xxxx:xxx:0) on 0 with 4 bytes
<linkset1:NOTE> Cycling not in service link 0 'slt0' [0x926fc58]
<slt0:INFO> Sending PDU message: Disconnect Request
Data dump: 00 00 80 00 00 01 00 00 00 0a 00 00 00 00 00 00
Protocol Type: 1
Message ID: 0
Channel ID: 0
<slt0:NOTE> Link inhibition changed 0x01 -> 0x01 [0x9285dd8]
<slt0:INFO> Sending PDU message: Connect Request
Data dump: 00 00 80 00 00 01 00 01 00 06 00 00 00 00 00 04 00 00 00 03
Protocol Type: 1
Message ID: 1
Channel ID: 0
Cisco shows the below log,
*May 1 17:09:46.024: itu2IAC_Start chnl=0 MTP2IAC_IDLE
*May 1 17:09:46.032: itu2IAC_Emergency chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:46.048: itu2IAC_Rcvd_SIOS chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:46.068: itu2IAC_Rcvd_SIOS chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:47.216: itu2IAC_Rcvd_SIOS chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:47.220: itu2IAC_Rcvd_SIO chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:47.220: itu2IAC_Rcvd_SIO chnl=0 MTP2IAC_ALIGNED
*May 1 17:09:47.220: itu2IAC_Rcvd_SIE chnl=0 MTP2IAC_ALIGNED
*May 1 17:09:47.220: itu2IAC_Rcvd_SIE chnl=0 MTP2IAC_PROVING
*May 1 17:09:47.728: itu2IAC_T4_TMO chnl=0 MTP2IAC_PROVING
*May 1 17:09:57.756: itu2IAC_Start chnl=0 MTP2IAC_IDLE
*May 1 17:09:57.760: itu2IAC_Emergency chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:57.780: itu2IAC_Rcvd_SIOS chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:57.820: itu2IAC_Rcvd_SIOS chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:59.216: itu2IAC_Rcvd_SIOS chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:59.216: itu2IAC_Rcvd_SIO chnl=0 MTP2IAC_NOT_ALIGNED
*May 1 17:09:59.220: itu2IAC_Rcvd_SIE chnl=0 MTP2IAC_ALIGNED
*May 1 17:09:59.220: itu2IAC_Rcvd_SIE chnl=0 MTP2IAC_PROVING
*May 1 17:09:59.728: itu2IAC_T4_TMO chnl=0 MTP2IAC_PROVING
Re: Debug yate
Hi. I know about this tool. but here you also can't set debug on same ip address or username. On 30.04.2011, at 21:20, Tengo wrote: > Dmitriy Abramov wrote: >> Yate have very nice tool for debug - machine mode. > > Another debugging tool is msgsniff: > http://yate.null.ro/pmwiki/index.php?n=Main.Msgsniff > > One could also write a simple external module, which would install message or "watch" handlers and dump messages based on some criteria (filter).
Re: DB schema
Hi, We don't offer a schema because you normally adapt the queries to your project. This are the fields for some of the tables: CREATE TABLE cdr ( "time" timestamp without time zone, chan text, address text, direction text, billid text, caller text, "called" text, duration time without time zone, billtime time without time zone, ringtime time without time zone, status text, reason text, ended boolean ) CREATE TABLE accounts ( enabled boolean, protocol text, username text, description text, "interval" text, formats text, authname text, "password" text, "number" text, server text, gatekeeper text, "domain" text, registrar text, outbound text, localaddress text, modified boolean, account text, id serial NOT NULL, status text ) CREATE TABLE lines (i think this appears as users in the configuration file) ( "password" text, first_name text, last_name text, address text, inuse integer, "location" text, expires timestamp without time zone, line text ) Regards, Monica Tepelus Виталий Сергеевич wrote: > Hi, > > Hello, tell me where I can find the postgresql database schema for the > Register module?
Re: Latest SVN - MTP2 alignment failing
Hello, Nik! In order to be standards compliant Yate now refuses to validate links that fail ITU Q.707 Link Maintenance procedure. A WARN regarding the SLTM indicates a configuration mismatch. You probably have wrong (or none at all) point codes configured for the linkset. In each linkset (type=ss7-mtp3) section you must have: - one local= line - one adjacent= line - zero or more route= lines whose point codes must be different from adjacent and local - one netind2pctype= line - zero or one netindicator= line Paul On Sunday 01 May 2011 09:16:50 pm Nik Pakar wrote: > Dear all, im trying to build up latest SVN with ciscosm. But mtp2 alignment > failing. Below is the log shows on yate log. Can any one please shed some > light on this. I have good working link/linkset on quite older svn. > > thanks for any help > Nik. > > > <linkset1:WARN> Received SLTM ITU,xx-xx-xx:xx-xx-xx:0 (xxxx:xxx:0) on 0 > with 4 bytes > [...]
SDPMedia::update() question
Hi,
I meet a problem with SDPMedia::update() in the context of SIP reInvite. I don't understand what's the reason of 'm_formats = m_format;' here. This will bring on mediaChanged(*m) func will be called in the func 'bool SDPSession::setMedia(ObjList* media)' as m_formats changed when reInvite occurs.
// Update members from a dispatched "chan.rtp" message
void SDPMedia::update(const NamedList& msg, bool pickFormat)
{
DDebug(DebugAll,"SDPMedia::update('%s',%s) [%p]",
msg.c_str(),String::boolText(pickFormat),this);
m_id = msg.getValue("rtpid",m_id);
m_lPort = msg.getValue("localport",m_lPort);
if (pickFormat) {
const char* format = msg.getValue("format");
if (format) {
m_format = format;
if ((m_formats != m_format) && (msg.getIntValue("remoteport") > 0)) {
Debug(DebugNote,"Choosing started '%s' format '%s' [%p]",
c_str(),format,this);
m_formats = m_format;
}
}
}
}
Regards,
Bian
About yate video support
I see http://yate.null.ro/pmwiki/index.php?n=Main.SIPClient it's write "Video - soon to be implemented"
but Such a long time it's also write "soon"....
we wait a long long time.....
When will this be achieved?
http://yate.null.ro/archive/?action=show_msg&actionargs%5B%5D=20&actionargs%5B%5D=72
some one has say about this at Tue, 15 May 2007 12:36:17 +0200
Has in the past 3 years,no body can achieve it????
--
Jhone Wead 体验网易邮箱2G超大附件,轻松发优质大电影、大照片,提速3倍!
体验网易邮箱2G超大附件,轻松发优质大电影、大照片,提速3倍!
About yate video support
I see http://yate.null.ro/pmwiki/index.php?n=Main.SIPClient it's write "Video - soon to be implemented"
but Such a long time it's also write "soon"....
we wait a long long time.....
When will this be achieved?
http://yate.null.ro/archive/?action=show_msg&actionargs%5B%5D=20&actionargs%5B%5D=72
some one has say about this at Tue, 15 May 2007 12:36:17 +0200
Has in the past 3 years,no body can achieve it????
--
Jhone Wead
Supervisor: killing unresponsive child
Hi all
I have problem with stability of latest Yate 3.3.2
Symptoms: once or twice a day Yate restarts (kills all connections and restarts engine). First problem occours usually in similar time of day between 08:00 and 09:00 AM, that's the time when most users go to work and log to SIP server. Server load that time is about 0.3-0.6, CPU usage less than 10%, about 30 active SIP connections (60 channels), about 1000 SIP users online.
Error messages:
Supervisor: killing unresponsive child (most often)
<FAIL> Peer ID failed - timeout on call endpoint mutex owned by 'YSIP EndPoint'!
I use Yate only as SIP server, no voip hardware involved.
Loaded modules:
Loaded module YRTP
Loaded module Call Generator
Loaded module MsgSniffer
Loaded module RManager
Loaded module ExtModule
Loaded module CdrBuild
Loaded module SIP Channel
Loaded module CdrFile
Loaded module RegexRoute
Loaded module Late Router
Loaded module Register for database
Loaded module Accounts from file
Loaded module MySQL based on 5.0.51a
Loaded module CallCounters
Loaded module Signalling Channel
Loaded module Registration from file
Loaded module SIP Features
Could anyone give me advice on what's going on and how to debug/correct this problem? It really repeats every day at least one time
Kind Regards,
Mateusz
RSS Feed