Hi Nareg, In the config guides, the SBC ones refer to CUBE-SP which was the SP SBC offering from Cisco before it was EoS'ed. CUBE ENT config guides are for the Enterprise SBC offering Cisco has. If you are looking to get demarcation between your enterprise and the ITSP, you will deploy CUBE ENT on the enterprise side. More details on CUBE ENT can be found at https://cisco.box.com/cube At the same time, ITSP will have an SP SBC that CUBE ENT will communicate with on their side and that SP SBC was the CUBE SP offering or any other vendor's SP SBC. Since CUBE SP was EoS'ed long time back, I would suggest not to deploy it. Hope this clarifies. Regards, Hussain
... View more
Issue: One of the most common reasons for inbound T37 OnRamp faxes to fail is connection issues with the SMTP server. This could happen due to one of the following reasons: No SMTP Server configured SMTP Server configured but no IP route to server exists Incorrect username@hostname information being sent to the SMTP server Troubleshooting: 1. If inbound faxes on a T37 OnRamp GW are failing, run the following debugs: debug voip ccapi inout debug voip vtsp all debug fax foip all debug fax mta all debug fax fmsp send t30 debug fax fmsp receive t30 debug fax mspi all debug fax dmsp default 2. If you see the following message in the debugs then, Mar 5 16:48:47.212: (C)S: MAIL FROM:<FAX=@> Mar 5 16:48:47.708: (C)R: 501 5.5.4 Invalid Address Mar 5 16:48:47.708: esmtp_client_work: error in response to MAIL FROM The SMTP server does not like the MAIL FROM information. This is the originator account being used in the From field in the OnRamp email and is incorrect. Either one of the following needs to be configured on the gateway and should match what is defined in the SMTP server. ! Define the postmaster mail account for the onramp gateway mta send postmaster Administrator@exchange.com OR ! Specifies the hostname and username for the originator (“From:” field of email header) mta send mail-from hostname cisco.com mta send mail-from username FAXES 3. If you see the following message in the debugs then, Mar 4 10:46:48.703: %MSPI-1-MSPI_BAD_CONFIG: MSPI-bad configuration, mspi_setup_req:NULL server ip addressMar 4 10:46:48.703: mspi_setup_req: NULL server address
Mar 4 10:46:48.703: %LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_ESMTP_CONNECT: ESMTP client did not connect or lost connection to remote server The SMTP server may not be configured or configured incorrectly. Please check the following: ! Specify the destination email server that will receive the OnRamp fax email mta send server 10.1.1.1 port 25 4. If you see the following message in the debugs then, Mar 20 09:35:30.310: SMTP is in the error state... Mar 20 09:35:30.310: disc text=no route to destination (3): SMTP client open failed Mar 20 09:35:30.310: Still waiting for the SMTP connection..... Mar 20 09:35:30.310: %LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_ESMTP_CONNECT: ESMTP client did not connect or lost connection to remote server Mar 20 09:35:30.310: mspi_disconnect: cid=0x141, st=DISCONNECTING, cause=no route to destination (3) Mar 20 09:35:30.310: mspi_on_call_hist: cid=0x141, cause=no route to destination (3): SMTP client open failed Mar 20 09:35:30.310: disposing smtp ctx The SMTP server is configured but either no IP route to it exists or the OnRamp GW is not able to access port 25. Please verify connectivity by doing a telnet to the SMTP server's IP Address and port 25. You should see an output similar to below HQ#telnet 192.168.15.11 25 Trying 192.168.15.11, 25 ... Open 220 testmail.cisco.com Microsoft ESMTP MAIL Service ready at Wed, 14 Dec 2011 17:28:00 -0700 To see a sample OnRamp GW configuration, please check the Configuring T.37 article.
... View more
Introduction Starting IOS version 15.1(2)T, we can match inbound dial-peers via IP Address or hostname. This enables CUBE/TDM-SIP to connect to two or more different ITSPs allowing specific call routing, codec selection, digit manipulation, CAC, QoS, or security policies for each ITSP. Feature Overview Dial-peer selection is based on immediate SIP neighbor's address information and applicable only to incoming SIP calls. The address information is retrieved from the VIA header of the incoming message, which is then used to lookup the dial-peer that has the best match for the criteria selected. The lookup will first attempt to match a dial-peer with the address information in the following order: Via header Request URI To URI From URI Called Number If none of the parameters match, then the default inbound dial-peer is matched. This feature also allows for Generic DNS Caching framework for faster FQDN to IP Address lookup. For a configured FQDN, the DNS Caching framework resolves the FQDN and stores the corresponding set of IP addresses for it. The framework also takes care of the regular DNS refreshes for the FQDN. For a dial-peer match to be done, if the incoming Via header has an IP address and the configuration has an FQDN, then the corresponding resolved addressed of this FQDN is queried from the DNS Caching Framework. Call Flow ITSP1 ---> SIP --> Call from source address 172.16.1.10 -----> | ----> CUBE - SIP - CUCM - IP Phones ITSP2 ---> SIP --> Call from source address 172.31.10.10 ---> Sample Config !To handle incoming calls from ITSP1 voice class uri 1001 sip host ipv4:172.16.1.10 dial-peer voice 1 voip description Calls from ITSP1 session protocol sipv2 incoming uri via 1001 max-connection 10 codec g711ulaw acc-qos controlled-load req-qos controlled-load !To handle incoming calls from ITSP2 voice class uri 1002 sip host ipv4:172.31.10.10 dial-peer voice 1 voip description Calls from ITSP1 incoming uri via 1002 session protocol sipv2 max-connection 30 codec g729r8
... View more
About T.37 (Store-and-Forward) is an ITU standard which deals with sending and receiving fax messages using an email. It defines the basic communication procedures between the voice gateway and both the PSTN fax and mail server used in a T.37 call flow. Additionally they cover the formatting rules and encoding methods (MIME and TIFF) used in the fax/email conversion process for T.37. The T.30 specification defines the communication protocol between the T.37 voice gateway and the PSTN fax machine. Communication between the T.37 voice gateway and the mail server occurs via SMTP. MIME supplements SMTP by removing many of the formatting restrictions imposed by RFC 822 and provides attributes that describe how the fax images are encoded within the email so that the destination device can easily decode them. Cisco's implementation of T.37 supports a very small subset of the possible content types and encodings supported by MIME. For example, a Cisco T.37 gateway can only process emails with plain text or enriched text in the body of the email. Additionally, it only handles fax pages that are graphically encoded as TIFF-F as an attachment to the email. T.37 has two modes of operation: OnRamp - A T.37 OnRamp gateway (must run on the originating gateway) handles incoming PSTN fax calls, converts them to an email, and forwards the email to an SMTP mail server OffRamp - The OffRamp functionality (must run on a terminating gateway) turns incoming emails into a fax call T.37 Store-and-Forward Call Flow OnRamp With the On-ramp process, a voice gateway handles incoming calls from the standard fax machine or the PSTN and converts a traditional Group 3 fax to an e-mail message with a Tagged Image File Format (TIFF) attachment. The fax e-mail message and attachment are handled by an e-mail server while traversing the packet network. When acting as the On-ramp gateway, the Cisco gateway receives faxes from end users, converts them into TIFF files, creates standard MIME e-mail messages, attaches the TIFF files to the e-mail messages, and forwards the fax-mail messages to the designated SMTP server for storage. The gateway uses the sending MTA and dial peers to complete these tasks. The sending MTA, which is the Cisco gateway, defines delivery parameters associated with the e-mail message to which the fax TIFF file is attached. The delivery parameters include defining a return e-mail path or designating a destination mail server. OnRamp Configuration Guide Configuration hostname OnRampGW ! Enable T.37 function on the gateway
fax interface-type fax-mail controller T1 x/y/z framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 voice-port x/y/z:23 ! Define the onramp script to be utilized by the POTS dial peer
application service onramp flash:app_faxmail_onramp.220.127.116.11.tcl ! Link the onramp POTS dial peer to the script defined in the application submenu. ! Ensure that this OnRamp POTS dial-peer matches the correct incoming number
dial-peer voice <tag_1> pots service onramp incoming called-number 5556667777 direct-inward-dial port x/y/z:23!
dial-peer voice <tag_2> mmoip ! Define the IOS-bundled onramp script for the MMoIP dial peer.
service fax_on_vfc_onramp_app out-bound destination-pattern 5556667777 ! Specify that this MMoIP dial peer handles fax
information-type fax ! Indicate the email address of where the fax email should be sent (“To:” field)
session target mailto: email@example.com ! Request that an MDN message be sent back when the destination mail client has ! opened the fax message mdn ! Request that DSN messages be sent
dsn delayed dsn success dsn failure ! Define the value to be used in the CSI message sent to the originating fax machine.
! Wildcard that specifies that the information displayed is captured from the configured ! destination pattern.
fax receive called-subscriber $d$ ! Specify the destination email server that will receive the OnRamp fax email
mta send server 10.1.1.1 port 25 ! Specify text that will appear in the “Subject:” field of the email header
mta send subject Incoming PSTN Fax for 5556667777 ! Indicate the filename that will be used for the fax image attached to the email
mta send filename pstn_fax ! Insert a user comment to the email prefix header for additional identifying information
mta send origin-prefix This is an incoming fax message from the PSTN ! Define the postmaster mail account for the onramp gateway
mta send postmaster Administrator@exchange.com ! Specifies the hostname and username for the originator (“From:” field of email header.
mta send mail-from hostname cisco.com mta send mail-from username FAXES ! Specify the hostname and username for where MDNs should be sent.
mta send return-receipt-to hostname cisco.com mta send return-receipt-to username myaccount In this the originating PSTN fax machine dials (555) 666-7777 to reach the onramp gateway. The call arrives on voice port x/y/z:23 and matches the inbound POTS dial peer <tag_1>, which is configured with the appropriate onramp TCL script. On the outbound side the MMoIP dial peer <tag_2> is matched which directs the gateway to send the fax transmission as an email. This working onramp configuration contains all of the required T.37 onramp commands as well as some of the optional ones that are commonly seen. Note that this onramp configuration can be combined with an offramp configuration in order to create a single gateway that supports both onramp and offramp functionality. OffRamp With the Off-ramp process, a voice gateway handles calls going out from the network to fax machine or the PSTN and converts a fax e-mail with TIFF attachment into a traditional fax format that can be delivered to a standard fax machine or the PSTN. Off-ramp faxing requires that the Cisco gateway act as an Off-ramp gateway to dial the POTS and communicate with a remote fax machine (Group 3 fax device), using standard fax protocols. The Off-ramp gateway provides the following functionality: Converts a fax-mail to TIFF file (or plain text file) into a standard format and delivers it to the recipient. The Store-and-Forward Fax application does not alter the TIFF or plain text file in any way from its original format when converting it into a standard fax format. The Off-ramp gateway uses the receiving MTA and dial peers to perform the conversion. Delivers an e-mail message as a standard fax transmission. The Cisco gateway generates information that is appended to the top of each faxed page (text-to-fax pages) and creates a fax cover sheet. The Off-ramp gateway uses the receiving MTA, dial peers, and commands specific to formatting the appended information and generating a fax cover sheet to deliver e-mail messages as fax transmissions. Uses only POTS dial peers to define the line characteristics between the forwarding Off-ramp gateway and the fax device. Optionally configure the MMoIP dial peers can be configured to define fax compression schemes and resolution. This option is useful only if those parameters are to be altered for the received fax-mails. Defines the parameters associated with the gateway SMTP server, using the receiving MTAs. This can be its SMTP host aliases, which can be different than its normal DNS hostnames, or internal Cisco IOS hostname. OffRamp Configuration Guide Configuration hostname OffRamp ! Define the TSI value to be sent by the offramp gateway to the termainting fax machine. fax send transmitting-subscriber $s$ ! Specify the left fax header to display the sender’s address, the center header to ! display the transmission time and the right header to display the page number. fax send left-header $s$ fax send center-header $t$ fax send right-header $p$ ! Specify that a fax cover page be included with offramp fax transmissions. fax send coverpage enable ! Include email header information on the fax cover sheet. fax send coverpage show-detail ! Specify a comment to be included on fax cover pages. fax send coverpage comment OffRamp Fax From XYZ Corporation ! Enable T.37 faxing on the voice gateway. fax interface-type fax-mail ! Specify the mail server where DSN messages are sent. mta send server 10.1.1.1 port 25 ! Define additional hostnames to be used as an alias for this offramp gateway. mta receive aliases 18.104.22.168 mta receive aliases offramp.cisco.com ! Specify the number of simultaneous SMTP connections for the offramp gateway. mta receive maximum-recipients 100 ! Enable MDN response on the offramp gateway. mta receive generate mdn ! Specify the location of the offramp TCL script. ! This script is referenced by the offramp MMoIP dial peer. application service offramp flash:app_faxmail_offramp.22.214.171.124.tcl voice-port 1/0:23 ! Configure the offramp outbound POTS dial peer. dial-peer voice <tag_3> pots destination-pattern 4695550000 port x/y/z:23 forward-digits all ! Configure the inbound offramp MMoIP dial peer. dial-peer voice <tag_4> mmoip ! Link this MMoIP dial peer to the TCL offramp script defined under the application submenu service offramp ! Specify that this MMoIP dial peer handles fax information-type fax incoming called-number 4695550000 ! Specify the optional use of MH image encoding. image encoding MH ! Specify the optional image resolution of super fine. image resolution super-fine
... View more
About There may be scenarios where a third party vendor’s PBX hardware uses a proprietary ISDN signaling protocol. Unless the same PBX (signaling standard) is used on both ends of the circuit, you need a way so that the two PBXs or voice gateways can properly communicate signaling information back and forth. QSIG is an open standard protocol which defines services and signaling protocols for Private Integrated Services Networks (PISNs) to overcome this issue. It is a peer-to-peer signaling protocol that uses Q.931 as its underlying signaling protocol but modifies the signals so proprietary ISDN signaling protocols can be used by non-proprietary equipment on the other end of the connection. The ISDN Q.921 and Q.931 standards provide the basis for QSIG protocol, which sets a worldwide standard for PBX interconnection. In a basic QSIG call, a user in a Private Integrated Services Network Exchange (PINX) can place a call to a user that is in a remote PINX. The called party receives the caller name or number as the call rings. The calling party receives the called name and number when the user phone rings in the remote PINX. All the features that are available as a PBX user operate transparently across the network. QSIG protocol provides supplementary and additional network features, as defined for PISNs, if the corresponding set of QSIG features are supported by both ends of the call. Cisco UC solutions support QSIG to connect with various vendors’ PBX systems and Central Office (CO) switches that use the QSIG standard. Note that if QSIG information is being tunneled to CUCM (or if it is a MGCP PRI to CUCM running QSIG) then the feature set supported will differ from that which is supported in IOS. Configuation/Deployment Examples The switch type confiugred must be QSIG: isdn switch-type primary-qsig
To have IOS decode QSIG messages, enable: voice service voip
To enable Call Diversion: interface Serial x/y/z:23
isdn supp-service calldiversion
For Transparent Tunneling of QSIG and Q.931 over SIP/H.323: voice service voip
signaling forward unconditional
signaling forward rawmsg !this command can also be placed under the respective VoIP dial-peer
For translation between SIP and QSIG MWI, only unsolicited notify is supported: sip-ua
mwi-server dns:cisco.com expires 60 port 5060 transport udp unsolicitedvoice service voip
For CME with QSIG PBX: voice service voip
voice service pots
supplementary-service qsig call-forward For CME with QSIG PBX being used as Voicemail Server such as Mitel: voice service voip
dial-peer voice <tag> pots
port x/y/z:23 H.450.7 may need to be enabled for some scenarios where transferring via Q.SIG over H323: voice service voip
CUCM supports both ECMA and ISO standards for Q.SIG. See the endpoint specific configuration in CUCM to ensure that it is provisioned properly. There are also sevral QSIG service parameters in CUCM under varios sections such as call forward. QSIG Support on IOS Voice GWs Please refer the link below: QSIG Support on Voice Gateways CME Support Please reference the QSIG section in the CME Admin guide for the latest information: CME Administration Guide
... View more
Introduction With the number of faxing protocols supported by Cisco devices and Service Providers, it is easy to get confused with all the possibilities. The important point to note is that in a fax call flow, all the devices on VoIP need to utilize the same faxing protocol for a fax call to be successful as faxing protocols cannot be transcoded unlike audio calls. A fax call first sets up as an audio call and then switches over to a fax call. Two of the most common switchover mechanisms are NSE (Cisco propriety) and protocol based (Standards) switchover. Just like the faxing protocols, the switchover mechanism also needs to be the same in a fax call flow. This document lists the most commonly encountered faxing call flows Cisco customers open TAC SRs for along with a baseline configuration that should be present on the gateways. Fax Call Flows A. Telco – PRI – GW – FXS – Fax/Modem [No FoIP protocols involved] voice service pots fax rate disable B. Telco – PRI – GW – MGCP – CUCM – MGCP – VG224 – Fax/Modem [Can do both Passthrough(NSE) and T38] Config for both GW and VG224 doing Modem Passthrough(NSE) no ccm-manager fax protocol cisco mgcp modem passthrough voip mode nse mgcp modem passthrough voip codec g711ulaw Config for both GW and VG224 doing T38 no ccm-manager fax protocol cisco no mgcp fax t38 inhibit mgcp package-capability fxr-package mgcp default-package fxr-package no mgcp fax t38 ecm C. Telco – FXO – GW – H323/SIP – CUCM – SCCP – VG248 – Fax/Modem [Can do both Passthrough(NSE) and T38(NSE). Protocol based switchover is not supported with SCCP] Config for GW doing Modem Passthrough(NSE) dial-peer voice <tag> voip modem passthrough nse codec g711ulaw OR If there is no specific configuration on the dial-peer, then the following should be present under "voice service voip" voice service voip modem passthrough nse codec g711ulaw Config for VG248 doing Modem Passthrough(NSE) 1) Configure --> Telephony --> Port specific parameters --> Choose the port to which the Fax machine is connected. Set "Fax Relay" to "disabled" 2) Configure --> Telephony --> Advanced Settings Set "Passthrough signaling" to IOS Mode Config for GW doing T38(NSE) dial-peer voice <tag> voip fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback pass-through <g711ulaw or g711alaw> fax-relay ecm disable OR If there is no specific configuration on the dial-peer, then the following should be present under "voice service voip" voice service voip fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback pass-through <g711ulaw or g711alaw> fax-relay ecm disable fax-relay sg3-to-g3 Config for VG248 doing T38(NSE) 1) Configure --> Telephony --> Port specific parameters --> Choose the port to which the Fax machine is connected a) Set "Fax Relay" to "T.38 peer to peer" b) Set "Fax relay ECM" to "disabled" c) Set "Fax relay NSF" to "override with 000000" 2) Configure --> Telephony --> Advanced Settings Set "Passthrough signaling" to IOS Mode D. Telco – PRI – GW – MGCP – CUCM – SCCP – ATA186 – Fax/Modem [Can only do Passthrough(NSE)] Config for GW doing Modem Passthrough(NSE) no ccm-manager fax protocol cisco mgcp modem passthrough voip mode nse mgcp modem passthrough voip codec g711ulaw Config for ATA186 doing Modem Passthrough(NSE) Please refer to "Configuring and Troubleshooting the Cisco ATA 186 with Fax" E. Telco – PRI – GW – MGCP – CUCM – SIP – ATA187 – Fax/Modem [Can do both Passthrough and T38] Config for GW doing Modem Passthrough: no ccm-manager fax protocol cisco mgcp modem passthrough voip mode nse mgcp modem passthrough voip codec g711ulaw Config for GW doing T38: no ccm-manager fax protocol cisco no mgcp fax t38 inhibit mgcp package-capability fxr-package mgcp default-package fxr-package no mgcp fax t38 ecm mgcp fax t38 nsf 000000 For ATA187 please refer to "Cisco ATA 187 Analog Telephone Adaptor Administration Guide for SIP, Version 1.0" F. Telco – PRI – GW – SIP/H323 – CUCM – SIP – Fax Server [Mostly uses T38, but need to confirm with the customer] Config for GW doing T38 dial-peer voice <tag> voip fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback pass-through <g711ulaw or g711alaw> fax-relay ecm disable OR If there is no specific configuration on the dial-peer, then the following should be present under "voice service voip" voice service voip fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback pass-through <g711ulaw or g711alaw> fax-relay ecm disable fax-relay sg3-to-g3 G. ITSP – SIP – CUBE – SIP/H323 – CUCM – SCCP – VG224 [VG224 needs to be an MGCP GW for this setup to work. NSE switchover is only specific to Cisco devices and providers do not support NSE based switchovers] Config for CUBE doing T38: dial-peer voice <tag> voip fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback pass-through <g711ulaw or g711alaw> fax-relay ecm disable OR If there is no specific configuration on the dial-peer, then the following should be present under "voice service voip" voice service voip fax protocol t38 nse ls-redundancy 0 hs-redundancy 0 fallback pass-through <g711ulaw or g711alaw> fax-relay ecm disable fax-relay sg3-to-g3 Config for VG224 doing T38: no ccm-manager fax protocol cisco no mgcp fax t38 inhibit mgcp package-capability fxr-package mgcp default-package fxr-package no mgcp fax t38 ecm H. ATA186 – SCCP – CUCM – SIP – ATA187 [ATA187 needs to run firmware 9.2.3 to support NSE based passthrough, otherwise integration is not possible]
... View more
If power is lost or the phone is reset during upgrade, all stored credentials are removed. After power is restored, the devices will recover by using the normal recovery sequence. This can include requesting a new IP address, downloading a configuration file, applying any new configuration parameters, downloading new firmware or locales, and registering with the Call Control.
... View more
How are you connected to the PSTN? PRI, CAS, E1 R2, or FXO? When you say bad voice quality, what exactly is the symptom? Choppy audio, echo, static, etc.The following document has samples of various bad audio quality symptoms and they can help you identify exactly what are you experiencing. Recognizing and Categorizing Symptoms of Voice Quality Problems. http://www.cisco.com/en/US/tech/tk652/tk698/technologies_white_paper09186a00801545e4.shtml
... View more