HI,
I am having issue in receiving FAX from PSTN lines to Public SIP trunk connected to PABX and PABX release is 9.1. The issue is that when a FAX is sent in manual mode from FAX machine PABX doest detect T38 but when its sent in auto mode PABX detects T38 and FAX call is successfull
What the Public SIP service provider has said is listed below and also attached is the trace taken from PABX.
"[font=]Here is what's happening
Scenario 1 – Auto mode (S3 --> PBX)
paper is fed, dialled the number and pressed start. Fax machine dials the number, stars negotiation and sends the fax successfully. See the below SIP msg flow negotiating the T.38.
Scenario 2 – Manual mode (S3 --> PBX)
paper is fed, pressed speaker phone, dial the number and listen for the ringing. When PBX answers the call, start button is pressed to send the fax. Fax machine stars negotiation and then it fails to send the fax. See the below SIP msg flow requesting for T.38.
Softswitch (MetSphere CFS) sends SIP INVITE (SDP) message 3 time and PBX (3350203) doesn't respond to the INVITE msg. Finally softswitch sends BYE to terminate the call.
Basically when PBX detects fax tone, it send the request and softswitch responds to it allowing T.38 fax. But when softswitch detects and request for T.38, PBX doesn't respond to it. Please investigate why PBX doesn't respond to T.38 SIP INVITE msg.
Regards[/font]"
please help me out in this
Incoming FAX issue when sent in manual mode
Incoming FAX issue when sent in manual mode
You do not have the required permissions to view the files attached to this post.
Re: Incoming FAX issue when sent in manual mode
The good practice is to provide two different logs with two cases: successful and unsuccessful with calling/called numbers, actions description. Let me to quote krzysioD:
Note that it's our private time, that we spent to help you, so please don't expect complete solution for your problem.
You will need to do homework by your self.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7013
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: Incoming FAX issue when sent in manual mode
We should put that on a wall...
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: Incoming FAX issue when sent in manual mode
hi,
below are the details and attached is the 2 call scenarios with one successful and other not successful.
Calling number is 3320636 (External PSTN line)
Called number is 203 (DID number 3350203(PABX extension) )
below are the details and attached is the 2 call scenarios with one successful and other not successful.
Calling number is 3320636 (External PSTN line)
Called number is 203 (DID number 3350203(PABX extension) )
You do not have the required permissions to view the files attached to this post.
Re: Incoming FAX issue when sent in manual mode
From c log
Attach sipalarm.log file which corresponds to that unsuccesful call and check "incvisu" and "excvisu" output.1317797698 -> ALARM: [receiveSuccessfulEvent] Call: SD5phq401-4b96d1787006a3e2eccc28fec3092baf-a808010 eqt: 799 TERMINATED_STATE failed to emit a Successful message.
1317797698 -> ALARM: CPU main
1317797698 -> [SIPLogAlarm] Log file reached maximum size, archiving...
1317797698 -> sip_short1 1
1317797698 -> sip_short1 0
1317797698 -> [SIPRollAlarmLog] Log file renamed from '/tmpd/sipalarm.log' to '/tmpd/sipalarm3.log'
1317797698 -> [SIPLogAlarm] Log file archived successfully
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.