Hi everyone,
I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI
(Megalink) circuit and having some trouble getting it to handshake.
Thanks for any help or suggestions to diagnose this problem.
The problem is that Asterisk has trouble bringing up the link. I see
the following lines every couple of minutes:
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
h87*CLI> pri show spans
PRI span 1/0: Provisioned, Up, Active
h87*CLI> pri show spans
PRI span 1/0: Provisioned, Up, Active
== Primary D-Channel on span 1 down
[Oct 1 17:52:49] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No
D-channels available! Using Primary channel 24 as D-channel anyway!
h87*CLI> pri show spans
PRI span 1/0: Provisioned, Down, Active
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
h87*CLI> pri show spans
PRI span 1/0: Provisioned, Up, Active
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 down
[Oct 1 17:55:20] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No
D-channels available! Using Primary channel 24 as D-channel anyway!
h87*CLI> pri show spans
PRI span 1/0: Provisioned, Down, Active
Of course I cannot dial out:
-- Executing [2446411 at default:1] NoOp("SIP/368-081f51d8",
"Dial Time
of Day via PRI") in new stack
-- Executing [2446411 at default:2] Dial("SIP/368-081f51d8",
"ZAP/3|2446411|30|Tt") in new stack
[Oct 1 18:01:27] WARNING[13623]: app_dial.c:1106 dial_exec_full: Unable
to create channel of type 'ZAP' (cause 0 - Unknown)
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [2446411 at default :3]
Congestion("SIP/368-081f51d8", "")
in new stack
== Spawn extension (default, 2446411, 3) exited non-zero on
'SIP/368-081f51d8'
If I turn on pri debugging, I see lots of:
h87*CLI> pri debug span 1
Enabled debugging on span 1
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Periodically I see:
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:664 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
== Primary D-Channel on span 1 up
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:664 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
== Primary D-Channel on span 1 up
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:664 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
== Primary D-Channel on span 1 up
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:664 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
== Primary D-Channel on span 1 up
> Protocol Discriminator: Q.931 (8) len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> [18 03 a9 83 88]
> Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0
Exclusive Dchan: 0
> ChanSel: Reserved
> Ext: 1 Coding: 0 Number Specified Channel
Type: 3
> Ext: 1 Channel: 8 ]
> [79 01 80]
> Restart Indentifier (len= 3) [ Ext: 1 Spare: 0 Resetting Indicated
Channel (0) ]
-- Timeout occured, restarting PRI
q921.c:356 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
Sending Set Asynchronous Balanced Mode Extended
q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
== Primary D-Channel on span 1 down
[Oct 1 18:04:09] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No
D-channels available! Using Primary channel 24 as D-channel anyway!
Sending Set Asynchronous Balanced Mode Extended
Sending Set Asynchronous Balanced Mode Extended
Any help is greatly appreciated!
Thanks,
Alvin
The only time I have had this problem is when there was a version mismatch between Zaptel and Asterisk. Once I resolved that issue (latest asterisk + latest zaptel + reasonably recent wanpipe) everything worked for me. Alvin Austin wrote:> Hi everyone, > > I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI > (Megalink) circuit and having some trouble getting it to handshake. > Thanks for any help or suggestions to diagnose this problem. > > > The problem is that Asterisk has trouble bringing up the link. I see > the following lines every couple of minutes: > > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Up, Active > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Up, Active > == Primary D-Channel on span 1 down > [Oct 1 17:52:49] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Down, Active > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Up, Active > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 down > [Oct 1 17:55:20] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Down, Active > > Of course I cannot dial out: > > -- Executing [2446411 at default:1] NoOp("SIP/368-081f51d8", "Dial Time > of Day via PRI") in new stack > -- Executing [2446411 at default:2] Dial("SIP/368-081f51d8", > "ZAP/3|2446411|30|Tt") in new stack > [Oct 1 18:01:27] WARNING[13623]: app_dial.c:1106 dial_exec_full: Unable > to create channel of type 'ZAP' (cause 0 - Unknown) > == Everyone is busy/congested at this time (1:0/0/1) > -- Executing [2446411 at default :3] Congestion("SIP/368-081f51d8", "") > in new stack > == Spawn extension (default, 2446411, 3) exited non-zero on > 'SIP/368-081f51d8' > > If I turn on pri debugging, I see lots of: > > h87*CLI> pri debug span 1 > Enabled debugging on span 1 > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > > Periodically I see: > > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > > Protocol Discriminator: Q.931 (8) len=13 > > Call Ref: len= 2 (reference 0/0x0) (Originator) > > Message type: RESTART (70) > > [18 03 a9 83 88] > > Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 > Exclusive Dchan: 0 > > ChanSel: Reserved > > Ext: 1 Coding: 0 Number Specified Channel > Type: 3 > > Ext: 1 Channel: 8 ] > > [79 01 80] > > Restart Indentifier (len= 3) [ Ext: 1 Spare: 0 Resetting Indicated > Channel (0) ] > -- Timeout occured, restarting PRI > q921.c:356 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED > Sending Set Asynchronous Balanced Mode Extended > q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH > == Primary D-Channel on span 1 down > [Oct 1 18:04:09] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > > > Any help is greatly appreciated! > > Thanks, > Alvin > > > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
As soon as I saw channel '24 as D-channel' my guess is that the card/config is set up as T1, when you need E1. PaulH On Mon, 2007-10-01 at 18:23 -0600, Alvin Austin wrote:> Hi everyone, > > I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI > (Megalink) circuit and having some trouble getting it to handshake. > Thanks for any help or suggestions to diagnose this problem. > > > The problem is that Asterisk has trouble bringing up the link. I see > the following lines every couple of minutes: > > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Up, Active > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Up, Active > == Primary D-Channel on span 1 down > [Oct 1 17:52:49] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Down, Active > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Up, Active > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 down > [Oct 1 17:55:20] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > h87*CLI> pri show spans > PRI span 1/0: Provisioned, Down, Active > > Of course I cannot dial out: > > -- Executing [2446411 at default:1] NoOp("SIP/368-081f51d8", "Dial Time > of Day via PRI") in new stack > -- Executing [2446411 at default:2] Dial("SIP/368-081f51d8", > "ZAP/3|2446411|30|Tt") in new stack > [Oct 1 18:01:27] WARNING[13623]: app_dial.c:1106 dial_exec_full: Unable > to create channel of type 'ZAP' (cause 0 - Unknown) > == Everyone is busy/congested at this time (1:0/0/1) > -- Executing [2446411 at default :3] Congestion("SIP/368-081f51d8", "") > in new stack > == Spawn extension (default, 2446411, 3) exited non-zero on > 'SIP/368-081f51d8' > > If I turn on pri debugging, I see lots of: > > h87*CLI> pri debug span 1 > Enabled debugging on span 1 > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > > Periodically I see: > > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > -- Got SABME from network peer. > Sending Unnumbered Acknowledgement > q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is > Q921_LINK_CONNECTION_ESTABLISHED > == Primary D-Channel on span 1 up > > Protocol Discriminator: Q.931 (8) len=13 > > Call Ref: len= 2 (reference 0/0x0) (Originator) > > Message type: RESTART (70) > > [18 03 a9 83 88] > > Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0 > Exclusive Dchan: 0 > > ChanSel: Reserved > > Ext: 1 Coding: 0 Number Specified Channel > Type: 3 > > Ext: 1 Channel: 8 ] > > [79 01 80] > > Restart Indentifier (len= 3) [ Ext: 1 Spare: 0 Resetting Indicated > Channel (0) ] > -- Timeout occured, restarting PRI > q921.c:356 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED > Sending Set Asynchronous Balanced Mode Extended > q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH > == Primary D-Channel on span 1 down > [Oct 1 18:04:09] WARNING[13164]: chan_zap.c:2393 pri_find_dchan: No > D-channels available! Using Primary channel 24 as D-channel anyway! > Sending Set Asynchronous Balanced Mode Extended > Sending Set Asynchronous Balanced Mode Extended > > > Any help is greatly appreciated! > > Thanks, > Alvin > > > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
I've recompiled with the latest svn sources for zaptel, libpri, and
Asterisk. Wanpipe is 3.3.0.p4.
Switched the T1 cable. Same result.
(It's a Sasktel Megalink T1/PRI circuit)
CLI> shows:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 down
[Oct 1 20:15:19] WARNING[7120]: chan_zap.c:2393 pri_find_dchan: No
D-channels available! Using Primary channel 24 as D-channel anyway!
== Primary D-Channel on span 1 up
== Primary D-Channel on span 1 up
CLI> pri show spans
alternates between:
PRI span 1/0: Provisioned, Down, Active (most of the time)
and:
PRI span 1/0: Provisioned, Up, Active (during its retry sequence -
below)
with debugging enabled: CLI> pri debug span 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sending Set Asynchronous Balanced Mode Extended
[..]
Sending Set Asynchronous Balanced Mode Extended
-- Got SABME from network peer.
Sending Unnumbered Acknowledgement
q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:664 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
== Primary D-Channel on span 1 up
[above paragraph repeated 7 more times]
> Protocol Discriminator: Q.931 (8) len=13
> Call Ref: len= 2 (reference 0/0x0) (Originator)
> Message type: RESTART (70)
> [18 03 a9 83 82]
> Channel ID (len= 5) [ Ext: 1 IntID: Implicit PRI Spare: 0
Exclusive Dchan: 0
> ChanSel: Reserved
> Ext: 1 Coding: 0 Number Specified Channel
Type: 3
> Ext: 1 Channel: 2 ]
> [79 01 80]
> Restart Indentifier (len= 3) [ Ext: 1 Spare: 0 Resetting Indicated
Channel (0) ]
-- Timeout occured, restarting PRI
q921.c:356 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
Sending Set Asynchronous Balanced Mode Extended
q921.c:150 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
== Primary D-Channel on span 1 down
[Oct 1 20:30:49] WARNING[7003]: chan_zap.c:2393 pri_find_dchan: No
D-channels available! Using Primary channel 24 as D-channel anyway!
Sending Set Asynchronous Balanced Mode Extended
[..]
Sending Set Asynchronous Balanced Mode Extended
# wanrouter status
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Devices currently active:
wanpipe1
Wanpipe Config:
Device name | Protocol Map | Adapter | IRQ | Slot/IO | If's | CLK |
Baud rate |
wanpipe1 | N/A | A101/1D/A102/2D/4/4D/8| 16 | 4 |
1 | EXT | 0 |
Wanrouter Status:
Device name | Protocol | Station | Status |
wanpipe1 | AFT HDLC | N/A | Connected |
File /etc/zaptel.conf is:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- do not hand edit
# Zaptel Channels Configurations (zaptel.conf)
#
loadzone=us
defaultzone=us
#Sangoma A101 port 1 [slot:4 bus:41 span: 1]
span=1,0,0,esf,b8zs
bchan=1-23
dchan=24
File /etc/asterisk/zapata.conf is:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
;Zaptel Channels Configurations (zapata.conf)
;
;For detailed zapata options, view /etc/asterisk/zapata.conf.orig
[trunkgroups]
[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
;Sangoma A101 port 1 [slot:4 bus:41 span: 1]
; I also tried: switchtype=national
switchtype=dms100
context=pstn-pri
group=1
signalling=pri_cpe
channel => 1-23
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Still struggling; thanks for any help and ideas.
Alvin
Thanks for all of the good suggestions. I've been able to get things working. I had been trying to use zaptel svn in order to get past error messages with compiling ztdummy.ko for the 2.6.22 kernel (http://bugs.digium.com/view.php?id=10426 which has been apparently been solved in svn). Too bleeding edge, I guess. I reverted back to a tried-and-true kernel (2.6.17), and then compiled the stable 1.4 zaptel/libpri/asterisk/wanpipe versions, and things are happy now. Regards to all, Alvin Stephen Bosch wrote: > Alvin Austin wrote: > >> I've recompiled with the latest svn sources for zaptel, libpri, and Asterisk. Wanpipe is 3.3.0.p4. >> Switched the T1 cable. Same result. >> > > Hmn -- when you recompiled, did you > > 1. clean out all the source directories? > 2. remove the binaries? > 3. recompile in the right order? > > I'm not sure using SVN is a good idea here. It should work with "stable" ;) > > Has the PRI been tested with test equipment? We should make sure there is a D channel before assuming misconfiguration. I don't think we can do even a loopback test if there is no D channel... > > -Stephen- > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
On Mon, Oct 1, 2007 at 7:23 PM, Alvin Austin <aan at crlogic.com> wrote:> Hi everyone,Hi Alvin,> I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI > (Megalink) circuit and having some trouble getting it to handshake. > Thanks for any help or suggestions to diagnose this problem.I was trying to figure out on that issue and find a something reasonable and I found it. As of branch 1.4 of zaptel, the option for hardware HDLC framing has been integrated and IIRC since 3.2.2 version, wanpipe uses it rather than their own patch, so it's needed to change all those ... dchan=16 ... from zaptel.conf to ... hardhdlc=16 ... in order to pass the HDLC framing from the Sangoma's HDLC engine to the D channel. That explains why when you changed version prior the mentioned above, everything worked (Considering that this thread is from Oct 1, 2007)> The problem is that Asterisk has trouble bringing up the link. I see > the following lines every couple of minutes: > > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 up > == Primary D-Channel on span 1 upSince 2008-03-08, (chan_zap revision #106945) you will see that just once because the channel state itself is not changing.> q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED > q921.c:664 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHEDThose messages indicate that layer 2 is trying to reinitialize because there are no response from the other side due the missing working D-Channel. Regards, -- Octavio H. Ruiz Cervera Neocenter, SA. de CV. http://www.neocenter.com/ Soluciones para Centros de Contacto y Telefon?a IP Tel.: (+52 55) 8590-9000 Ext. 7016 Mobile: (+52 155) 5514-087790 Mobile: (+52 155) 5541-351242