Hi FoxB,
~ I have Ingenico 5100 terminals connection to AS5300 with mica modems. ~ ~ When terminals are set for 2400 and I have ~ Code: ~ modemcap entry ~ POS_5100:MSC=&F&D2S0=0S15=0S21=0S22=0S23=0S24=0S29=4S30=2400S31=1200S64=6 ~ ~ ~ Terminals connect and information is exchanged.
OK.
~ But if I set the terminals to 1200 ~ ~ And ~ Code: ~ modemcap entry ~ POS_5100:MSC=&F&D2S0=0S15=0S21=0S22=0S23=0S24=0S29=4S30=2400S31=1200S64=7 ~ ~ or ~ Code: ~ modemcap entry ~ POS_5100:MSC=&F&D2S0=0S15=0S21=0S22=0S23=0S24=0S29=4S30=2400S31=1200S64=8 ~ ~ ~ They got disconnected after first packet is exchanged. ~ ~ Any idea what to change?
I guess first of all, I would ask what different terminals you need to support, and how are they configured. Are some set for 2400 bps (V.22bis) and others for 1200 bps (Bell212a or V.22)?
Is it feasible to configure all terminals as desired? If so, then why not configure them all for V.22bis - which you say works fine - and be done with it?
Or must you support some terminals that are configured for V.22bis, and others that are configured for V.22/Bell212a?
In that case, you don't want to use S64 which sets a fixed modulation, and so can't possibly accommodate clients that are configured for different modulations.
We normally find configuring the MICA modems to automode for V.22bis (actually V.23) and below works well. Here is a typical configuration:
&f&d2s29=4ss53=0s15=0s22=0s23=0s24=0s0=0
If you should find that that a PoS call works well from one client but does not from another client, then here are the debugs that I would collect.
First, configure msec timestamps on your debugs, and "no logging console". You might want to log to a logging buffer. Also configure an ACL to match traffic to/from your application server. Also configure "service internal" (hidden global command). Also configure "modem call-record terse".
Also busy out all modems but one (if you can).
debug isdn q931 ! or debug cas debug csm modem ! or debug modem csm, in some IOS debug modem debug modem mica tx s/p debug modem mica rx s/p debug ip tcp packet address debug ip packet detail dump ! hidden command
Capture all of the debug output from a successful call. Then do the same for a failed call. Now compare and contrast the information from the two calls.
Have fun,
Aaron